Proxmox Cluster Broken almost every day

S

starnetwork

Renowned Member
Dec 8, 2009
422
10
83
Hi,
I have cluster of 2x10Gbps network via Bond, using LACP
but almost every day, and sometime even few times a day, I connect to the GUI and see only on server info all servers and nodes with questionmark
attaching screenshot

after I logged-in to server202 and run:
systemctl restart pve-cluster.service
and it's back to green

any suggestion why it's happen?
how can we thoroughly solve it?
why it's effect all the servers and not just server202?

Regards,
 

Attachments

  • Proxmox-cluster-error-0804.png
    Proxmox-cluster-error-0804.png
    39.5 KB · Views: 26
LnxBil said:
You have to provide for information including log file output.
Click to expand...
sure, here:
Code: 
Virtual Environment 5.1-46
Node 'server202'
2018-04-08
Apr 08 07:55:54 server202 kernel: read cpu 6 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 7 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 8 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 9 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 10 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 11 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 12 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 13 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 14 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 15 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 16 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 17 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 18 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 19 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 20 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 21 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 22 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 23 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 24 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 25 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 26 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 27 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 28 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 29 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 30 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 31 ibrs val 0
Apr 08 07:55:54 server202 kernel: sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
Apr 08 07:55:54 server202 kernel: use_ibrs = 4, use_ibpb = 4
Apr 08 07:55:54 server202 kernel: read cpu 0 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 1 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 2 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 3 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 4 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 5 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 6 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 7 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 8 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 9 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 10 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 11 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 12 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 13 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 14 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 15 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 16 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 17 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 18 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 19 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 20 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 21 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 22 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 23 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 24 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 25 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 26 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 27 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 28 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 29 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 30 ibrs val 0
Apr 08 07:55:54 server202 kernel: read cpu 31 ibrs val 0
Apr 08 07:55:54 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502144) was formed. Members
Apr 08 07:55:54 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502144) was formed. Members
Apr 08 07:55:54 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:55:54 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:55:54 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:55:54 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:55:56 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502148) was formed. Members
Apr 08 07:55:56 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502148) was formed. Members
Apr 08 07:55:56 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:55:56 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:55:56 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:55:56 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:55:58 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502152) was formed. Members
Apr 08 07:55:58 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502152) was formed. Members
Apr 08 07:55:58 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:55:58 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:55:58 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:55:58 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:00 server202 systemd[1]: Starting Proxmox VE replication runner...
Apr 08 07:56:00 server202 systemd[1]: Started Proxmox VE replication runner.
Apr 08 07:56:01 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502156) was formed. Members
Apr 08 07:56:01 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502156) was formed. Members
Apr 08 07:56:01 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:01 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:01 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:01 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:03 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502160) was formed. Members
Apr 08 07:56:03 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502160) was formed. Members
Apr 08 07:56:03 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:03 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:03 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:03 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:04 server202 kernel: sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
Apr 08 07:56:04 server202 kernel: use_ibrs = 4, use_ibpb = 4
Apr 08 07:56:04 server202 kernel: read cpu 0 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 1 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 2 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 3 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 4 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 5 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 6 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 7 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 8 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 9 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 10 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 11 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 12 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 13 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 14 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 15 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 16 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 17 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 18 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 19 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 20 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 21 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 22 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 23 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 24 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 25 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 26 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 27 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 28 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 29 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 30 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 31 ibrs val 0
Apr 08 07:56:04 server202 kernel: sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
Apr 08 07:56:04 server202 kernel: use_ibrs = 4, use_ibpb = 4
Apr 08 07:56:04 server202 kernel: read cpu 0 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 1 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 2 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 3 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 4 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 5 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 6 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 7 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 8 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 9 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 10 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 11 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 12 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 13 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 14 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 15 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 16 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 17 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 18 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 19 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 20 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 21 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 22 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 23 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 24 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 25 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 26 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 27 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 28 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 29 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 30 ibrs val 0
Apr 08 07:56:04 server202 kernel: read cpu 31 ibrs val 0
Apr 08 07:56:04 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502164) was formed. Members
Apr 08 07:56:04 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502164) was formed. Members
Apr 08 07:56:04 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:04 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:04 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:04 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:06 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502168) was formed. Members
Apr 08 07:56:06 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502168) was formed. Members
Apr 08 07:56:06 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:06 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:06 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:06 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:11 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502172) was formed. Members
Apr 08 07:56:11 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502172) was formed. Members
Apr 08 07:56:11 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:11 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:11 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:11 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:13 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502176) was formed. Members
Apr 08 07:56:13 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502176) was formed. Members
Apr 08 07:56:13 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:13 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:13 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:13 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:14 server202 kernel: sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
Apr 08 07:56:14 server202 kernel: use_ibrs = 4, use_ibpb = 4
Apr 08 07:56:14 server202 kernel: read cpu 0 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 1 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 2 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 3 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 4 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 5 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 6 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 7 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 8 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 9 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 10 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 11 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 12 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 13 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 14 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 15 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 16 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 17 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 18 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 19 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 20 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 21 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 22 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 23 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 24 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 25 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 26 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 27 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 28 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 29 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 30 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 31 ibrs val 0
Apr 08 07:56:14 server202 kernel: sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
Apr 08 07:56:14 server202 kernel: use_ibrs = 4, use_ibpb = 4
Apr 08 07:56:14 server202 kernel: read cpu 0 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 1 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 2 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 3 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 4 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 5 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 6 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 7 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 8 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 9 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 10 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 11 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 12 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 13 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 14 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 15 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 16 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 17 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 18 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 19 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 20 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 21 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 22 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 23 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 24 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 25 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 26 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 27 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 28 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 29 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 30 ibrs val 0
Apr 08 07:56:14 server202 kernel: read cpu 31 ibrs val 0
Apr 08 07:56:14 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502180) was formed. Members
Apr 08 07:56:14 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502180) was formed. Members
Apr 08 07:56:14 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:14 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:14 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:14 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:16 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502184) was formed. Members
Apr 08 07:56:16 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502184) was formed. Members
Apr 08 07:56:16 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:16 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:16 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:16 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:21 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502188) was formed. Members
Apr 08 07:56:21 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502188) was formed. Members
Apr 08 07:56:21 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:21 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:21 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:21 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:23 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502192) was formed. Members
Apr 08 07:56:23 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502192) was formed. Members
Apr 08 07:56:23 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:23 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:23 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:23 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:24 server202 kernel: sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
Apr 08 07:56:24 server202 kernel: use_ibrs = 4, use_ibpb = 4
Apr 08 07:56:24 server202 kernel: read cpu 0 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 1 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 2 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 3 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 4 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 5 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 6 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 7 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 8 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 9 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 10 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 11 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 12 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 13 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 14 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 15 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 16 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 17 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 18 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 19 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 20 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 21 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 22 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 23 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 24 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 25 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 26 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 27 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 28 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 29 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 30 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 31 ibrs val 0
Apr 08 07:56:24 server202 kernel: sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
Apr 08 07:56:24 server202 kernel: use_ibrs = 4, use_ibpb = 4
Apr 08 07:56:24 server202 kernel: read cpu 0 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 1 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 2 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 3 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 4 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 5 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 6 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 7 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 8 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 9 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 10 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 11 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 12 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 13 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 14 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 15 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 16 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 17 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 18 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 19 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 20 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 21 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 22 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 23 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 24 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 25 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 26 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 27 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 28 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 29 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 30 ibrs val 0
Apr 08 07:56:24 server202 kernel: read cpu 31 ibrs val 0
Apr 08 07:56:24 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502196) was formed. Members
Apr 08 07:56:24 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502196) was formed. Members
Apr 08 07:56:24 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:24 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:24 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:24 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:26 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502200) was formed. Members
Apr 08 07:56:26 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502200) was formed. Members
Apr 08 07:56:26 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:26 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:26 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:26 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:33 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502204) was formed. Members
Apr 08 07:56:33 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502204) was formed. Members
Apr 08 07:56:33 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:33 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:33 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:33 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:34 server202 kernel: sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
Apr 08 07:56:34 server202 kernel: use_ibrs = 4, use_ibpb = 4
Apr 08 07:56:34 server202 kernel: read cpu 0 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 1 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 2 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 3 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 4 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 5 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 6 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 7 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 8 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 9 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 10 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 11 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 12 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 13 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 14 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 15 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 16 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 17 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 18 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 19 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 20 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 21 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 22 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 23 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 24 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 25 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 26 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 27 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 28 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 29 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 30 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 31 ibrs val 0
Apr 08 07:56:34 server202 kernel: sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
Apr 08 07:56:34 server202 kernel: use_ibrs = 4, use_ibpb = 4
Apr 08 07:56:34 server202 kernel: read cpu 0 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 1 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 2 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 3 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 4 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 5 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 6 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 7 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 8 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 9 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 10 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 11 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 12 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 13 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 14 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 15 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 16 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 17 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 18 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 19 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 20 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 21 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 22 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 23 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 24 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 25 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 26 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 27 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 28 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 29 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 30 ibrs val 0
Apr 08 07:56:34 server202 kernel: read cpu 31 ibrs val 0
Apr 08 07:56:34 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502208) was formed. Members
Apr 08 07:56:34 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502208) was formed. Members
Apr 08 07:56:34 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:34 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:34 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:34 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:36 server202 corosync[2072]: notice  [TOTEM ] A new membership (192.168.10.21:2502212) was formed. Members
Apr 08 07:56:36 server202 corosync[2072]:  [TOTEM ] A new membership (192.168.10.21:2502212) was formed. Members
Apr 08 07:56:36 server202 corosync[2072]: notice  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:36 server202 corosync[2072]: notice  [MAIN  ] Completed service synchronization, ready to provide service.
Apr 08 07:56:36 server202 corosync[2072]:  [QUORUM] Members[9]: 1 2 3 4 5 6 7 8 9
Apr 08 07:56:36 server202 corosync[2072]:  [MAIN  ] Completed service synchronization, ready to provide service.
 
