I have a 2 node proxmox 3.4 cluster, with separate quorum device.
I upgraded the proxmox nodes using premium repositories, with success.
Nevertheless, after the reboots, one node loose quorum and the other, for mysterious reasons, interferes with another cluster we have, using proxmox 2.3:
proxmox 2.3 cluster: /var/log/syslog
Nov 25 10:59:45 a84 rgmanager[641850]: [pvevm] VM 41245 is running
Nov 25 10:59:45 a84 rgmanager[641864]: [pvevm] VM 243 is running
Nov 25 10:59:46 a84 corosync[3031]: [TOTEM ] Retransmit List: 298b1 298b2 298b
3 298b4 298b5 298b6 298b7 298b8 298b9 298ba 298bb 298bc 298bd 298be 298bf 298c0
298c1
If I power down the 3.4 nodes, the messages disappear from the neighbor 2.3 cluster and works normally with no issues at all.
First I thought the problem was multicast issues, I reconfigured the cluster for unicast, modified some firewall rules, check the switches, and after several tests, down-times, and so on, I discovered if I boot proxmox 3.4-premium nodes with old kernel, the quorum problem no longer exists and all nodes and clusters work fine.
stock kernel: 2.6.32-39-pve
premium kernel: 2.6.32-43-pve
short story:
- one proxmox 2.3 cluster working normally.
- another 3.4 proxmox cluster.
|->after upgrade 3.4 nodes, proxmox 2.3 cluster looses rgmanager conectivity and messages from syslog are flooded with 'retransmit list' and alike. 3.4 cluster never gets Quorate status (inquorate).
powering down the 3.4 nodes, or booting 3.4 nodes with stock kernel, the problem is gone from the 2.3 cluster.
Please help me with this issue.
Regards,
Alfredo Luco.
I upgraded the proxmox nodes using premium repositories, with success.
Nevertheless, after the reboots, one node loose quorum and the other, for mysterious reasons, interferes with another cluster we have, using proxmox 2.3:
proxmox 2.3 cluster: /var/log/syslog
Nov 25 10:59:45 a84 rgmanager[641850]: [pvevm] VM 41245 is running
Nov 25 10:59:45 a84 rgmanager[641864]: [pvevm] VM 243 is running
Nov 25 10:59:46 a84 corosync[3031]: [TOTEM ] Retransmit List: 298b1 298b2 298b
3 298b4 298b5 298b6 298b7 298b8 298b9 298ba 298bb 298bc 298bd 298be 298bf 298c0
298c1
If I power down the 3.4 nodes, the messages disappear from the neighbor 2.3 cluster and works normally with no issues at all.
First I thought the problem was multicast issues, I reconfigured the cluster for unicast, modified some firewall rules, check the switches, and after several tests, down-times, and so on, I discovered if I boot proxmox 3.4-premium nodes with old kernel, the quorum problem no longer exists and all nodes and clusters work fine.
stock kernel: 2.6.32-39-pve
premium kernel: 2.6.32-43-pve
short story:
- one proxmox 2.3 cluster working normally.
- another 3.4 proxmox cluster.
|->after upgrade 3.4 nodes, proxmox 2.3 cluster looses rgmanager conectivity and messages from syslog are flooded with 'retransmit list' and alike. 3.4 cluster never gets Quorate status (inquorate).
powering down the 3.4 nodes, or booting 3.4 nodes with stock kernel, the problem is gone from the 2.3 cluster.
Please help me with this issue.
Regards,
Alfredo Luco.