• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Spamassasin not monitored

Thomas Wilhelmi

Regular Pleskian
Hello,

I upgraded from 17.0 (last version) to 17.5.3 on Ubuntu 16.04.

My SpamAssassin is running but not monitored and I get the following entries in the logfile:

Jun 23 23:03:19 h2504000 monit[3614]: 'psa_spamassassin' failed to start
Jun 23 23:03:19 h2504000 monit[3614]: 'psa_spamassassin' process is not running
Jun 23 23:03:19 h2504000 monit[3614]: 'psa_spamassassin' trying to restart
Jun 23 23:03:19 h2504000 monit[3614]: 'psa_spamassassin' start: /opt/psa/admin/bin/spammng

How can I solve this?

BR,
Willi
 
Hi Thomas Wilhelmi,

did you consider to stop/start "psa-spamassassin" over the command line?
Code:
/etc/init.d/psa-spamassassin stop

/etc/init.d/psa-spamassassin start
 
Hi Thomas Wilhelmi,

did you consider to stop/start "psa-spamassassin" over the command line?
Code:
/etc/init.d/psa-spamassassin stop

/etc/init.d/psa-spamassassin start
Yes, but I used the commands from the Watchdog-Entry:

/opt/psa/admin/bin/spammng --stop
/opt/psa/admin/bin/spammng --start

and I even rebootet the server
 
Hi,

if someone else has the same issue:

In the file /usr/local/psa/etc/modules/watchdog/monitrc.tpl the monitored Pid-File is mentioned. Here we see that the file /var/run/spamd.pid is monitored:

# SpamAssassin
check process psa_spamassassin
with pidfile "/var/run/spamd.pid"
start = "<psa_spamassassin_start>"
stop = "<psa_spamassassin_stop>"
if failed host localhost port 783 <spamassassin_protocol_check> with timeout <psa_spamassassin_connection_timeout> seconds then restart
if <psa_spamassassin_timeout_restarts> restarts within <psa_spamassassin_timeout_cycles> cycles then timeout
every <psa_spamassassin_cycles> cycles
mode <psa_spamassassin_mode>

but the Pid-File Spamassassin creates is /var/run/spamassassin.pid. Now we have 2 Options:

1. go to the path /var/run and run the following command: ln -s spamassassin.pid spamd.pid

or

2. Change the mentioned config-file Monitor.tpl so it has the following lines:
# SpamAssassin
check process psa_spamassassin
with pidfile "/var/run/spamassassin.pid"
start = "<psa_spamassassin_start>"
stop = "<psa_spamassassin_stop>"
if failed host localhost port 783 <spamassassin_protocol_check> with timeout <psa_spamassassin_connection_timeout> seconds then restart
if <psa_spamassassin_timeout_restarts> restarts within <psa_spamassassin_timeout_cycles> cycles then timeout
every <psa_spamassassin_cycles> cycles
mode <psa_spamassassin_mode>

Good luck :)
 
Back
Top