[Server-devel] Ejabberd CPU/RAM Spike -> Crashes

[Devon Connolly]

I'm having some issues with ejabbered after re-flashing and re-registering a
student's XO. No other changes were made to the server; however, the beam
process has begun to constantly use 100% cpu while the ram usage swells to
over 1GB and then proceeds to eat the 2GB swap.  This continues until the
load average of the server reaches ~14,14,14 at which time the server
becomes unresponsive.

Multiple erl crash logs are being created (about 5-10 per minute) in
/var/log/ejabberd.  A brief excerpt:

erl_crash_20091216-124645.dump
_________________________________________________
=erl_crash_dump:0.1
Wed Dec 16 12:46:47 2009
Slogan: Kernel pid terminated (application_controller)
({application_start_failure, kernel, {shutdown, {kernel, start, [normal,
[]]}}})
System version: Erlang (BEAM) emulator version 5.6.5 [source]
[async-threads:0] [hipe][kernel-poll:false]

------------------------------
Anyway, each of these crash dump files are thousands of lines.  Any ideas
for debugging this?

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.laptop.org/pipermail/server-devel/attachments/20091216/076df5ec/attachment.htm