Hi Mike,
Mike Erdely wrote on Mon, Dec 04, 2006 at 11:14:59AM -0500:
> Ingo Schwarze wrote:
>> Could you check whether jabberd2 also uses large numbers of file
>> descriptors?
> Mine is set to 1024 in both files (defaults).
Er, well, i meant the number of file descriptors jabberd,
in particular c2s, actually used, not the number is was allowed to.
[EMAIL PROTECTED] # fstat | grep _jabberd | wc -l
78
[EMAIL PROTECTED] # fstat | grep s2s | wc -l
11
[EMAIL PROTECTED] # fstat | grep c2s | wc -l
30
>> Mike Erdely wrote on Fri, Dec 01, 2006 at 12:07:19PM -0500:
>>> 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 see. In our case, it was the s2s process. Yet, the file Klara
patched is used for both binaries, so it may still be the same bug.
> 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>
Even if it should not help in your case, i.e. if you found another
unrelated bug, i should like to see Klara's patch in the tree to
save people from being bitten by the bug we stumbled upon -
let me know if i can do anything more to help.
Yours,
Ingo
