The mailing list for listmasters using Sympa

[Patrick Rynhart <address@concealed>]

I thought I'd follow up this issue with my logs better formatted.  The 
logs below illustrate what's happening:

1. A bulk slave daemon process is started.
2. After doing work & once the expiry time elapses, the slave daemon 
appears to exit normally.
3. However, when Sympa services are restarted, it's logged that the 
slave "died suddenly".

This only happens once in a while.  (There are bulk slave daemon's 
starting and ending without an issue 99%+ of the time.)

My question is how can this situation happen ?

-----------

Apr 12 19:23:22 tur-lists2 bulk[14031]: info Bulk slave daemon started 
with pid 14031
Apr 12 19:23:22 tur-lists2 bulk[14031]: notice Done sending message  to 
list address@concealed (priority 8) in 2 seconds since scheduled 
expedition date.
Apr 12 19:23:22 tur-lists2 bulk[14031]: notice Done sending message  to 
list address@concealed (priority 8) in 2 seconds since scheduled 
expedition date.
Apr 12 19:23:23 tur-lists2 bulk[14031]: notice Done sending message  to 
list address@concealed (priority 8) in 2 seconds since scheduled 
expedition date.
Apr 12 19:23:23 tur-lists2 bulk[14031]: notice Done sending message  to 
list address@concealed (priority 8) in 2 seconds since scheduled 
expedition date.
Apr 12 19:33:24 tur-lists2 bulk[14031]: info Process 14031 didn't send 
any message since 600 seconds, exiting.
Apr 12 19:33:24 tur-lists2 bulk[14031]: notice bulk.pl exited normally 
due to signal
Apr 13 03:09:35 tur-lists2 bulk[15135]: notice tools::write_pid() 
Previous process 14031 died suddenly ; notifying listmaster