[SOLVED] Nach update auf 5.4-11 keine Clusterkommunikation mehr

S

sommer75

Active Member
Proxmox Subscriber
Nov 29, 2016
21
2
43
50
Hallo,
nach dem Update des zweiten Node in einem 3 Node Cluster hat der zweite Node die Kommunikation zum Cluster verloren.


Jul 30 17:43:27 pve02 login[4126]: ROOT LOGIN on '/dev/tty1'
Jul 30 17:43:27 pve02 systemd[4107]: Startup finished in 112ms.
Jul 30 17:43:27 pve02 systemd[1]: Started User Manager for UID 0.
Jul 30 17:44:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Jul 30 17:44:01 pve02 pvesr[4709]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:44:02 pve02 pvesr[4709]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:44:03 pve02 pvesr[4709]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:44:04 pve02 pvesr[4709]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:44:05 pve02 pvesr[4709]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:44:06 pve02 pvesr[4709]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:44:07 pve02 pvesr[4709]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:44:08 pve02 pvesr[4709]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:44:09 pve02 pvesr[4709]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:44:10 pve02 pvesr[4709]: error with cfs lock 'file-replication_cfg': no quorum!
Jul 30 17:44:10 pve02 systemd[1]: pvesr.service: Main process exited, code=exited, status=13/n/a
Jul 30 17:44:10 pve02 systemd[1]: Failed to start Proxmox VE replication runner.
Jul 30 17:44:10 pve02 systemd[1]: pvesr.service: Unit entered failed state.
Jul 30 17:44:10 pve02 systemd[1]: pvesr.service: Failed with result 'exit-code'.
Jul 30 17:45:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Jul 30 17:45:01 pve02 pvesr[5111]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:45:02 pve02 pvesr[5111]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:45:03 pve02 pvesr[5111]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:45:04 pve02 pvesr[5111]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:45:05 pve02 pvesr[5111]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:45:06 pve02 pvesr[5111]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:45:07 pve02 pvesr[5111]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:45:08 pve02 pvesr[5111]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:45:09 pve02 pvesr[5111]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:45:10 pve02 pvesr[5111]: error with cfs lock 'file-replication_cfg': no quorum!
Jul 30 17:45:10 pve02 systemd[1]: pvesr.service: Main process exited, code=exited, status=13/n/a
Jul 30 17:45:10 pve02 systemd[1]: Failed to start Proxmox VE replication runner.
Jul 30 17:45:10 pve02 systemd[1]: pvesr.service: Unit entered failed state.
Jul 30 17:45:10 pve02 systemd[1]: pvesr.service: Failed with result 'exit-code'.
Jul 30 17:46:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Jul 30 17:46:01 pve02 pvesr[5535]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:46:02 pve02 pvesr[5535]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:46:03 pve02 pvesr[5535]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:46:04 pve02 pvesr[5535]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:46:05 pve02 pvesr[5535]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:46:06 pve02 pvesr[5535]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:46:07 pve02 pvesr[5535]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:46:08 pve02 pvesr[5535]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:46:09 pve02 pvesr[5535]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:46:10 pve02 pvesr[5535]: error with cfs lock 'file-replication_cfg': no quorum!
Jul 30 17:46:10 pve02 systemd[1]: pvesr.service: Main process exited, code=exited, status=13/n/a
Jul 30 17:46:10 pve02 systemd[1]: Failed to start Proxmox VE replication runner.
Jul 30 17:46:10 pve02 systemd[1]: pvesr.service: Unit entered failed state.
Jul 30 17:46:10 pve02 systemd[1]: pvesr.service: Failed with result 'exit-code'.
Jul 30 17:46:32 pve02 pvedaemon[3860]: <root@pam> successful auth for user 'root@pam'
Jul 30 17:47:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Jul 30 17:47:01 pve02 pvesr[5951]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:47:02 pve02 pvesr[5951]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:47:03 pve02 pvesr[5951]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:47:04 pve02 pvesr[5951]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:47:05 pve02 pvesr[5951]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:47:06 pve02 pvesr[5951]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:47:07 pve02 pvesr[5951]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:47:08 pve02 pvesr[5951]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:47:09 pve02 pvesr[5951]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:47:10 pve02 pvesr[5951]: error with cfs lock 'file-replication_cfg': no quorum!
Jul 30 17:47:10 pve02 systemd[1]: pvesr.service: Main process exited, code=exited, status=13/n/a
Jul 30 17:47:10 pve02 systemd[1]: Failed to start Proxmox VE replication runner.
Jul 30 17:47:10 pve02 systemd[1]: pvesr.service: Unit entered failed state.
Jul 30 17:47:10 pve02 systemd[1]: pvesr.service: Failed with result 'exit-code'.
Jul 30 17:48:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Jul 30 17:48:00 pve02 pvesr[6343]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:48:01 pve02 pvesr[6343]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:48:02 pve02 pvesr[6343]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:48:03 pve02 pvesr[6343]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:48:04 pve02 pvesr[6343]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:48:05 pve02 pvesr[6343]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:48:06 pve02 pvesr[6343]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:48:07 pve02 pvesr[6343]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:48:08 pve02 pvesr[6343]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:48:10 pve02 pvesr[6343]: error with cfs lock 'file-replication_cfg': no quorum!
Jul 30 17:48:10 pve02 systemd[1]: pvesr.service: Main process exited, code=exited, status=13/n/a
Jul 30 17:48:10 pve02 systemd[1]: Failed to start Proxmox VE replication runner.
Jul 30 17:48:10 pve02 systemd[1]: pvesr.service: Unit entered failed state.
Jul 30 17:48:10 pve02 systemd[1]: pvesr.service: Failed with result 'exit-code'.
Jul 30 17:49:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Jul 30 17:49:01 pve02 pvesr[6797]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:49:02 pve02 pvesr[6797]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:49:03 pve02 pvesr[6797]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:49:04 pve02 pvesr[6797]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:49:05 pve02 pvesr[6797]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:49:06 pve02 pvesr[6797]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:49:07 pve02 pvesr[6797]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:49:08 pve02 pvesr[6797]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:49:09 pve02 pvesr[6797]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:49:10 pve02 pvesr[6797]: error with cfs lock 'file-replication_cfg': no quorum!
Jul 30 17:49:10 pve02 systemd[1]: pvesr.service: Main process exited, code=exited, status=13/n/a
Jul 30 17:49:10 pve02 systemd[1]: Failed to start Proxmox VE replication runner.
Jul 30 17:49:10 pve02 systemd[1]: pvesr.service: Unit entered failed state.
Jul 30 17:49:10 pve02 systemd[1]: pvesr.service: Failed with result 'exit-code'.
Jul 30 17:50:00 pve02 systemd[1]: Starting Proxmox VE replication runner...
Jul 30 17:50:01 pve02 pvesr[7234]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:50:02 pve02 pvesr[7234]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:50:03 pve02 pvesr[7234]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:50:04 pve02 pvesr[7234]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:50:05 pve02 pvesr[7234]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:50:06 pve02 pvesr[7234]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:50:07 pve02 pvesr[7234]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:50:08 pve02 pvesr[7234]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:50:09 pve02 pvesr[7234]: trying to acquire cfs lock 'file-replication_cfg' ...
Jul 30 17:50:10 pve02 pvesr[7234]: error with cfs lock 'file-replication_cfg': no quorum!
Jul 30 17:50:10 pve02 systemd[1]: pvesr.service: Main process exited, code=exited, status=13/n/a
Jul 30 17:50:10 pve02 systemd[1]: Failed to start Proxmox VE replication runner.
Jul 30 17:50:10 pve02 systemd[1]: pvesr.service: Unit entered failed state.
Jul 30 17:50:10 pve02 systemd[1]: pvesr.service: Failed with result 'exit-code'.
Logs



