• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

spamassassin syswrite error

T

the_raverX

Guest
In the last couple of months since updating to Plesk 8.0.1 we've had problems with our mail server...

at times mail will just stop getting delivered to mailboxes, and after quite a bit of digging around we found out the problem was related to SpamAssassin..

if we do:
/etc/init.d/spamassassin stop
/etc/init.d/psa-spamassassin stop
/etc/init.d/spamassassin start
/etc/init.d/psa-spamassassin start

mail will start getting processed again..

chased through the logs and found that when spamassassin dies, the following appears in the mail logs..

spamd[22359]: prefork: syswrite(8) failed, retrying... at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamA
ssassin/SpamdForkScaling.pm line 554

searched google, appears to be an existing problem in the version of spamassassin bundled with plesk, and recommendation is to upgrade..

of course attempting to do this via cpan doesn't work..

anyone have suggestions?
 
*bump*

no one has any advice on how to fix this?

i've just had to restart spamassassin and psa-spamassassin as spamassassin had died out again with this error and now mail is backlogged on our server..
 
Back
Top