[SOLVED] pvecm addnode = 400 Parameter verification failed

Dec 7, 2017
32
5
13
44
Hallo,

ich möchte einen Cluster aufbauen und scheitere beim hinzufügen von der Node B zu Node A

Code:
pvecm addnode 192.168.1.11
400 Parameter verification failed.
node: invalid format - value does not look like a valid node name

pvecm addnode <node> [OPTIONS]

Code:
pveversion -v
proxmox-ve: 5.1-43 (running kernel: 4.15.17-1-pve)
pve-manager: 5.1-52 (running version: 5.1-52/ba597a64)
pve-kernel-4.13: 5.1-44
pve-kernel-4.15: 5.1-4
pve-kernel-4.15.17-1-pve: 4.15.17-8
pve-kernel-4.13.16-2-pve: 4.13.16-48
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-31
libpve-guest-common-perl: 2.0-15
libpve-http-server-perl: 2.0-8
libpve-storage-perl: 5.0-21
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-17
pve-cluster: 5.0-27
pve-container: 2.0-22
pve-docs: 5.1-17
pve-firewall: 3.0-8
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-4
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-3
qemu-server: 5.0-25
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.8-pve1~bpo9

Was ist genau das Problem? Ich habe auch einmal den FQDN von dem Host probiert, aber erhalte die gleiche Fehlermeldung.

Besten Dank im voraus
 

Besten Dank Tom,

ich konnte den Cluster initial aktivieren:

pvecm create -votes 2 cluster

Join request OK, finishing setup locally
stopping pve-cluster service
backup old database to '/var/lib/pve-cluster/backup/config-1526459719.sql.gz'
waiting for quorum...OK
(re)generate node files
generate new node certificate
merge authorized SSH keys and known hosts
generated new node certificate, restart pveproxy and pvedaemon services
successfully added node 'snoopy-12' to cluster

Aber nach kurzer Zeit gibt es ein Problem und der Cluster funktioniert nicht mehr:

