join in cluster failed

H

haiwan

Well-Known Member
Apr 23, 2019
249
1
58
37
Establishing API connection with host '172.16.10.140'
Login succeeded.
Request addition of this node
Join request OK, finishing setup locally
stopping pve-cluster service
backup old database to '/var/lib/pve-cluster/backup/config-1556116060.sql.gz'
waiting for quorum...
 
()


Task viewer: 创建集群

输出状态

停止
Corosync Cluster Engine Authentication key generator.
Gathering 1024 bits for key from /dev/urandom.
Writing corosync key to /etc/corosync/authkey.
Writing corosync config to /etc/pve/corosync.conf
Restart corosync and cluster filesystem
TASK OK
 
root@pve140:~# journalctl -u corosync
-- Logs begin at Thu 2019-04-25 02:24:01 CST, end at Thu 2019-04-25 22:29:10 CST. --
Apr 25 02:24:06 pve140 systemd[1]: Starting Corosync Cluster Engine...
Apr 25 02:24:06 pve140 corosync[1953]: [MAIN ] Corosync Cluster Engine ('2.4.4-dirty'): started and ready to provide service.
Apr 25 02:24:06 pve140 corosync[1953]: [MAIN ] Corosync built-in features: dbus rdma monitoring watchdog systemd xmlconf qdevices qnetd snmp pie relro bindnow
Apr 25 02:24:06 pve140 corosync[1953]: notice [MAIN ] Corosync Cluster Engine ('2.4.4-dirty'): started and ready to provide service.
Apr 25 02:24:06 pve140 corosync[1953]: info [MAIN ] Corosync built-in features: dbus rdma monitoring watchdog systemd xmlconf qdevices qnetd snmp pie relro bindnow
Apr 25 02:24:06 pve140 corosync[1953]: warning [MAIN ] interface section bindnetaddr is used together with nodelist. Nodelist one is going to be used.
Apr 25 02:24:06 pve140 corosync[1953]: warning [MAIN ] Please migrate config file to nodelist.
Apr 25 02:24:06 pve140 corosync[1953]: [MAIN ] interface section bindnetaddr is used together with nodelist. Nodelist one is going to be used.
Apr 25 02:24:06 pve140 corosync[1953]: [MAIN ] Please migrate config file to nodelist.
Apr 25 02:24:06 pve140 corosync[1953]: notice [TOTEM ] Initializing transport (UDP/IP Multicast).
Apr 25 02:24:06 pve140 corosync[1953]: notice [TOTEM ] Initializing transmit/receive security (NSS) crypto: aes256 hash: sha1
Apr 25 02:24:06 pve140 corosync[1953]: [TOTEM ] Initializing transport (UDP/IP Multicast).
Apr 25 02:24:06 pve140 corosync[1953]: [TOTEM ] Initializing transmit/receive security (NSS) crypto: aes256 hash: sha1
Apr 25 02:24:06 pve140 corosync[1953]: notice [TOTEM ] The network interface [192.168.100.140] is now up.
Apr 25 02:24:06 pve140 corosync[1953]: [TOTEM ] The network interface [192.168.100.140] is now up.
Apr 25 02:24:06 pve140 corosync[1953]: notice [SERV ] Service engine loaded: corosync configuration map access [0]
Apr 25 02:24:06 pve140 corosync[1953]: info [QB ] server name: cmap
Apr 25 02:24:06 pve140 corosync[1953]: notice [SERV ] Service engine loaded: corosync configuration service [1]
Apr 25 02:24:06 pve140 corosync[1953]: info [QB ] server name: cfg
Apr 25 02:24:06 pve140 corosync[1953]: notice [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
Apr 25 02:24:06 pve140 corosync[1953]: info [QB ] server name: cpg
Apr 25 02:24:06 pve140 corosync[1953]: notice [SERV ] Service engine loaded: corosync profile loading service [4]
Apr 25 02:24:06 pve140 corosync[1953]: notice [SERV ] Service engine loaded: corosync resource monitoring service [6]
Apr 25 02:24:06 pve140 corosync[1953]: warning [WD ] Watchdog not enabled by configuration
Apr 25 02:24:06 pve140 corosync[1953]: [SERV ] Service engine loaded: corosync configuration map access [0]
Apr 25 02:24:06 pve140 corosync[1953]: warning [WD ] resource load_15min missing a recovery key.
Apr 25 02:24:06 pve140 corosync[1953]: warning [WD ] resource memory_used missing a recovery key.
Apr 25 02:24:06 pve140 corosync[1953]: info [WD ] no resources configured.
Apr 25 02:24:06 pve140 corosync[1953]: notice [SERV ] Service engine loaded: corosync watchdog service [7]
Apr 25 02:24:06 pve140 corosync[1953]: notice [QUORUM] Using quorum provider corosync_votequorum
Apr 25 02:24:06 pve140 corosync[1953]: notice [SERV ] Service engine loaded: corosync vote quorum service v1.0 [5]
Apr 25 02:24:06 pve140 corosync[1953]: info [QB ] server name: votequorum
Apr 25 02:24:06 pve140 corosync[1953]: notice [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Apr 25 02:24:06 pve140 corosync[1953]: info [QB ] server name: quorum
Apr 25 02:24:06 pve140 corosync[1953]: notice [TOTEM ] A new membership (192.168.100.140:360) was formed. Members joined: 1
Apr 25 02:24:06 pve140 corosync[1953]: warning [CPG ] downlist left_list: 0 received
Apr 25 02:24:06 pve140 corosync[1953]: notice [QUORUM] Members[1]: 1
Apr 25 02:24:06 pve140 corosync[1953]: notice [MAIN ] Completed service synchronization, ready to provide service.
Apr 25 02:24:06 pve140 systemd[1]: Started Corosync Cluster Engine.
Apr 25 02:24:06 pve140 corosync[1953]: [QB ] server name: cmap
Apr 25 02:24:06 pve140 corosync[1953]: [SERV ] Service engine loaded: corosync configuration service [1]
Apr 25 02:24:06 pve140 corosync[1953]: [QB ] server name: cfg
Apr 25 02:24:06 pve140 corosync[1953]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
Apr 25 02:24:06 pve140 corosync[1953]: [QB ] server name: cpg
Apr 25 02:24:06 pve140 corosync[1953]: [SERV ] Service engine loaded: corosync profile loading service [4]
Apr 25 02:24:06 pve140 corosync[1953]: [SERV ] Service engine loaded: corosync resource monitoring service [6]
Apr 25 02:24:06 pve140 corosync[1953]: [WD ] Watchdog not enabled by configuration
Apr 25 02:24:06 pve140 corosync[1953]: [WD ] resource load_15min missing a recovery key.
Apr 25 02:24:06 pve140 corosync[1953]: [WD ] resource memory_used missing a recovery key.
Apr 25 02:24:06 pve140 corosync[1953]: [WD ] no resources configured.
Apr 25 02:24:06 pve140 corosync[1953]: [SERV ] Service engine loaded: corosync watchdog service [7]
Apr 25 02:24:06 pve140 corosync[1953]: [QUORUM] Using quorum provider corosync_votequorum
Apr 25 02:24:06 pve140 corosync[1953]: [SERV ] Service engine loaded: corosync vote quorum service v1.0 [5]
Apr 25 02:24:06 pve140 corosync[1953]: [QB ] server name: votequorum
Apr 25 02:24:06 pve140 corosync[1953]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Apr 25 02:24:06 pve140 corosync[1953]: [QB ] server name: quorum
Apr 25 02:24:06 pve140 corosync[1953]: [TOTEM ] A new membership (192.168.100.140:360) was formed. Members joined: 1
Apr 25 02:24:06 pve140 corosync[1953]: [CPG ] downlist left_list: 0 received
Apr 25 02:24:06 pve140 corosync[1953]: [QUORUM] Members[1]: 1
Apr 25 02:24:06 pve140 corosync[1953]: [MAIN ] Completed service synchronization, ready to provide service
Stoiko Ivanov said:
Please post in English if possible (maybe using google translate or similar).

I'm not sure I got all necessary information but:



* cluster-joins hanging there usually happen because of network issues - see https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_cluster_network (and run the `omping` commands)

* check the logs of corosync: `journalctl -u corosync`



hope this helps!
Click to expand...
 
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