Ejabberd crash every hour

Hello all....

from this monday we have a big problem with our installation of ejabberd 2.1.9-1 (xmpp client is pidgin)

The server start eating memory until also swap is full; then ejabber crash.

I've disabled all modules and in this way this stop happening.

Now we can't change our the password (501: feature not implemented) , can't set the mood...(disappeared option in menu) WTF happened about you?

How can enable at least the password changing feature?
In ejabberd user manual there's no reference about.

Thank you very much for the help...

crash wrote: The server start

crash wrote:

The server start eating memory until also swap is full; then ejabber crash.

I've disabled all modules and in this way this stop happening.

This means that one of the modules is doing something that consumes a lot of memory. You want to know that module is problematic, to disable the problem module, and enable the other modules.

Maybe you have users that spam or abuse of mod_offline, or of mod_pubsub, or mod_vcard...

crash wrote:

Now we can't change our the password (501: feature not implemented) ,
How can enable at least the password changing feature?

For that, enable mod_register.

crash wrote:

can't set the mood...(disappeared option in menu) WTF happened about you?

For that, enable mod_pubsub.

First of all thank you very

First of all thank you very much for the help,

But a few informations for this problem:

We are migrating from a well known commercial IM application, so I've manually register about 350 users (I don't want users can self register accounts), all was working well since I had about 100 of 350 users connected; when I've reach 150 users, the server start eating ram and then crash, so I had disabled all modules and the server start to work well without additional feature.
When I had tried to enable the mod_pubsub the server start eating ram again.

Can we limit this?

About the mod_register... THANK YOU !!! YOU SAVED ME!!!

crash wrote: We are migrating

crash wrote:

We are migrating from a well known commercial IM application, so I've manually register about 350 users (I don't want users can self register accounts), all was working well since I had about 100 of 350 users connected; when I've reach 150 users, the server start eating ram and then crash, so I had disabled all modules and the server start to work well without additional feature.
When I had tried to enable the mod_pubsub the server start eating ram again.

Can we limit this?

Simple solution: enable all the modules except mod_pubsub :)

But if your users need mod_pubsub, then you would have to investigate what circumstances make mod_pubsub to eat RAM: when some specific user logins? at certain hours of day? immediately after server start? when users wake up in the morning and connect to the server?

Syndicate content