Is it spamdyke that's using the CPU, or another process? clamav had a problem doing this sort of thing a couple versions back (0.95.x iirc).
Other than that, I haven't heard of anything like this. I'd look at processes related to queuing (scanners?) and see if there's a problem in that area. Given your volume, I'd suspect that there's a resource constraint that a little configuration tweaking might remedy. -- -Eric 'shubes' On 08/17/2011 10:33 PM, Chris Boulton wrote: > We're seeing a lot of spamdyke processes on our servers getting stuck in > some sort of state where they'll hang, and use 100% CPU until we kill -9 > them. Anyone else seeing this with 4.2.0? > > From what it looks like, it occurs once spamdyke has done its job and > Qmail has accepted the message. There'll always be open network > descriptors stuck in CLOSE_WAIT: > > spamdyke 32096 root txt REG 8,6 > 275224 1731152 /usr/bin/spamdyke > spamdyke 32096 root mem REG 8,6 > 93504 1730437 /usr/lib/libz.so.1.2.3.3 > spamdyke 32096 root mem REG 8,6 > 14616 54944903 /lib/libdl-2.7.so <http://libdl-2.7.so> > spamdyke 32096 root mem REG 8,6 > 1667176 1733359 /usr/lib/libcrypto.so.0.9.8 > spamdyke 32096 root mem REG 8,6 > 1375536 54944893 /lib/libc-2.7.so <http://libc-2.7.so> > spamdyke 32096 root mem REG 8,6 > 335936 1733360 /usr/lib/libssl.so.0.9.8 > spamdyke 32096 root mem REG 8,6 > 119288 54944779 /lib/ld-2.7.so <http://ld-2.7.so> > spamdyke 32096 root 0u IPv4 477462833 > TCP [US]:smtp->[THEM]:62593 (CLOSE_WAIT) > spamdyke 32096 root 1u IPv4 477462833 > TCP [US]:smtp->[THEM]:62593 (CLOSE_WAIT) > spamdyke 32096 root 2u IPv4 477462833 > TCP [US]:smtp->[THEM]:62593 (CLOSE_WAIT) > spamdyke 32096 root 3u IPv4 477462971 > UDP *:56058 > spamdyke 32096 root 4u unix 0xffff88005cac9500 > 477464597 socket > spamdyke 32096 root 5w FIFO 0,8 > 477463023 pipe > spamdyke 32096 root 6r FIFO 0,8 > 477463024 pipe > > An strace on the process shows that absolutely nothing is happening: > > $ strace -p 32096 > Process 32096 attached - interrupt to quit > ^CProcess 32096 detached > > Version: > > $ spamdyke -v > spamdyke 4.2.0+TLS+CONFIGTEST+DEBUG (C)2011 Sam Clippinger, samc (at) > silence (dot) org > http://www.spamdyke.org/ > > We're receiving around 80,000 connections to spamdyke a day, and out of > that end up with about 8 hung processes. > > I've just enabled the full-log-dir option in spamdyke to try and get > some internal logs, but I can't leave it enabled for long due to the > amount of mail we receive. > > Regards, > > Chris Boulton > Lead Engineer > BigCommerce > > Web: http://www.bigcommerce.com > > > > _______________________________________________ > spamdyke-users mailing list > spamdyke-users@spamdyke.org > http://www.spamdyke.org/mailman/listinfo/spamdyke-users _______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
