simscan queue does back up, and spamd begins to max out the cpu.
On Apr 4, 2007, at 5:49 PM, Bill Shupp wrote:
Alexey Amerik wrote:
Also Im spamd logs with debug enabled I see this:
@4000000046141a6c3a9a673c [4489] dbg: prefork: child 23924: entering
state 1
@4000000046141a6c3a9c4b9c [4489] dbg: prefork: new lowest idle
kid: 23924
@4000000046141a6c3a9d3dcc [4489] dbg: prefork: child reports idle
@4000000046141a6c3a9eeb7c [4489] info: prefork: child states: II
@4000000046141a6c3aa41f84 [23924] dbg: prefork: sysread(6) not ready,
wait max 300 secs
@4000000046141af03a75feec [23925] dbg: prefork: periodic ping from
spamd parent
@4000000046141af03a76165c [23925] dbg: prefork: sysread(8) not ready,
wait max 300 secs
@4000000046141af03a7625fc [23924] dbg: prefork: periodic ping from
spamd parent
@4000000046141af03a76359c [23924] dbg: prefork: sysread(6) not ready,
wait max 300 secs
Is spamd working at all? Can you send test messages through it
successfully? Or does it just get overwhelmed and the simscan queue
backs up?
Regards,
Bill
