[Server-devel] Ejabberd CPU/RAM Spike -> Crashes

[Martin Langhoff]

On Sun, Dec 20, 2009 at 12:57 PM, Martin Langhoff
<martin.langhoff at gmail.com> wrote:
> Yep, I am interested in getting to the bottom of this.

I think I have an initial assessment of the situation.

Clearly, the mnesia DB got corrupted somehow. Because of that...

 - the init script did cannot stop ejabberd normally...

 - killall -9 beam kills the beam processes, which get restarted right
away (such is the magic of erlang's engine "failsafe design") by
epmd...

 - Moodle's cronjob talks to ejabberd every 5 minutes. When ejabberd
is broken, you get a pileup of php scripts trying to run ejabberdctl
again and again.

so your attempts to follow my instructions (stop ejabberd, remove
corrupt DB, start it again) didn't succeed.

Now it's up on a pristine state, and I am monitoring it...



m
-- 
 martin.langhoff at gmail.com
 martin at laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff