It's ktrace...and the output is extremely bizzare:
26208 qmail-smtpd EMUL "native"
26208 qmail-smtpd CALL gettimeofday(0xcfbe6c08,0)
26208 qmail-smtpd RET gettimeofday 0
26208 qmail-smtpd CALL getpid()
26208 qmail-smtpd RET getpid 26208/0x6660
26208 qmail-smtpd CALL getpid()
26208 qmail-smtpd RET getpid 26208/0x6660
26208 qmail-smtpd CALL gettimeofday(0xcfbe6ba8,0)
26208 qmail-smtpd RET gettimeofday 0
26208 qmail-smtpd CALL getpid()
26208 qmail-smtpd RET getpid 26208/0x6660
26208 qmail-smtpd CALL getpid()
26208 qmail-smtpd RET getpid 26208/0x6660
26208 qmail-smtpd CALL gettimeofday(0xcfbe6c08,0)
26208 qmail-smtpd RET gettimeofday 0
26208 qmail-smtpd CALL getpid()
26208 qmail-smtpd RET getpid 26208/0x6660
26208 qmail-smtpd CALL getpid()
26208 qmail-smtpd RET getpid 26208/0x6660
26208 qmail-smtpd CALL gettimeofday(0xcfbe6ba8,0)
26208 qmail-smtpd RET gettimeofday 0
26208 qmail-smtpd CALL getpid()
26208 qmail-smtpd RET getpid 26208/0x6660
26208 qmail-smtpd CALL getpid()
26208 qmail-smtpd RET getpid 26208/0x6660
...
This just keeps going until I run a kill -9 <pid>. I have no idea why this is
happening -- those functions are basic OS kinds of things, if I'm not mistaken, and
my OS seems to be in good shape.
Any thoughts, anyone?
Alex Kirk
Be nice to attach to the borked running process (or one of the borked
running processes) and see what it is doing. Is the trace program on
openbsd ptrace?
-----Original Message-----
From: Alex Kirk [mailto:alex.kirk@sourcefire.com]
Sent: Friday, May 18, 2007 10:46 AM
To: qmail@list.cr.yp.to
Subject: Dozens of qmail-smtpd processes eating 100% of CPU
Hello All,
schnarff.com:/var/log/qmail/smtpd$ ps aux | grep -i
qmail-smtpd
qmaild 6570 95.5 0.3 376 1416 ?? R 10:32AM 0:31.39
/var/qmail/bin/qmail-smtpd
root 13548 0.0 0.1 260 336 ?? I 10:07AM 0:00.02
supervise
qmail-smtpd
qmaild 5794 0.0 0.1 316 500 ?? S 10:31AM 0:00.01
/usr/local/bin/tcpserver -v -R -l schnarff.com -x /etc/tcp.smtp.cdb -c
50 -u 1012 -g 1005 0 smtp /var/qmail/bin/qmail-smtpd
I'd appreciate any information at all on what might be causing this, and
will be more than happy to supply additional info as necessary to help
diagnose.
Thanks,
Alex Kirk
|