• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

SpamAssasin errors.....update killed it?

M

mirlyn

Guest
Get this in the logs:
Dec 2 08:52:49 roadrunner spamd[6791]: server hit by SIGHUP, restarting
Dec 2 08:52:50 roadrunner spamd[6793]: server hit by SIGHUP, restarting
Dec 2 08:52:51 roadrunner spamd[7310]: server started on UNIX domain socket /tmp/spamd_full.sock (running version 2.63)
Dec 2 08:52:51 roadrunner spamd[7311]: server started on UNIX domain socket /tmp/spamd_light.sock (running version 2.63)
Dec 2 08:53:57 roadrunner spamd[7310]: got connection over /tmp/spamd_full.sock
Dec 2 08:53:57 roadrunner spamd[7311]: got connection over /tmp/spamd_light.sock
Dec 2 08:53:57 roadrunner spamd[7530]: bad protocol: header error: (closed before headers)
Dec 2 08:53:57 roadrunner spamd[7531]: bad protocol: header error: (closed before headers)

I've been reading around looking for answers....is this the bug in the recent update? I searched, but nothing matches up as to possible causes/fixes.

We did an update Wednesday....ever since then, SA hardly checks email. I get the "bad protocol" messages for hours, then a successful scan, then more hours of "bad protocol."

Ideas?
 
If you do not use FreeBSD, upgrade to a more recent release.
 
Using 7.5.4 on Fedora Core 2

opened a ticket with plesk...awaiting response....
 
Back
Top