RGManager only starts on 2 out of 3 nodes

mangaskahn

New Member
Nov 15, 2012
3
0
1
I have been running Proxmox happily for about a month now on a 3 node cluster. I am in the process of configuring HA and I'm having trouble with the RM manager service. I seems that it will only start on the first two nodes to start up. It will run on all 3 nodes, but only on 2 at any given time. It never starts up on the last node powered on. Is there any way this can be corrected?
 
From Syslog, there doesn't appear to be any errors -

Nov 15 11:46:53 tlc-lvm03 rgmanager[2391]: Waiting for quorum to form
Nov 15 11:47:03 tlc-lvm03 rgmanager[2391]: Quorum formed
Nov 15 11:58:51 tlc-lvm03 rgmanager[3888]: Waiting for quorum to form
Nov 15 11:59:35 tlc-lvm03 rgmanager[3888]: Quorum formed
Nov 15 12:14:43 tlc-lvm03 pvedaemon[4781]: starting service rgmanager: UPID:tlc-lvm03:000012AD:000194BD:50A52303:srvstart:rgmanager:jmangas@TLC.LOCAL:
Nov 15 12:14:43 tlc-lvm03 pvedaemon[4008]: <jmangas@TLC.LOCAL> starting task UPID:tlc-lvm03:000012AD:000194BD:50A52303:srvstart:rgmanager:jmangas@TLC.LOCAL:
Nov 15 12:14:43 tlc-lvm03 pvedaemon[4008]: <jmangas@TLC.LOCAL> end task UPID:tlc-lvm03:000012AD:000194BD:50A52303:srvstart:rgmanager:jmangas@TLC.LOCAL: OK
Nov 15 12:15:02 tlc-lvm03 pvedaemon[4816]: starting service rgmanager: UPID:tlc-lvm03:000012D0:00019C42:50A52316:srvstart:rgmanager:jmangas@TLC.LOCAL:
Nov 15 12:15:02 tlc-lvm03 pvedaemon[4006]: <jmangas@TLC.LOCAL> starting task UPID:tlc-lvm03:000012D0:00019C42:50A52316:srvstart:rgmanager:jmangas@TLC.LOCAL:
Nov 15 12:15:02 tlc-lvm03 pvedaemon[4006]: <jmangas@TLC.LOCAL> end task UPID:tlc-lvm03:000012D0:00019C42:50A52316:srvstart:rgmanager:jmangas@TLC.LOCAL: OK



Which log should I be looking at? There are no errors in the console task log, and the cluster log shows the same messages as above. /var/log/cluster/rgmanager.log shows only the first 4 lines above.
I tried enabling debug logging on the rgmanager daemon by adding


<logging>
<logging_daemon name="rgmanager" debug="on"/>
</logging>


to cluster.conf but I don't see any additional output in the logs.