I have exactly have same

Ohi — Thu, 17 Nov 2011 16:05:01 +0000

I have exactly have same problem. Did you find any solution for this? Thanks.

http://www.ejabberd.im/node/5065

Ok I think found the real

tmartin — Fri, 23 Sep 2011 08:36:11 +0000

Ok I think found the real issue.

So during my tests I worked only on two nodes: ejabberd@jabber1.site1 and ejabberd@jabber2.site1.

Here is my tests:
- ejabberd is running on both nodes, all is working well
- I stopped ejabberd on ejabberd@jabber1.site1, ejabberd@jabber2.site1 saw it down as excepted
- I restarted ejabberd@jabber2.site1, it saw ejabberd@jabber1.site1 down and is worked as well
- I stopped ejabberd@jabber2.site1, at this point there is no more ejabberd running
- I started ejabberd@jabber1.site1 and there is the problem: he is not responding at all, it seems he is waiting for the second node...

So I guess when a node goes down, and if it know there was an other node UP in the past, he try to communicate with it (and wait for it) when it restart.
There is anyway to bypassed this feature?

ejabberd - Comments for "Issue in ejabberd cluster when others nodes are unavailable."

I have exactly have same

Ok I think found the real