• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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