I want to join a node to a cluster. But it fails and keeps hanging; I tried to do it again (after reinstall) but its the same :
The systemctl status corosync.service :
It pops up in the webinterface, but as a down device... I did change the /etc/network/interfaces to give the device a fake MAC; (I rebooted before trying)
Code:
root@helium:~# pvecm add xx
The authenticity of host 'xx.xx.xx.xx (xx)' can't be established.
ECDSA key fingerprint is xx
Are you sure you want to continue connecting (yes/no)? yes
root@xx's password:
node helium already defined
copy corosync auth key
stopping pve-cluster service
backup old database
Job for corosync.service failed. See 'systemctl status corosync.service' and ' ' for details.
waiting for quorum...The systemctl status corosync.service :
Code:
oot@helium:~# systemctl status corosync.service
● corosync.service - Corosync Cluster Engine
Loaded: loaded (/lib/systemd/system/corosync.service; enabled)
Active: failed (Result: exit-code) since Mon 2017-04-10 12:56:43 CEST; 1h 12min ago
Process: 3974 ExecStart=/usr/share/corosync/corosync start (code=exited, status=1/FAILURE)
Apr 10 12:55:43 helium corosync[3981]: [MAIN ] Corosync built-in features: augeas systemd pie relro bindnow
Apr 10 12:55:43 helium corosync[3982]: [TOTEM ] Initializing transport (UDP/IP Multicast).
Apr 10 12:55:43 helium corosync[3982]: [TOTEM ] Initializing transmit/receive security (NSS) crypto: aes256 hash: sha1
Apr 10 12:55:43 helium corosync[3982]: [TOTEM ] The network interface [143.169.30.65] is now up.
Apr 10 12:55:43 helium corosync[3982]: [SERV ] Service engine loaded: corosync configuration map access [0]
Apr 10 12:55:43 helium corosync[3982]: [QB ] server name: cmap
Apr 10 12:55:43 helium corosync[3982]: [SERV ] Service engine loaded: corosync configuration service [1]
Apr 10 12:55:43 helium corosync[3982]: [QB ] server name: cfg
Apr 10 12:55:43 helium corosync[3982]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
Apr 10 12:56:43 helium corosync[3974]: Starting Corosync Cluster Engine (corosync): [FAILED]
Apr 10 12:56:43 helium systemd[1]: corosync.service: control process exited, code=exited status=1
Apr 10 12:56:43 helium systemd[1]: Failed to start Corosync Cluster Engine.
Apr 10 12:56:43 helium systemd[1]: Unit corosync.service entered failed state.
Code:
journalctl -xn
-- Logs begin at Mon 2017-04-10 12:26:08 CEST, end at Mon 2017-04-10 14:11:01 CEST. --
Apr 10 14:03:01 helium cron[2237]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Apr 10 14:04:01 helium cron[2237]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Apr 10 14:05:01 helium cron[2237]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Apr 10 14:06:01 helium cron[2237]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Apr 10 14:07:01 helium cron[2237]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Apr 10 14:08:01 helium cron[2237]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Apr 10 14:08:35 helium systemd-timesyncd[1674]: interval/delta/delay/jitter/drift 2048s/-0.001s/0.016s/0.001s/-4ppm
Apr 10 14:09:01 helium cron[2237]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Apr 10 14:10:01 helium cron[2237]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)
Apr 10 14:11:01 helium cron[2237]: (*system*vzdump) CAN'T OPEN SYMLINK (/etc/cron.d/vzdump)It pops up in the webinterface, but as a down device... I did change the /etc/network/interfaces to give the device a fake MAC; (I rebooted before trying)
Code:
cat /etc/network/interfaces
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet manual
pre-up ifconfig eth0 hw ether 00:1a:ac:22:06:d8
auto vmbr0
iface vmbr0 inet static
address 1XX
netmask 255.255.0.0
gateway XX
#hwaddress ether 00:1a:8c:22:06:d8
bridge_ports eth0
bridge_stp off
bridge_fd 0
Code: