Question Plesk SpamAssassin service is down. Why ?

[OverWolf]

Hi,
today I've received an email from watchdog that spamassassin went down.
I've tried to look if ther was a memory problem, but I've 8GB and plesk report me that I'm using 2.5GB.
I would like to know where I can look to find (if there is) the problem.

I'm on 17.5.3 update 91 on CentOS 7.7

On Mail log I found these :

Mar 28 03:29:45 server1 spamd[2050]: spamd: server killed by SIGTERM, shutting down
Mar 28 03:29:46 server1 spamd[31094]: logger: removing stderr method

on messages I found these :

Mar 28 03:29:45 server1 systemd: Stopping Spamassassin daemon...
Mar 28 03:29:45 server1 systemd: Stopped Spamassassin daemon.
Mar 28 03:29:45 server1 systemd: Starting Spamassassin daemon...
Mar 28 03:29:46 server1 monit: 'psa_spamassassin' process is not running
Mar 28 03:29:46 server1 monit: 'psa_spamassassin' trying to restart
Mar 28 03:29:46 server1 monit: 'psa_spamassassin' start: /usr/local/psa/admin/bin/spammng
Mar 28 03:29:47 server1 systemd: Started Spamassassin daemon.
Mar 28 03:29:47 server1 monit: Service start was done successfully.

Edit:
I found a strange coincidence; at the same time there was nginx log rotation. Is this a possible cause ?

 

[IgorG]

I found a strange coincidence; at the same time there was nginx log rotation. Is this a possible cause ?

This may be related to this described issue Logrotate process takes a lot of CPU time
I suggest you check it.

 

[OverWolf]

Hi Igor,
thank you, but I'm on 17.5.3 and not 12. Anyway, I've looked and the dimension isn't a problem

5834 Mar 30 03:17 logrotate.status