ejabberd keeps stopping for no apparent reason

Hi,

I have a debian server (6.0.7 - squeeze) with ejabberd (2.1.5-3+squeeze1). A few month ago it became unstable: it keeps stopping for no apparent reason. First it was running for a month or so before stopping, but recently it will only run a few hours, or less. Sometimes while I'm connected, sometimes when I'm offline.

There is no dump file, and there is nothing in the log showing any issue.

I turned on debbuging, this is what I can see in the log:

=INFO REPORT==== 2013-04-05 01:01:38 ===
D(<0.2197.0>:ejabberd_receiver:320) : Received XML on stream = " "

=INFO REPORT==== 2013-04-05 01:01:47 ===
D(<0.509.0>:ejabberd_receiver:320) : Received XML on stream = " "

=INFO REPORT==== 2013-04-05 01:01:47 ===
D(<0.509.0>:shaper:61) : State: {maxrate,50000,6232.0702032723975,
                                    1365120070698857}, Size=1
M=0.010664627044319143, I=36985.704

=INFO REPORT==== 2013-04-05 01:02:08 ===
D(<0.2197.0>:ejabberd_receiver:320) : Received XML on stream = " "

=INFO REPORT==== 2013-04-05 01:02:38 ===
D(<0.2197.0>:ejabberd_receiver:320) : Received XML on stream = " "

=INFO REPORT==== 2013-04-05 01:02:47 ===
D(<0.509.0>:ejabberd_receiver:320) : Received XML on stream = " "

=INFO REPORT==== 2013-04-05 01:02:47 ===
D(<0.509.0>:shaper:61) : State: {maxrate,50000,3116.048620370867,
                                    1365120107684567}, Size=1
M=0.010321626913023085, I=59331.373

=INFO REPORT==== 2013-04-05 01:03:08 ===
D(<0.2197.0>:ejabberd_receiver:320) : Received XML on stream = " "

Does anybody have an idea what this could be? Is there a way to do further debugging?

Thanks in advance.

Robert

Those " " messages are

Those " " messages are probably the typical keep-alive messages some clients send every few seconds to ensure the connection is kept open. They are not necessary, but they are not reason for the problem you have: I think the problem is somewhere else.

If ejabberd stops kindly, it should show in the log some mention. If it crashes abruptly, it should leave a crash dump. So, if you have neither of them, I have no more clues.

Syndicate content