Ingo Schwarze wrote:
Mike Erdely wrote on Fri, Dec 01, 2006 at 12:07:19PM -0500:
Could you check whether jabberd2 also uses large numbers of file
descriptors?
Mine is set to 1024 in both files (defaults).
Any ideas? Anyone else seeing c2s spike at 100% CPU on an almost
daily basis?
All this is now several months ago, but i dimly recall we saw
jabberd2 processes eating most of the CPU, too, though it never
got as bad as locking up the system (PIII 635MHz, 256 MD RAM).
It's actually _just_ the c2s process taking all the CPU. Killing the
jabberd perl wrapper script kills all processes and then jabberd can be
restarted.
I'm still sure about the following: When killing the processes
holding the leaked file descriptors, the CPU did go to 100% for
several seconds, and during that time, the system was not
responsive. But in all cases, the processes finally died off
and released all resourced they held.
The system was never unresponsive. Only jabber. At first it was only
new connections, but then even established connections seemed not to be
able to chat.
I've applied your patch to the 4.0 port, rebuild and re-installed.
We'll see if it makes a difference:
<http://marc.theaimsgroup.com/?l=openbsd-ports&m=116519984904818&w=2>
-ME
