The mailing list for listmasters using Sympa

[Olivier Salaun - CRU <address@concealed>]

You might fix your problem with :
        * either change 'log_socket_type' sympa.conf parameter
        * or apply attached patch against Log.pm. It will prevent Sympa from 
trying to
          reconnect to syslogd if connection was lost.

Please keep us informed which solution worked for you...

Eric Sandquist wrote:
> Well... Syslogd has been running the whole time.. All other loggins seems to
> be working just fine...  Last weeks re-attempt at this yielded this error:
>
> connect: No such file or directory (SOCK_DGRAM after trying SOCK_STREEM) at
> /www/sympa/bin/Log.pm line 96
>
> Is it possible, then, that syslogd is unavailable due to another process
> writing to it?  If so, is there another way for me to redirect of handle the
> logging?
>
> Sever load has been very low over all - .86-1.40...  So this does not seem
> to make sense...

--
Olivier Salaun
Comite Reseau des Universites
*** /home/sympa/bin/Log.pm      Tue Feb 11 14:50:58 2003
--- /tmp/Log.pm Tue Feb 11 14:49:27 2003
***************
*** 67,76 ****
      # do not log if log level if too high regarding the log requested by 
user 
      return if ($level > $log_level);
  
!     unless (syslog($fac, $m, @_)) {
!       &do_connect();
!           syslog($fac, $m, @_);
!     }
      if ($main::options{'foreground'} and (!$main::options{'batch'}))  {
        $m =~ s/%m/$errno/g;
        printf STDERR "$m\n", @_;
--- 67,76 ----
      # do not log if log level if too high regarding the log requested by 
user 
      return if ($level > $log_level);
  
! #    unless (syslog($fac, $m, @_)) {
! #     &do_connect();
! #         syslog($fac, $m, @_);
! #    }
      if ($main::options{'foreground'} and (!$main::options{'batch'}))  {
        $m =~ s/%m/$errno/g;
        printf STDERR "$m\n", @_;