"Ihnen, David" <[EMAIL PROTECTED]> wrote: >So, I looked at top and slocate was eating cpu. I killed slocate, Hmm... wonder why it was eating CPU. >and restarted qmail. Why? >Its been running for 20 minutes now, at 100% cpu >utilization. Funny that qmail-send is now doing what slocate was doing. You're seeing this behavior on two systems? If it was just one, I'd suspect a h/w problem. >I disabled tcpserver so that more messages won't interfere with the >processing of the current queue. Watch out for local injections, too, via qmail-inject. >These systems have fast disks and fast CPUs. Should I let it continue >munging on the data and hope it cranks through, or should I do something >else... Don't do anything else until you figure out what the problem is. Randomly trying things like restarting qmail will only make the problem worse. >The log file shows nothing since restart at this time.... Hmm... What qmail processes are running? >CPU states: 0.1% user, 99.8% system, 0.0% nice, 0.0% idle Ouch. 99.8% system is pretty extreme. Try strace'ing qmail-send to see what it's doing. > 403 root 0 0 216 168 116 S 0 0.0 0.0 544:12 syslogd Consider multilog instead. -Dave
