copy_config timeout?

[David Baron <d_...@012.net.il>]

Saw this in my logcheck:

Jul 18 22:28:55 ip6-localhost spamd[10008]: spamd: copy_config timeout, 
respawning child process after 114 messages at /usr/sbin/spamd line 1130.

Latest and greatest from Debian Sid. What's happening?

Re: copy_config timeout?

[Matt Kettler <mk...@verizon.net>]

Daryl C. W. O'Shea wrote:
> David Baron wrote:
>> Saw this in my logcheck:
>>
>> Jul 18 22:28:55 ip6-localhost spamd[10008]: spamd: copy_config
>> timeout, respawning child process after 114 messages at
>> /usr/sbin/spamd line 1130.
>>
>> Latest and greatest from Debian Sid. What's happening?
>
> It took more than 20 seconds for a spamd child to restore its initial
> SA config (which could have been modified by a user config) after
> processing a message.  It gave up and killed itself.
>
> This is usually indicative of high load and/or swap thrashing.  It's
> not a fatal condition but if it's happening constantly you'll want to
> investigate why.

And while you're at it, check to make sure you're not using any absurdly
large add-on rulesets like sa-blacklist (which is really only practical
for research purposes, but for legacy reasons is included in RulesDuJour
so many people accidentally use this ruleset.)

Re: copy_config timeout?

["Daryl C. W. O'Shea" <sp...@dostech.ca>]

David Baron wrote:
> Saw this in my logcheck:
> 
> Jul 18 22:28:55 ip6-localhost spamd[10008]: spamd: copy_config timeout, 
> respawning child process after 114 messages at /usr/sbin/spamd line 1130.
> 
> Latest and greatest from Debian Sid. What's happening?

It took more than 20 seconds for a spamd child to restore its initial SA 
config (which could have been modified by a user config) after 
processing a message.  It gave up and killed itself.

This is usually indicative of high load and/or swap thrashing.  It's not 
a fatal condition but if it's happening constantly you'll want to 
investigate why.


Daryl