You want to know who and how

mfoss — Mon, 06 Jun 2011 08:38:07 +0000

You want to know who and how provokes the sessions to close.
Maybe ejabberd closes the XMPP session of a user because
the TCP connection of that XMPP session was closed.

Are the bots running in a remote machine, where a network program
in the middle may close the TCP connections?

If that happens exactly at 00.43 everyday, try adding 5 minutes to the clock of the machine.
Is now the session closing delayed 5 minutes too? Now advance the clock 10 minutes,
is now the session clossing advanced 10 minutes?

Clients get disconnected, but ejabberd itself doesn't stop?
One way I know to close XMPP sessions is to call "ejabberdctl stop",
and then ejabberd logs:

(ejabberd@localhost)1> 
=INFO REPORT==== 6-Jun-2011::10:28:02 ===
I(<0.456.0>:mod_muc_room:705) : Stopping MUC room room123@conference.localhost

=INFO REPORT==== 6-Jun-2011::10:28:02 ===
I(<0.453.0>:ejabberd_c2s:1454) : ({socket_state,gen_tcp,#Port<0.5221>,<0.452.0>}) Close session for badlop@localhost/work

=INFO REPORT==== 6-Jun-2011::10:28:07 ===
I(<0.39.0>:ejabberd_app:89) : ejabberd 2.1.7 is stopped in the node ejabberd@localhost

... and, at the client side,

dotz — Sun, 05 Jun 2011 10:12:34 +0000

... and, at the client side, I get "host unreachable". Any ideas, why?

ejabberd - Comments for "ejabberd disconnects my bots every day at 00:43"

You want to know who and how

... and, at the client side,