Hey guys
I recently deployed ejabberd in our environment. It has been running great. But today all of a sudden one the primary node is running at 180% CPU.
Nothing has changed, same number of users and everything.
What should i look at ? There is no info in the logs of any abnormality.
Let me know if you have seen this before.
What is your ejabberd version
What is your ejabberd version ? Did you check your ejabberd logs ?
ejabberd 15.07 running on
ejabberd 15.07 running on centos 7.
Keep seeing OOM's out of the blue with nothing in the ejabberd logs.
beam.smp is acting up taking 140-180% cpu at times.
thing i do not understand is. It was working fine for a few weeks and all of a sudden we start seeing these OOM's.
Searches for this issue are all over the place. someone says its pubsub and somewhere i saw mention of SMP parameter in ejabberdctl.cfg.
So talking about that SMP config in my ejabberdctl.cfg it is commented out.
#SMP=auto
Is the default disable ? should this be enabled ?
There is one change i can
There is one change i can think of. I changed the c2s_shaper and s2s_shaper from normal to fast.
and changed the fast value to 500000 bytes (=500 Kbps)
Could that be it ?
anyone ?
anyone ?