I'm running jabberd2 from ports on an 4.0-release+patches, P4 2GHz, 1 GB
RAM box for ~50 users. This box is running nothing but jabber & mysql.
Jabber is configured to use the local mysql (its only purpose is jabber)
for storage and LDAPS for authentication.
During the work week jabber seems to be working fine and then at some
point people cannot log in. People who are already logged in do not seem
to have a problem. A few seconds later, the c2s process is taking all of
the CPU.
Jabber has to be killed and restarted in order to work again.
I've modified sysctl with "kern.maxfiles=10240".
I've set mysqld to run under this login class (sudo -c mysql
.../mysql.server start):
mysql:\
:openfiles-cur=4096:\
:openfiles-max=4096:\
:tc=daemon:
It doesn't feel like a mysql problem since mysql never has to be restarted.
Running /usr/local/sbin/jabberd as root or as _jabberd doesn't make a
difference.
Any ideas? Anyone else seeing c2s spike at 100% CPU on an almost daily
basis?
-ME