May 16 10:35:00 snoopy-11 systemd[1]: Started Proxmox VE replication runner.
May 16 10:35:18 snoopy-11 pvedaemon[2473]: <root@pam> successful auth for user 'root@pam'
May 16 10:35:18 snoopy-11 pvedaemon[2473]: <root@pam> adding node snoopy-12 to cluster
May 16 10:35:18 snoopy-11 pmxcfs[3127]: [dcdb] notice: wrote new corosync config '/etc/corosync/corosync.conf' (version = 2)
May 16 10:35:18 snoopy-11 corosync[3144]: notice [CFG ] Config reload requested by node 1
May 16 10:35:18 snoopy-11 corosync[3144]: [CFG ] Config reload requested by node 1
May 16 10:35:18 snoopy-11 pmxcfs[3127]: [status] notice: update cluster info (cluster name nsdcluster, version = 2)
May 16 10:35:20 snoopy-11 corosync[3144]: notice [TOTEM ] A new membership (192.168.1.11:8) was formed. Members joined: 2
May 16 10:35:20 snoopy-11 corosync[3144]: [TOTEM ] A new membership (192.168.1.11:8) was formed. Members joined: 2
May 16 10:35:20 snoopy-11 corosync[3144]: warning [CPG ] downlist left_list: 0 received
May 16 10:35:20 snoopy-11 corosync[3144]: warning [CPG ] downlist left_list: 0 received
May 16 10:35:20 snoopy-11 corosync[3144]: [CPG ] downlist left_list: 0 received
May 16 10:35:20 snoopy-11 corosync[3144]: [CPG ] downlist left_list: 0 received
May 16 10:35:20 snoopy-11 corosync[3144]: notice [QUORUM] Members[2]: 1 2
May 16 10:35:20 snoopy-11 corosync[3144]: notice [MAIN ] Completed service synchronization, ready to provide service.
May 16 10:35:20 snoopy-11 corosync[3144]: [QUORUM] Members[2]: 1 2
May 16 10:35:20 snoopy-11 corosync[3144]: [MAIN ] Completed service synchronization, ready to provide service.
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [dcdb] notice: members: 1/3127, 2/3087
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [dcdb] notice: starting data syncronisation
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [status] notice: members: 1/3127, 2/3087
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [status] notice: starting data syncronisation
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [dcdb] notice: received sync request (epoch 1/3127/00000002)
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [status] notice: received sync request (epoch 1/3127/00000002)
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [dcdb] notice: received all states
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [dcdb] notice: leader is 1/3127
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [dcdb] notice: synced members: 1/3127
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [dcdb] notice: start sending inode updates
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [dcdb] notice: sent all (33) updates
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [dcdb] notice: all data is up to date
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [status] notice: received all states
May 16 10:35:25 snoopy-11 pmxcfs[3127]: [status] notice: all data is up to date
May 16 10:35:27 snoopy-11 pmxcfs[3127]: [status] notice: received log
May 16 10:35:39 snoopy-11 pvedaemon[2473]: <root@pam> successful auth for user 'root@pam'
May 16 10:36:00 snoopy-11 systemd[1]: Starting Proxmox VE replication runner...
May 16 10:36:00 snoopy-11 systemd[1]: Started Proxmox VE replication runner.
May 16 10:36:18 snoopy-11 pmxcfs[3127]: [status] notice: received log
May 16 10:37:00 snoopy-11 systemd[1]: Starting Proxmox VE replication runner...
May 16 10:37:00 snoopy-11 systemd[1]: Started Proxmox VE replication runner.
May 16 10:38:00 snoopy-11 systemd[1]: Starting Proxmox VE replication runner...
May 16 10:38:00 snoopy-11 systemd[1]: Started Proxmox VE replication runner.
May 16 10:38:56 snoopy-11 corosync[3144]: error [TOTEM ] FAILED TO RECEIVE
May 16 10:38:56 snoopy-11 corosync[3144]: [TOTEM ] FAILED TO RECEIVE
May 16 10:38:57 snoopy-11 corosync[3144]: notice [TOTEM ] A new membership (192.168.1.11:12) was formed. Members left: 2
May 16 10:38:57 snoopy-11 corosync[3144]: notice [TOTEM ] Failed to receive the leave message. failed: 2
May 16 10:38:57 snoopy-11 corosync[3144]: [TOTEM ] A new membership (192.168.1.11:12) was formed. Members left: 2
May 16 10:38:57 snoopy-11 corosync[3144]: warning [CPG ] downlist left_list: 1 received
May 16 10:38:57 snoopy-11 corosync[3144]: notice [QUORUM] Members[1]: 1
May 16 10:38:57 snoopy-11 corosync[3144]: notice [MAIN ] Completed service synchronization, ready to provide service.
May 16 10:38:57 snoopy-11 corosync[3144]: [TOTEM ] Failed to receive the leave message. failed: 2
May 16 10:38:57 snoopy-11 corosync[3144]: [CPG ] downlist left_list: 1 received
May 16 10:38:57 snoopy-11 corosync[3144]: [QUORUM] Members[1]: 1
May 16 10:38:57 snoopy-11 corosync[3144]: [MAIN ] Completed service synchronization, ready to provide service.
May 16 10:38:57 snoopy-11 pmxcfs[3127]: [dcdb] notice: members: 1/3127
May 16 10:38:57 snoopy-11 pmxcfs[3127]: [status] notice: members: 1/3127

Status von snoopy-12

root@snoopy-12:~# pvecm status
Quorum information
------------------
Date: Wed May 16 10:39:16 2018
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000002
Ring ID: 2/64
Quorate: No

Votequorum information
----------------------
Expected votes: 3
Highest expected: 3
Total votes: 1
Quorum: 2 Activity blocked
Flags:

Membership information
----------------------
Nodeid Votes Name
0x00000002 1 192.168.1.12 (local)
 

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!

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!