[ejabberd] Server allocating all available ram, then stops at 100% CPU

Peter Schwindt ejabberd at schwindt-net.de
Mon Nov 11 10:45:32 MSK 2013


we're experiencing some unfunny behaviour at jabber.ccc.de these days:

After some time running the ejabberd (2.1.13) beam.smp (erlang 15b1)
process is seen to run at > 150% CPU, allocating more and more ram and
afterwards it stops accepting and forwarding packets and runs at 100% -
which therefor isn't usable so we have to kill the process and restart.

Having a look at the last log entries in ejabberd.log there are quite a
few of these:

=ERROR REPORT==== 2013-11-11 07:35:27 ===
E(<0.487.0>:gen_iq_handler:118) : {badarg,



Any ideas? Is there another possibility to look for the reason of these


More information about the ejabberd mailing list