ejabberd - Comments for "Jabber server keeps crashing after gobbling memory"

I'm seeing this very same

neil — Wed, 13 May 2009 12:44:35 +0000

I'm seeing this very same issue as well - so any help here would be greatly appreciated.

The output for the process information in webtool looks like so:

Pid Name/Spawned as State Reductions Stack+heap MsgQ Length
<0.27394.12> proc_lib:init_p/5 Garbing (limited info) 110439599 285082125 288927

The crash I think is happening because the garbage collector is trying to allocate some memory - but it can't get it.

Any help would be fantastic.

badlop, what queues do you

DrKpo — Fri, 06 Feb 2009 17:47:39 +0000

badlop, what queues do you mean? Erlang interprocess queues or something else?

Anyways:
How do I check exactly if the queues consume RAM?

Thanks.

Some ideas

mfoss — Thu, 16 Oct 2008 18:17:50 +0000

Probably the memory is consumed by the processes queues: if the messages can't be processed as fast as they are received, the queues increase until some limit is reached. In your case it seems the limit is imposed by the system RAM, or maybe by Erlang capability to handle 4 GB.

If you increase the available RAM, the crash will happen later, but will happen for sure.

If that's the reason of the problem, the solution is to ensure that the queues don't grow continually. Some ideas:

Send less messages per unit time, so they can be processed faster than they are received.
Send smaller messages... I'm not sure if that is related, it depends how big your current messages are
Give more processing power to the executors, so that they can process your messages faster than they are received.
You have: [kernel-poll:false]. You can enable that, maybe it helps a little. Check Kernel Poll on ejabberd