Karsten Bräckelmann <guent...@rudersport.de> writes:
> 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
No, there are no such messages. But the whole think seems a bit
paradoxical anyway, since if the logging failed the message should not
appear in the system log, should it?
> where the $eval_stat hopefully will give some more hints. What are you
> using for logging in SA?
I am starting spamd with --syslog-socket=unix, is that what you mean?
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
