On Thu, Jan 27, 2005 at 04:41:56PM +0100, Walter Haidinger wrote: > Hi! > > Whenever I enable either pyzor or dcc (or both), spamd hangs and spamc > doesn't return until the spamd process is killed. While running, it tries > to consume all available CPU time. > > In short (more details below), here are the debug logs: > debug: Pyzor is available: /usr/bin/pyzor > debug: entering helper-app run mode > logmsg: server hit by SIGCHLD > server hit by SIGCHLD > > That is, the helper-app never returns. Only if the forked spamd child is > manually killed. > > Without pyzor/dcc, or when fed through spamassassin (with dcc and pyzor), > there are no problems.
<snip> > spamc was always invoked with: > 'cat testmsg | spamc -U /var/lib/home/spamd/spamd.socket' I am not that familiar with SA but here are some suggestions: Have you tried running spamc/spamd in regular tcp/ip mode instead of through unix sockets? Is it spamd that hogs the cpu? Does it hang before executing pyzor, while pyzor is executing or after pyzor terminates? You might find helpful information by attaching (with the -p switch) strace or ltrace to the process hogging the cpu. The hanging process is clearly doing something, but what? Good luck, Martin Zuziak <[EMAIL PROTECTED]>
