• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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