Proxmox Cluster 2 nodes, problem with 2 Activity blocked

[Kage]

Hello,

i have problem with create 2 nodes cluster, after 5-10 min cluster goes to Quorum 2 Activity blocked(red in web interface)

configs below

are you able to advice what i have to do more to make this working?


root@hutivu:/home/psobota# pvecm status
Quorum information
------------------
Date: Tue Apr 12 11:43:53 2016
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000001
Ring ID: 38976
Quorate: No

Votequorum information
----------------------
Expected votes: 2
Highest expected: 2
Total votes: 1
Quorum: 2 Activity blocked
Flags:

Membership information
----------------------
Nodeid Votes Name
0x00000001 1 192.168.1.254 (local)

root@lifebook:~# pvecm status
Quorum information
------------------
Date: Tue Apr 12 11:46:51 2016
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000002
Ring ID: 35448
Quorate: No

Votequorum information
----------------------
Expected votes: 2
Highest expected: 2
Total votes: 1
Quorum: 2 Activity blocked
Flags:

Membership information
----------------------
Nodeid Votes Name
0x00000002 1 192.168.1.57 (local)


root@hutivu:/home/psobota# cat /etc/hosts|egrep "192.168.1.57|192.168.1.254"
192.168.1.254 localhost
192.168.1.254 hutivu.zapto.org hutivu pvelocalhost
192.168.1.57 lifebook.zapto.org lifebook

root@lifebook:~# cat /etc/hosts|egrep "192.168.1.57|192.168.1.254"
192.168.1.57 lifebook.zapto.org lifebook pvelocalhost
192.168.1.254 hutivu.zapto.org hutivu


root@hutivu:/home/psobota# cat /etc/pve/corosync.conf
logging {
debug: off
to_syslog: yes
}

nodelist {
node {
name: lifebook
nodeid: 2
quorum_votes: 1
ring0_addr: lifebook
}

node {
name: hutivu
nodeid: 1
quorum_votes: 1
ring0_addr: hutivu
}

}

quorum {
provider: corosync_votequorum
}

totem {
cluster_name: home
config_version: 4
ip_version: ipv4
secauth: on
version: 2
interface {
bindnetaddr: 192.168.1.254
ringnumber: 0
}

}


root@lifebook:~# cat /etc/pve/corosync.conf
logging {
debug: off
to_syslog: yes
}

nodelist {
node {
name: lifebook
nodeid: 2
quorum_votes: 1
ring0_addr: lifebook
}

node {
name: hutivu
nodeid: 1
quorum_votes: 1
ring0_addr: hutivu
}

}

quorum {
provider: corosync_votequorum
}

totem {
cluster_name: home
config_version: 4
ip_version: ipv4
secauth: on
version: 2
interface {
bindnetaddr: 192.168.1.254
ringnumber: 0
}

}

 

[t.lamprecht]

Hmm sounds like a switch problem? Does multicast work reliably?

Check the tests, especially the 5th in your case from:
https://pve.proxmox.com/wiki/Troubleshooting_multicast,_quorum_and_cluster_issues

Check if your switch is configured correctly and allows multicast, you can try to disable IGMP snooping on the switch (often the source for such problems).

If it still gives problems post the output from

journalctl -b -u corosync

 

[Kage]

Hi,

yes i set separated devices with one cable between nodes and now it's working ok,

have you any experience with MIKROTIK CLOUD ROUTER SWITCH CRS125-24G-1S-2HND-IN set as normal bridge, no firewall, all other configuration removed. when connection goes via this mikrotik, then not working

Best Regards / Pozdrawiam

Przemysław Sobota