The mailing list for listmasters using Sympa

["Silvers, Tim" <address@concealed>]

It turned out to be a bad message. Once I moved it from the msg queue, I was 
able to start Sympa and both sympa.pl processes kept running, processing the 
queue.

Another error I received indicated that there may have been an unsupported 
character set in the mail, which is likely what was occurring.

Tim

> On Sep 17, 2015, at 1:17 PM, Silvers, Tim <address@concealed> wrote:
> 
> Hi. I am having trouble diagnosing a problem with Sympa. I admit that I am 
> not well-versed in Sympa. I inherited it from a former admin. Today, 
> without any changes made on our backend, one of the two sympa.pl processes 
> died. Attempts to recover have not been successful. My understanding is 
> that there are two of these processes running, one to manage administration 
> and another one to manage the spools. I am not even sure which of them is 
> dying.
> 
> I ran an strace on the sympa.pl script and the last output is looking for a 
> file that it cannot find in the library paths.
> 
> stat("/usr/lib64/perl5/auto/DBI/DESTROY.al", 0x1c57130) = -1 ENOENT (No 
> such file or directory)
> stat("/usr/local/sympa/bin/auto/DBI/DESTROY.al", 0x7fff202da900) = -1 
> ENOENT (No such file or directory)
> stat("/usr/local/lib64/perl5/auto/DBI/DESTROY.al", 0x7fff202da900) = -1 
> ENOENT (No such file or directory)
> stat("/usr/local/share/perl5/auto/DBI/DESTROY.al", 0x7fff202da900) = -1 
> ENOENT (No such file or directory)
> stat("/usr/lib64/perl5/vendor_perl/auto/DBI/DESTROY.al", 0x7fff202da900) = 
> -1 ENOENT (No such file or directory)
> stat("/usr/share/perl5/vendor_perl/auto/DBI/DESTROY.al", 0x7fff202da900) = 
> -1 ENOENT (No such file or directory)
> stat("/usr/lib64/perl5/auto/DBI/DESTROY.al", 0x7fff202da900) = -1 ENOENT 
> (No such file or directory)
> stat("/usr/share/perl5/auto/DBI/DESTROY.al", 0x7fff202da900) = -1 ENOENT 
> (No such file or directory)
> stat("./auto/DBI/DESTROY.al", 0x7fff202da900) = -1 ENOENT (No such file or 
> directory)
> write(4, "\1\0\0\0\1", 5)               = 5
> shutdown(4, 2 /* send and receive */)   = 0
> close(4)                                = 0
> close(3)                                = 0
> exit_group(0)                           = ?
> 
> Is this what is causing the failure? Why would it suddenly start failing?
> 
> Thanks,
> 
> Tim
>

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail