[ejabberd] PEP being memory hungry?

Evgeniy Khramtsov xramtsov at gmail.com
Tue Sep 21 10:07:06 MSD 2010


21.09.2010 09:02, Yao Ko wrote:
> These are two crashes from two different nodes on 9/13 and 9/16 
> respectively.
> http://clientupdater.raptr.com/koyao/erl_crash_20100913-210315.dump.gz
>    

It is hard to say about the exact reason for the crash, because there 
were several processes consuming memory:
1) one c2s process: you should return max_fsm_queue option back. Set it 
to 10000 globally and 1000 for ejabberd_c2s listener.
2) one process holding iq stanzas; it is hard to say what was the 
module, so try to set {iqdisc, {queues, 50}} for every module which 
support that option.
3) the most problematic part: ejabberd_mod_pubsub_loop_raptr.com with 
6329 messages in its queue. I have a little knowledge of the pubsub 
code, so maybe Christophe or Karim have any ideas.

> http://clientupdater.raptr.com/koyao/erl_crash_20100916-070055.dump.gz
>    

On this node, the reason of crash was error_logger actually. You should 
have enormous ejabberd.log/sasl.log on this node. Some analysis would be 
great: what were those messages?

-- 
Regards,
Evgeniy Khramtsov, ProcessOne.
xmpp:xram at jabber.ru.



More information about the ejabberd mailing list