On Wed, 2010-08-04 at 14:14 -0400, Nikolaus Rath wrote:
> For a couple of weeks now, spamd has been occasionally logging messages
> like this:
>
> Aug 4 02:49:58 ebox spamd[5555]: logger: try using
> --syslog-socket={unix,inet} or --syslog=file
> Aug 4 02:49:59 ebox spamd[30417]: logger: try using
> --syslog-socket={unix,inet} or --syslog=file
>
> Generally this doesn't seem to happen more than once a day and seems to
> coincide with some spamd childs taking exceptionally long to process a
> message:
After a quick grep and briefly looking at the code in Logger::Syslog, my
guess is that logging failed for some reason. That probably also
explains the long processing time. You also should see warnings logged
like this
logger: syslog failed: $eval_stat
where the $eval_stat hopefully will give some more hints. What are you
using for logging in SA?
guenther
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
