The mailing list for listmasters using Sympa

[Matt Caron <address@concealed>]

Also, assuming sudo is logging to syslog, you can grep for sudo in the logs, 
look for someone running the command and track it back to the user or program 
doing it.

On June 9, 2016 9:12:58 AM EDT, David Verdin <address@concealed> 
wrote:
>Hi,
>
>These logs appear when Sympa dameons receive an external kill signal.
>Sucvh as when the sympa init script is used with the "stop" command.
>
>So somebody must have issued this command. It could be some other
>process on your server. You should also check the shell history.
>
>Regards,
>
>David
>
>
>Le 09/06/2016 à 09:31, Simone Dal Maso (via sympa-users Mailing List) a
>écrit :
>> 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.
>>

-- 
"Life moves pretty fast. If you don't stop and look around once in a while, 
you could miss it."
    - Ferris Bueller
PGP Key: http://www.mattcaron.net/pgp_key.txt
~~ Matt Caron ~~