M
mirlyn
Guest
Get this in the logs:
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?
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?