ejabberd - Comments for "Ejabberd Cluster problem"

I am having the same issue.

ramiro — Tue, 24 Sep 2013 06:00:23 +0000

I am having the same issue. If I lose my primary server for some reason, other servers can't start. They run fine if they're already running, but if they go down for whatever reason, I can't bring them back up again. I have looked everywhere and there doesn't seem to be a good description anywhere on how to bring the second server up again. I have every single table replicated across to the secondary server.

I don't mind having to do manual work to bring it up but I don't like the idea that if my primary server is unavailable I can't do anything to restore the replicas.

Hello! The same problem with

sles — Thu, 05 Jul 2012 10:56:44 +0000

Hello!

The same problem with 2.1.10.
No logs at all, just doesn't allow connects.
Is it possible at least remove other nodes to start server?

I have found that with a two

brabb — Wed, 28 Mar 2012 23:11:13 +0000

I have found that with a two machine cluster, one always assumes the master role. This role appears to change depending on which node last committed a change. For instances I install server1 first and then server2 second. At this point if server1 is down, server2 will not start. However when I start both and then use the admin console (web interface) and change one of the database table storage options (RAM only to RAM and disk only) on server2 and submit the changes, this makes server2 become the master. Such that when I shut down both servers, server1 will not start until server2 is running.

I observed this behavior on both nodes (changing settings on one at a time) and the role of master switches.

I was not aware that clusters have to have a master. If one fails then I still have run time redundancy, however if the server left running was not the master and I need to restart, my solution is down (as the server won't start).

Is there some relevant documentation on this aspect of clustering? Is this expected behavior? Is there some configuration I am missing that would allow the two servers to start/stop independently of each other?

ejabberd version 2.1.8

I have the same problem on my

Hambik — Fri, 18 Nov 2011 07:51:24 +0000

I have the same problem on my cluster setup.
Both instances wait for each other to start. I cannot start one instance successfully without the other.

I am assuming that this is an expected behavior - During start-up the clustered nodes are kind of synchronizing each other by waiting for all instances to wake up. However, one thing which is very strange for me is that this is not documented anywhere :((.
OR, there must be a configuration option to enable single instance successful starting.

Anyway, I am also facing the same problem and any help would be appreciated. Btw, my Ejabberd version is 2.1.9.