Hi, I have review the logs

Ramesh Chand — Wed, 04 Jan 2017 07:56:50 +0000

Hi,

I have review the logs again but the process not mentioned anywhere in the logs.
We are using Apache/MySQL and ejabberd on the same server.

Thanks

Cannot allocate 1581921408

badlop — Tue, 03 Jan 2017 01:17:22 +0000

Cannot allocate 1581921408 bytes ---> that is more than 1300 megabytes, so I am not surprised the machine could not find so much RAM for ejabberd. The question is... what was ejabberd doing to require so many RAM?

Looking at your crash dump, it was almost all used by the erlang process <0.32019.26>. In the ejabberd logs, is that process mentioned anywhere? Maybe associated to some user, or some IP address, or to the SQL database (if you use one instead of Mnesia)?

ejabberd - Comments for "ejabberd Cannot allocate bytes of memory "

Hi, I have review the logs

Cannot allocate 1581921408