Cluster down but all hipersvisors are ok

A

Anthony Robert

Member
May 25, 2018
7
0
21
29
Hello,

I have a problem with my cluster all hypervisors are on, vm are ok.
i cant connect in ssh from every vmhost to others but the cluster is down with no modifications.
The last modification i do is to put these 3 servers in LACP with a eno1eno2->bond->bridge(ip/24).
the picture of syslog on 3 servers.
the dates of 3 servers ares ok & the same !

If someone can help me.

Best Regars

Anthony
 

Attachments

  • vm2.PNG
    vm2.PNG
    175.8 KB · Views: 7
  • vm4.PNG
    vm4.PNG
    187.5 KB · Views: 7
  • vm9.PNG
    vm9.PNG
    198.5 KB · Views: 7
Here the problem :

Jun 26 14:03:26 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:28 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5776) was formed. Members
Jun 26 14:03:28 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:28 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:28 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:28 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5776) was formed. Members
Jun 26 14:03:28 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:28 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:28 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:30 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5784) was formed. Members
Jun 26 14:03:30 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:30 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:30 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:30 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5784) was formed. Members
Jun 26 14:03:30 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:30 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:30 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:32 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5792) was formed. Members
Jun 26 14:03:32 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:32 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:32 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:32 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5792) was formed. Members
Jun 26 14:03:32 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:32 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:32 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:35 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5800) was formed. Members
Jun 26 14:03:35 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:35 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:35 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:35 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5800) was formed. Members
Jun 26 14:03:35 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:35 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:35 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:37 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5808) was formed. Members
Jun 26 14:03:37 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:37 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:37 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:37 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5808) was formed. Members
Jun 26 14:03:37 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:37 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:37 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:39 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5816) was formed. Members
Jun 26 14:03:39 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:39 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:39 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:39 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5816) was formed. Members
Jun 26 14:03:39 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:39 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:39 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:41 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5824) was formed. Members
Jun 26 14:03:41 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:41 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:41 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:41 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5824) was formed. Members
Jun 26 14:03:41 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:41 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:41 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:43 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5832) was formed. Members
Jun 26 14:03:43 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:43 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:43 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:43 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5832) was formed. Members
Jun 26 14:03:43 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:43 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:43 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:45 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5840) was formed. Members
Jun 26 14:03:45 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:45 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:45 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:45 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5840) was formed. Members
Jun 26 14:03:45 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:45 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:45 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:47 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5848) was formed. Members
Jun 26 14:03:47 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:47 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:47 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:47 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5848) was formed. Members
Jun 26 14:03:47 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:47 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:47 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:50 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5856) was formed. Members
Jun 26 14:03:50 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:50 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:50 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:50 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5856) was formed. Members
Jun 26 14:03:50 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:50 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:50 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:52 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5864) was formed. Members
Jun 26 14:03:52 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:52 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:52 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:52 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5864) was formed. Members
Jun 26 14:03:52 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:52 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:52 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:54 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5872) was formed. Members
Jun 26 14:03:54 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:54 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:54 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:54 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5872) was formed. Members
Jun 26 14:03:54 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:54 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:54 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:56 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5880) was formed. Members
Jun 26 14:03:56 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:56 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:56 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:56 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5880) was formed. Members
Jun 26 14:03:56 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:56 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:56 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:58 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5888) was formed. Members
Jun 26 14:03:58 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5888) was formed. Members
Jun 26 14:03:58 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:03:58 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:03:58 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:03:58 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:03:58 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:03:58 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:04:00 vmhost9 systemd[1]: Starting Proxmox VE replication runner...
Jun 26 14:04:00 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5896) was formed. Members
Jun 26 14:04:00 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5896) was formed. Members
Jun 26 14:04:00 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:04:00 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:04:00 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:04:00 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:04:00 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:04:00 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:04:01 vmhost9 pvesr[14923]: trying to aquire cfs lock 'file-replication_cfg' ...
Jun 26 14:04:02 vmhost9 pvesr[14923]: trying to aquire cfs lock 'file-replication_cfg' ...
Jun 26 14:04:02 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5904) was formed. Members
Jun 26 14:04:02 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5904) was formed. Members
Jun 26 14:04:02 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:04:02 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:04:02 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:04:02 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:04:02 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:04:02 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:04:03 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5908) was formed. Members
Jun 26 14:04:03 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:04:03 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:04:03 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:04:03 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5908) was formed. Members
Jun 26 14:04:03 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:04:03 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:04:03 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:04:03 vmhost9 pvesr[14923]: trying to aquire cfs lock 'file-replication_cfg' ...
Jun 26 14:04:04 vmhost9 pvesr[14923]: trying to aquire cfs lock 'file-replication_cfg' ...
Jun 26 14:04:05 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.4:5912) was formed. Members joined: 3
Jun 26 14:04:05 vmhost9 corosync[14684]: warning [TOTEM ] JOIN or LEAVE message was thrown away during flush operation.
Jun 26 14:04:05 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.4:5912) was formed. Members joined: 3
Jun 26 14:04:05 vmhost9 corosync[14684]: [TOTEM ] JOIN or LEAVE message was thrown away during flush operation.
Jun 26 14:04:05 vmhost9 corosync[14684]: [TOTEM ] JOIN or LEAVE message was thrown away during flush operation.
Jun 26 14:04:05 vmhost9 corosync[14684]: [TOTEM ] JOIN or LEAVE message was thrown away during flush operation.
Jun 26 14:04:05 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.2:5916) was formed. Members joined: 2
Jun 26 14:04:05 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.2:5916) was formed. Members joined: 2
Jun 26 14:04:05 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:04:05 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:04:05 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:04:05 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:04:05 vmhost9 corosync[14684]: notice [QUORUM] This node is within the primary component and will provide service.
Jun 26 14:04:05 vmhost9 corosync[14684]: notice [QUORUM] Members[3]: 2 3 1
Jun 26 14:04:05 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:04:05 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: members: 1/1540, 2/1429
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: starting data syncronisation
Jun 26 14:04:05 vmhost9 corosync[14684]: [QUORUM] This node is within the primary component and will provide service.
Jun 26 14:04:05 vmhost9 corosync[14684]: [QUORUM] Members[3]: 2 3 1
Jun 26 14:04:05 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: cpg_send_message retried 1 times
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: node has quorum
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: members: 1/1540, 2/1429
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: starting data syncronisation
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: members: 1/1540, 2/1429, 3/1502
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: members: 1/1540, 2/1429, 3/1502
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: received sync request (epoch 1/1540/0000001C)
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: received sync request (epoch 1/1540/0000001D)
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: received sync request (epoch 1/1540/00000018)
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: received sync request (epoch 1/1540/00000019)
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: received all states
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: leader is 1/1540
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: synced members: 1/1540, 2/1429
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: start sending inode updates
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: sent all (3) updates
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: all data is up to date
Jun 26 14:04:05 vmhost9 systemd[1]: Started Proxmox VE replication runner.
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: received all states
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: all data is up to date
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: received log
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: members: 1/1540, 3/1502
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: starting data syncronisation
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: members: 1/1540, 3/1502
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: starting data syncronisation
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: received sync request (epoch 1/1540/0000001E)
Jun 26 14:04:05 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.4:5920) was formed. Members left: 2
Jun 26 14:04:05 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 1 received
Jun 26 14:04:05 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.4:5920) was formed. Members left: 2
Jun 26 14:04:05 vmhost9 corosync[14684]: notice [QUORUM] Members[2]: 3 1
Jun 26 14:04:05 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:04:05 vmhost9 corosync[14684]: [CPG ] downlist left_list: 1 received
Jun 26 14:04:05 vmhost9 corosync[14684]: [CPG ] downlist left_list: 1 received
Jun 26 14:04:05 vmhost9 corosync[14684]: [QUORUM] Members[2]: 3 1
Jun 26 14:04:05 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: received all states
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: leader is 1/1540
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: synced members: 1/1540, 3/1502
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: start sending inode updates
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: sent all (0) updates
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [dcdb] notice: all data is up to date
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: received sync request (epoch 1/1540/0000001A)
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: received all states
Jun 26 14:04:05 vmhost9 pmxcfs[1540]: [status] notice: all data is up to date
Jun 26 14:04:06 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.2:5924) was formed. Members joined: 2
Jun 26 14:04:06 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.2:5924) was formed. Members joined: 2
Jun 26 14:04:06 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:04:06 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:04:06 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:04:06 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 0 received
Jun 26 14:04:06 vmhost9 corosync[14684]: [CPG ] downlist left_list: 0 received
Jun 26 14:04:06 vmhost9 corosync[14684]: notice [QUORUM] Members[3]: 2 3 1
Jun 26 14:04:06 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:04:06 vmhost9 corosync[14684]: [QUORUM] Members[3]: 2 3 1
Jun 26 14:04:06 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:04:11 vmhost9 pmxcfs[1540]: [dcdb] notice: members: 1/1540, 2/1429, 3/1502
Jun 26 14:04:11 vmhost9 pmxcfs[1540]: [dcdb] notice: starting data syncronisation
Jun 26 14:04:11 vmhost9 pmxcfs[1540]: [dcdb] notice: received sync request (epoch 1/1540/0000001F)
Jun 26 14:04:11 vmhost9 pmxcfs[1540]: [status] notice: members: 1/1540, 2/1429, 3/1502
Jun 26 14:04:11 vmhost9 pmxcfs[1540]: [status] notice: starting data syncronisation
Jun 26 14:04:11 vmhost9 pmxcfs[1540]: [status] notice: received sync request (epoch 1/1540/0000001B)
Jun 26 14:04:11 vmhost9 pmxcfs[1540]: [dcdb] notice: received all states
Jun 26 14:04:11 vmhost9 pmxcfs[1540]: [dcdb] notice: leader is 1/1540
Jun 26 14:04:11 vmhost9 pmxcfs[1540]: [dcdb] notice: synced members: 1/1540, 3/1502
Jun 26 14:04:11 vmhost9 pmxcfs[1540]: [dcdb] notice: start sending inode updates
Jun 26 14:04:11 vmhost9 pmxcfs[1540]: [dcdb] notice: sent all (3) updates
Jun 26 14:04:11 vmhost9 pmxcfs[1540]: [dcdb] notice: all data is up to date
Jun 26 14:04:12 vmhost9 pmxcfs[1540]: [status] notice: received all states
Jun 26 14:04:12 vmhost9 pmxcfs[1540]: [status] notice: all data is up to date
Jun 26 14:04:55 vmhost9 pveproxy[9821]: proxy detected vanished client connection
Jun 26 14:04:56 vmhost9 pveproxy[11208]: proxy detected vanished client connection
Jun 26 14:04:56 vmhost9 pveproxy[10985]: proxy detected vanished client connection
Jun 26 14:04:56 vmhost9 pveproxy[10985]: proxy detected vanished client connection
Jun 26 14:04:57 vmhost9 pveproxy[11208]: proxy detected vanished client connection
Jun 26 14:04:59 vmhost9 pvedaemon[23455]: <root@pam> successful auth for user 'root@pam'
Jun 26 14:05:00 vmhost9 systemd[1]: Starting Proxmox VE replication runner...
Jun 26 14:05:01 vmhost9 systemd[1]: Started Proxmox VE replication runner.
Jun 26 14:05:39 vmhost9 pveproxy[11208]: proxy detected vanished client connection
Jun 26 14:05:39 vmhost9 pvedaemon[23455]: <root@pam> successful auth for user 'root@pam'
Jun 26 14:05:40 vmhost9 pveproxy[10985]: proxy detected vanished client connection
Jun 26 14:05:45 vmhost9 pveproxy[9821]: proxy detected vanished client connection
Jun 26 14:05:45 vmhost9 pveproxy[9821]: proxy detected vanished client connection
Jun 26 14:05:46 vmhost9 pveproxy[9821]: proxy detected vanished client connection
Jun 26 14:06:00 vmhost9 systemd[1]: Starting Proxmox VE replication runner...
Jun 26 14:06:01 vmhost9 systemd[1]: Started Proxmox VE replication runner.
Jun 26 14:06:33 vmhost9 pveproxy[11208]: proxy detected vanished client connection
Jun 26 14:06:35 vmhost9 pveproxy[9821]: proxy detected vanished client connection
Jun 26 14:06:35 vmhost9 pveproxy[10985]: proxy detected vanished client connection
Jun 26 14:06:36 vmhost9 pveproxy[10985]: proxy detected vanished client connection
Jun 26 14:06:38 vmhost9 pveproxy[9821]: proxy detected vanished client connection
Jun 26 14:06:41 vmhost9 pvedaemon[9070]: <root@pam> successful auth for user 'root@pam'
Jun 26 14:07:00 vmhost9 systemd[1]: Starting Proxmox VE replication runner...
Jun 26 14:07:01 vmhost9 systemd[1]: Started Proxmox VE replication runner.
Jun 26 14:07:42 vmhost9 corosync[14684]: error [TOTEM ] FAILED TO RECEIVE
Jun 26 14:07:42 vmhost9 corosync[14684]: [TOTEM ] FAILED TO RECEIVE
Jun 26 14:07:44 vmhost9 corosync[14684]: notice [TOTEM ] A new membership (192.168.62.9:5928) was formed. Members left: 2 3
Jun 26 14:07:44 vmhost9 corosync[14684]: notice [TOTEM ] Failed to receive the leave message. failed: 2 3
Jun 26 14:07:44 vmhost9 corosync[14684]: warning [CPG ] downlist left_list: 2 received
Jun 26 14:07:44 vmhost9 corosync[14684]: notice [QUORUM] This node is within the non-primary component and will NOT provide any services.
Jun 26 14:07:44 vmhost9 corosync[14684]: notice [QUORUM] Members[1]: 1
Jun 26 14:07:44 vmhost9 corosync[14684]: notice [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:07:44 vmhost9 corosync[14684]: [TOTEM ] A new membership (192.168.62.9:5928) was formed. Members left: 2 3
Jun 26 14:07:44 vmhost9 corosync[14684]: [TOTEM ] Failed to receive the leave message. failed: 2 3
Jun 26 14:07:44 vmhost9 corosync[14684]: [CPG ] downlist left_list: 2 received
Jun 26 14:07:44 vmhost9 corosync[14684]: [QUORUM] This node is within the non-primary component and will NOT provide any services.
Jun 26 14:07:44 vmhost9 corosync[14684]: [QUORUM] Members[1]: 1
Jun 26 14:07:44 vmhost9 corosync[14684]: [MAIN ] Completed service synchronization, ready to provide service.
Jun 26 14:07:44 vmhost9 pmxcfs[1540]: [status] notice: node lost quorum
Jun 26 14:07:44 vmhost9 pmxcfs[1540]: [dcdb] crit: received write while not quorate - trigger resync
Jun 26 14:07:44 vmhost9 pmxcfs[1540]: [dcdb] crit: leaving CPG group
Jun 26 14:07:44 vmhost9 pmxcfs[1540]: [status] notice: members: 1/1540
Jun 26 14:07:44 vmhost9 pve-ha-lrm[1740]: unable to write lrm status file - unable to open file '/etc/pve/nodes/vmhost9/lrm_status.tmp.1740' - Permission denied
Jun 26 14:07:45 vmhost9 pmxcfs[1540]: [dcdb] notice: start cluster connection
Jun 26 14:07:45 vmhost9 pmxcfs[1540]: [dcdb] notice: members: 1/1540
Jun 26 14:07:45 vmhost9 pmxcfs[1540]: [dcdb] notice: all data is up to date
Jun 26 14:08:00 vmhost9 systemd[1]: Starting Proxmox VE replication runner...
Jun 26 14:08:01 vmhost9 pvesr[15446]: trying to aquire cfs lock 'file-replication_cfg' ...
Jun 26 14:08:02 vmhost9 pvesr[15446]: trying to aquire cfs lock 'file-replication_cfg' ...
Jun 26 14:08:03 vmhost9 pvesr[15446]: trying to aquire cfs lock 'file-replication_cfg' ...
Jun 26 14:08:04 vmhost9 pvesr[15446]: trying to aquire cfs lock 'file-replication_cfg' ...
Jun 26 14:08:05 vmhost9 pvesr[15446]: trying to aquire cfs lock 'file-replication_cfg' ...
Jun 26 14:08:06 vmhost9 pvesr[15446]: trying to aquire cfs lock 'file-replication_cfg' ...
Jun 26 14:08:07 vmhost9 pvesr[15446]: trying to aquire cfs lock 'file-replication_cfg' ...
Jun 26 14:08:08 vmhost9 pvesr[15446]: trying to aquire cfs lock 'file-replication_cfg' ...
Jun 26 14:08:09 vmhost9 pves
 
Ok, thank you !

Here my problem in multicast :
oot@vmhost9:~# omping -c 600 -i 1 -q 192.168.62.9 192.168.62.2
192.168.62.2 : waiting for response msg
192.168.62.2 : joined (S,G) = (*, 232.43.211.234), pinging
192.168.62.2 : given amount of query messages was sent

192.168.62.2 : unicast, xmt/rcv/%loss = 600/600/0%, min/avg/max/std-dev = 0.131/0.187/0.312/0.022
192.168.62.2 : multicast, xmt/rcv/%loss = 600/262/56%, min/avg/max/std-dev = 0.159/0.213/0.331/0.024


Here my network config :
vmhost 9:

vmhost 2:
 

Attachments

  • 2.PNG
    2.PNG
    11.6 KB · Views: 3
  • 9.PNG
    9.PNG
    12.5 KB · Views: 3
Anthony Robert said:
192.168.62.2 : multicast, xmt/rcv/%loss = 600/262/56%, min/avg/max/std-dev = 0.159/0.213/0.331/0.024
Click to expand...
56% packet loss for multicast, corosync uses multicast.

Go through the docs and setup your network accordingly.
 
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