Kann mir dazu vielleicht jemand einen Tipp geben?

Danke.
 
Was steht denn in den logs zu: corosync.service und pve-cluster.service? (`journalctl -u corosync.service -u pve-cluster.service`)
 
Jul 30 17:43:10 pve02 systemd[1]: Starting The Proxmox VE cluster filesystem...
Jul 30 17:43:11 pve02 pmxcfs[3576]: [quorum] crit: quorum_initialize failed: 2
Jul 30 17:43:11 pve02 pmxcfs[3576]: [quorum] crit: can't initialize service
Jul 30 17:43:11 pve02 pmxcfs[3576]: [confdb] crit: cmap_initialize failed: 2
Jul 30 17:43:11 pve02 pmxcfs[3576]: [confdb] crit: can't initialize service
Jul 30 17:43:11 pve02 pmxcfs[3576]: [dcdb] crit: cpg_initialize failed: 2
Jul 30 17:43:11 pve02 pmxcfs[3576]: [dcdb] crit: can't initialize service
Jul 30 17:43:11 pve02 pmxcfs[3576]: [status] crit: cpg_initialize failed: 2
Jul 30 17:43:11 pve02 pmxcfs[3576]: [status] crit: can't initialize service
Jul 30 17:43:13 pve02 systemd[1]: Started The Proxmox VE cluster filesystem.
Jul 30 17:43:13 pve02 systemd[1]: Starting Corosync Cluster Engine...
Jul 30 17:43:13 pve02 corosync[3709]: [MAIN ] Corosync Cluster Engine 3.0.2-dirty starting up
Jul 30 17:43:13 pve02 corosync[3709]: [MAIN ] Corosync built-in features: dbus monitoring watchdog systemd xmlconf snmp pie relro bindnow
Jul 30 17:43:13 pve02 corosync[3709]: [MAIN ] interface section bindnetaddr is used together with nodelist. Nodelist one is going to be used.
Jul 30 17:43:13 pve02 corosync[3709]: [MAIN ] Please migrate config file to nodelist.
Jul 30 17:43:13 pve02 corosync[3709]: [TOTEM ] Initializing transport (Kronosnet).
Jul 30 17:43:13 pve02 corosync[3709]: [TOTEM ] kronosnet crypto initialized: aes256/sha256
Jul 30 17:43:13 pve02 corosync[3709]: [TOTEM ] totemknet initialized
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] common: crypto_nss.so has been loaded from /usr/lib/x86_64-linux-gnu/kronosnet/crypto_nss.so
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync configuration map access [0]
Jul 30 17:43:13 pve02 corosync[3709]: [QB ] server name: cmap
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync configuration service [1]
Jul 30 17:43:13 pve02 corosync[3709]: [QB ] server name: cfg
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
Jul 30 17:43:13 pve02 corosync[3709]: [QB ] server name: cpg
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync profile loading service [4]
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync resource monitoring service [6]
Jul 30 17:43:13 pve02 corosync[3709]: [WD ] Watchdog not enabled by configuration
Jul 30 17:43:13 pve02 corosync[3709]: [WD ] resource load_15min missing a recovery key.
Jul 30 17:43:13 pve02 corosync[3709]: [WD ] resource memory_used missing a recovery key.
Jul 30 17:43:13 pve02 corosync[3709]: [WD ] no resources configured.
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync watchdog service [7]
Jul 30 17:43:13 pve02 corosync[3709]: [QUORUM] Using quorum provider corosync_votequorum
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync vote quorum service v1.0 [5]
Jul 30 17:43:13 pve02 corosync[3709]: [QB ] server name: votequorum
Jul 30 17:43:13 pve02 systemd[1]: Started Corosync Cluster Engine.
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Jul 30 17:43:13 pve02 corosync[3709]: [QB ] server name: quorum
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 0)
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 1 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 1 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 1 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 0)
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 3 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [TOTEM ] A new membership (3:20) was formed. Members joined: 3
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 0)
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 2 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 2 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
Jul 30 17:43:13 pve02 corosync[3709]: [CPG ] downlist left_list: 0 received
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 2 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [QUORUM] Members[1]: 3
Jul 30 17:43:13 pve02 corosync[3709]: [MAIN ] Completed service synchronization, ready to provide service.
Jul 30 17:43:17 pve02 pmxcfs[3576]: [status] notice: update cluster info (cluster name busclust, version = 5)
Jul 30 17:43:17 pve02 pmxcfs[3576]: [dcdb] notice: members: 3/3576
Jul 30 17:43:17 pve02 pmxcfs[3576]: [dcdb] notice: all data is up to date
Jul 30 17:43:17 pve02 pmxcfs[3576]: [status] notice: members: 3/3576
Jul 30 17:43:17 pve02 pmxcfs[3576]: [status] notice: all data is up to date
Jul 30 18:43:10 pve02 pmxcfs[3576]: [dcdb] notice: data verification successful
Jul 30 19:43:10 pve02 pmxcfs[3576]: [dcdb] notice: data verification successful
lines 35-64/64 (END)
-- Logs begin at Tue 2019-07-30 17:42:45 CEST, end at Tue 2019-07-30 20:08:07 CEST. --
Jul 30 17:43:10 pve02 systemd[1]: Starting The Proxmox VE cluster filesystem...
Jul 30 17:43:11 pve02 pmxcfs[3576]: [quorum] crit: quorum_initialize failed: 2
Jul 30 17:43:11 pve02 pmxcfs[3576]: [quorum] crit: can't initialize service
Jul 30 17:43:11 pve02 pmxcfs[3576]: [confdb] crit: cmap_initialize failed: 2
Jul 30 17:43:11 pve02 pmxcfs[3576]: [confdb] crit: can't initialize service
Jul 30 17:43:11 pve02 pmxcfs[3576]: [dcdb] crit: cpg_initialize failed: 2
Jul 30 17:43:11 pve02 pmxcfs[3576]: [dcdb] crit: can't initialize service
Jul 30 17:43:11 pve02 pmxcfs[3576]: [status] crit: cpg_initialize failed: 2
Jul 30 17:43:11 pve02 pmxcfs[3576]: [status] crit: can't initialize service
Jul 30 17:43:13 pve02 systemd[1]: Started The Proxmox VE cluster filesystem.
Jul 30 17:43:13 pve02 systemd[1]: Starting Corosync Cluster Engine...
Jul 30 17:43:13 pve02 corosync[3709]: [MAIN ] Corosync Cluster Engine 3.0.2-dirty starting up
Jul 30 17:43:13 pve02 corosync[3709]: [MAIN ] Corosync built-in features: dbus monitoring watchdog systemd xmlconf snmp pie relro bindnow
Jul 30 17:43:13 pve02 corosync[3709]: [MAIN ] interface section bindnetaddr is used together with nodelist. Nodelist one is going to be used.
Jul 30 17:43:13 pve02 corosync[3709]: [MAIN ] Please migrate config file to nodelist.
Jul 30 17:43:13 pve02 corosync[3709]: [TOTEM ] Initializing transport (Kronosnet).
Jul 30 17:43:13 pve02 corosync[3709]: [TOTEM ] kronosnet crypto initialized: aes256/sha256
Jul 30 17:43:13 pve02 corosync[3709]: [TOTEM ] totemknet initialized
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] common: crypto_nss.so has been loaded from /usr/lib/x86_64-linux-gnu/kronosnet/crypto_nss.so
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync configuration map access [0]
Jul 30 17:43:13 pve02 corosync[3709]: [QB ] server name: cmap
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync configuration service [1]
Jul 30 17:43:13 pve02 corosync[3709]: [QB ] server name: cfg
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
Jul 30 17:43:13 pve02 corosync[3709]: [QB ] server name: cpg
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync profile loading service [4]
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync resource monitoring service [6]
Jul 30 17:43:13 pve02 corosync[3709]: [WD ] Watchdog not enabled by configuration
Jul 30 17:43:13 pve02 corosync[3709]: [WD ] resource load_15min missing a recovery key.
Jul 30 17:43:13 pve02 corosync[3709]: [WD ] resource memory_used missing a recovery key.
Jul 30 17:43:13 pve02 corosync[3709]: [WD ] no resources configured.
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync watchdog service [7]
Jul 30 17:43:13 pve02 corosync[3709]: [QUORUM] Using quorum provider corosync_votequorum
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync vote quorum service v1.0 [5]
Jul 30 17:43:13 pve02 corosync[3709]: [QB ] server name: votequorum
Jul 30 17:43:13 pve02 systemd[1]: Started Corosync Cluster Engine.
Jul 30 17:43:13 pve02 corosync[3709]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Jul 30 17:43:13 pve02 corosync[3709]: [QB ] server name: quorum
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 0)
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 1 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 1 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 1 (passive) best link: 0 (pri: 1)
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 1 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 3 (passive) best link: 0 (pri: 0)
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 3 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [TOTEM ] A new membership (3:20) was formed. Members joined: 3
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 0)
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 2 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 2 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 2 (passive) best link: 0 (pri: 1)
Jul 30 17:43:13 pve02 corosync[3709]: [CPG ] downlist left_list: 0 received
Jul 30 17:43:13 pve02 corosync[3709]: [KNET ] host: host: 2 has no active links
Jul 30 17:43:13 pve02 corosync[3709]: [QUORUM] Members[1]: 3
Jul 30 17:43:13 pve02 corosync[3709]: [MAIN ] Completed service synchronization, ready to provide service.
Jul 30 17:43:17 pve02 pmxcfs[3576]: [status] notice: update cluster info (cluster name busclust, version = 5)
Jul 30 17:43:17 pve02 pmxcfs[3576]: [dcdb] notice: members: 3/3576
Jul 30 17:43:17 pve02 pmxcfs[3576]: [dcdb] notice: all data is up to date
Jul 30 17:43:17 pve02 pmxcfs[3576]: [status] notice: members: 3/3576
Jul 30 17:43:17 pve02 pmxcfs[3576]: [status] notice: all data is up to date
Jul 30 18:43:10 pve02 pmxcfs[3576]: [dcdb] notice: data verification successful
Jul 30 19:43:10 pve02 pmxcfs[3576]: [dcdb] notice: data verification successful
lines 19-64/64 (END)
 
Hmm - PVE 5.X kommt standardmässig mit corosync 2.x - die logs kommen von corosync 3.X.
Corosync 3 muss zwar vor dem update auf PVE 6 installiert werden, allerdings ist das ein eigener schritt in der Upgradeanleitung und ein eigenes repository:
https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0

was sind denn die corosync (und anderen) paketversionen auf allen clusternodes:
* `pveversion -v` auf allen hosts ausführen.
 
Genau das war das Problem, ich hatte am Node2 schon die Paketquelle für Corosync 3 eingetragen und es über die GUI dann mit aktualisiert. Nachdem ich die beiden Anderen nachgezogen habe funktioniert alles wie gewohnt.
Danke für den Support.
 
  • Like
Reactions: Stoiko Ivanov
You must log in or register to reply here.
Top Bottom