The mailing list for listmasters using Sympa

[David <address@concealed>]

No it's not a crash. Something we can be sure of is: when sympa crashes, it 
does not tell it on the logs just before.
Regards,
David

Le 9 juin 2016 17:14:01 CEST, Youcef N Baouchi 
<address@concealed> a écrit :
>Hi Simone,
>
>I feel like this is the same problem that several of us reported months
>ago about sympa crashing. What version are you running?
>
>Thanks,
>
>Youcef
>
>-----Original Message-----
>From: address@concealed
>[mailto:address@concealed] On Behalf Of Simone Dal
>Maso
>Sent: Thursday, June 9, 2016 1:31 AM
>To: Simone Dal Maso <address@concealed>
>Subject: [sympa-users] sympa daemon stops running...
>
>Hello,
>
>I really don't know if it is a sympa bug, but about once a day Sympa
>stops running.
>
>In the sympa.log I can read:
>
>
>Jun  9 07:48:58 localhost sympa[27013]: notice main::sigterm() signal
>TERM received, still processing current task Jun  9 07:48:58 localhost
>sympa[27013]: notice Sympa exited normally due to signal
>Jun  9 07:48:58 localhost archived[27033]: notice archived exited
>normally due to signal
>Jun  9 07:48:58 localhost bounced[27028]: notice bounced exited
>normally due to signal Jun  9 07:48:58 localhost bulk[27023]: notice
>main::sigterm() signal TERM received, still processing current task Jun
>9 07:48:58 localhost bulk[27023]: notice bulk.pl exited normally due to
>signal
>Jun  9 07:48:58 localhost task_manager[27018]: notice task_manager
>exited normally due to signal
>
>So Sympa stops running. The question is: do you have some ideas of what
>is happening? Where can I find more information about this strange
>process?
>
>Thank you.

-- 
Omnia vanitas