zima said:
Looks like issue with multicast/igmp on switch/router.
Click to expand...
1. thanks for that, can you please provide any additional info?
why it's effect this node only?
why pve-cluster.service restart solve it if it's network issue?
why the ceph network on same switches not effected that issue?
2. what should we changed?

Thanks again!
 
starnetwork said:
wow, thanks for that update!
any news so far?
updates?
Click to expand...
I don't think it was fixed yet.

I have the latest updates, even so, today (2 times) I had to restart pve-cluster service on all nodes to take back online my cluster.

That's really annoying, and many proxmox users are facing with it.
 
LnxBil said:
That's right, but I want to stop you from posting this false accusation:
Click to expand...

It's not a false accusation, not even an accusation. It's a bug report.

And I'll repeat as many as necessary. Almost everyday I have to restart pve-cluster service due to this issue. If I were the only one which is facing with it, that would be a "false accusation", but it is not.

And I say again, you don't add anything to the topic with your unuseful comments.
 
starnetwork said:
Hi Tom
thanks for that note!
  1. before I report bug, I checking with the community if it's something that happen only to me
  2. just to inform everyone, I did update to the last version and so far it's stable, so it's OK
  3. I sent another issue to the bugzilla, it's without any status changes from 10-2017 https://bugzilla.proxmox.com/show_bug.cgi?id=1532
FYI,
Click to expand...

This (1532) is a feature request and will be available for 5.2 (this is the plan).
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back