Fehlermeldung bei Einrichtung von ProxMoxVE Cluster

J

julianl11

New Member
Feb 24, 2026
3
0
1
Hallo,
ich habe zwei Laptops auf beiden läuft ProxMoxVE, auf einem der Laptops sind schon mehrere Vm´s und LXC Container. Auf diesem habe ich ein Cluster erstellt und wollte mit dem zweiten neu aufgesetzten ProxMoxVE Server dem Cluster beitreten. Verbinde ich mich aber mit dem Cluster bekomme ich folgende Fehlermeldung auf meinem MainNode:
'/etc/pve/nodes/pve2/pve-ssl.pem' does not exist! (500)
und auf pve2 bekomme ich fast dieselbe Fehlermeldung:
'/etc/pve/nodes/pve/pve-ssl.pem' does not exist! (500)

Ich habe schon mehrere Sachen versucht wie z.B das neu generieren der Certificate dem hinzufügen des jeweiligen anderen Server in /etc/hosts
Doch leider hat dies und andere Sachen das Problem nicht gelöst. Ich versuche seit 2 Tagen das Cluster zum laufen zu bringen, jedoch ohne Erfolg.

Ich hoffe in diesem Forum kann mir jemand helfen. (Ich bin noch recht neu bei ProxMoxVE und auch im HomeLab Bereich)

MFG
Julian
 
Last edited:
Willkommen und als erstes ein Hinweis: die Software heißt Proxmox VE und das wird auch so geschrieben. ProxMox existiert nicht.

Bitte stelle uns noch (in CODE Tags) die Ausgabe von pveversion -v von beiden Maschinen zur Verfügung, als auch die Verzeichnisinhalte von /etc/pve/nodes/
 
Entschuldigen Sie die falsche Schreibweiße, wie gesagt bin ich noch relativ neu.
Anbei die gefragten Inhalte:

pve:

Code: 
root@pve:~# ls -l /etc/pve/nodes/
total 0
drwxr-xr-x 2 root www-data 0 Jan 18 15:37 pve
drwxr-xr-x 2 root www-data 0 Feb 24 16:14 pve2


Code: 
root@pve:~# pveversion -v
proxmox-ve: 9.1.0 (running kernel: 6.17.4-2-pve)
pve-manager: 9.1.6 (running version: 9.1.6/71482d1833ded40a)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.17.4-2-pve-signed: 6.17.4-2
proxmox-kernel-6.17: 6.17.4-2
proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1
ceph-fuse: 19.2.3-pve2
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.4.1-1+pve1
ifupdown2: 3.3.0-1+pmx12
intel-microcode: 3.20251111.1~deb13u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.2
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.5
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.0.7
libpve-cluster-perl: 9.0.7
libpve-common-perl: 9.1.7
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.2.5
libpve-rs-perl: 0.11.4
libpve-storage-perl: 9.1.0
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-4
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.1.4-1
proxmox-backup-file-restore: 4.1.4-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.1
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-widget-toolkit: 5.1.6
pve-cluster: 9.0.7
pve-container: 6.1.2
pve-docs: 9.1.2
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.18-1
pve-ha-manager: 5.1.0
pve-i18n: 3.6.6
pve-qemu-kvm: 10.1.2-7
pve-xtermjs: 5.5.0-3
qemu-server: 9.1.4
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve3
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1


pve2:

Code: 
root@pve2:~# ls -l /etc/pve/nodes/
total 0
drwxr-xr-x 2 root www-data 0 Feb 25 14:48 pve2


Code: 
root@pve2:~# pveversion -v
proxmox-ve: 9.1.0 (running kernel: 6.17.2-1-pve)
pve-manager: 9.1.6 (running version: 9.1.6/71482d1833ded40a)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.17.2-1-pve-signed: 6.17.2-1
proxmox-kernel-6.17: 6.17.2-1
ceph-fuse: 19.2.3-pve2
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.4.1-1+pve1
ifupdown2: 3.3.0-1+pmx12
intel-microcode: 3.20251111.1~deb13u1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.2
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.5
libpve-apiclient-perl: 3.4.2
libpve-cluster-api-perl: 9.0.7
libpve-cluster-perl: 9.0.7
libpve-common-perl: 9.1.7
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.5
libpve-network-perl: 1.2.5
libpve-rs-perl: 0.11.4
libpve-storage-perl: 9.1.0
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-4
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.1.4-1
proxmox-backup-file-restore: 4.1.4-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.2.1
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.3
proxmox-widget-toolkit: 5.1.6
pve-cluster: 9.0.7
pve-container: 6.1.2
pve-docs: 9.1.2
pve-edk2-firmware: 4.2025.05-2
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.4
pve-firmware: 3.18-1
pve-ha-manager: 5.1.0
pve-i18n: 3.6.6
pve-qemu-kvm: 10.1.2-7
pve-xtermjs: 5.5.0-3
qemu-server: 9.1.4
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve3
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1
 
Das Clusterdateisystem in /etc/pve ist also auf jeden Fall in einem komischen Zustand. Hier wäre die gesamte Ausgabe des ersten fehlgeschlagenen Cluster-Joins interessant, alles danach können Folgefehler sein. Hast du die Ausgabe noch?
 
Nein diese habe ich leider nicht mehr. Anbei befindet sich mein aktueller log des pve-clusters und corosync

Code: 
Feb 25 14:34:33 pve2 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Feb 25 14:34:33 pve2 pmxcfs[833]: [main] notice: resolved node name 'pve2' to '192.168.178.33' for default node IP address
Feb 25 14:34:33 pve2 pmxcfs[833]: [main] notice: resolved node name 'pve2' to '192.168.178.33' for default node IP address
Feb 25 14:34:34 pve2 systemd[1]: Started pve-cluster.service - The Proxmox VE cluster filesystem.
Feb 25 14:34:46 pve2 pmxcfs[860]: [status] notice: could not create directory /var/lib/rrdcached/db/pve-node-9.0: No such file or directory
Feb 25 14:34:46 pve2 pmxcfs[860]: [status] notice: could not create directory /var/lib/rrdcached/db/pve-storage-9.0: No such file or directory
Feb 25 14:34:46 pve2 pmxcfs[860]: [status] notice: could not create directory /var/lib/rrdcached/db/pve-storage-9.0/pve2: No such file or directory
Feb 25 14:46:26 pve2 systemd[1]: Stopping pve-cluster.service - The Proxmox VE cluster filesystem...
Feb 25 14:46:26 pve2 pmxcfs[860]: [main] notice: teardown filesystem
Feb 25 14:46:26 pve2 pmxcfs[860]: [main] notice: exit proxmox configuration filesystem (0)
Feb 25 14:46:26 pve2 systemd[1]: pve-cluster.service: Deactivated successfully.
Feb 25 14:46:26 pve2 systemd[1]: Stopped pve-cluster.service - The Proxmox VE cluster filesystem.
Feb 25 14:46:26 pve2 systemd[1]: pve-cluster.service: Consumed 648ms CPU time, 69.4M memory peak.
Feb 25 14:46:26 pve2 systemd[1]: Starting pve-cluster.service - The Proxmox VE cluster filesystem...
Feb 25 14:46:26 pve2 pmxcfs[12115]: [main] notice: resolved node name 'pve2' to '192.168.178.33' for default node IP address
Feb 25 14:46:26 pve2 pmxcfs[12115]: [main] notice: resolved node name 'pve2' to '192.168.178.33' for default node IP address
Feb 25 14:46:26 pve2 pmxcfs[12117]: [quorum] crit: quorum_initialize failed: CS_ERR_LIBRARY (failed to connect to corosync)
Feb 25 14:46:26 pve2 pmxcfs[12117]: [quorum] crit: can't initialize service
Feb 25 14:46:26 pve2 pmxcfs[12117]: [confdb] crit: cmap_initialize failed: CS_ERR_LIBRARY (failed to connect to corosync)
Feb 25 14:46:26 pve2 pmxcfs[12117]: [confdb] crit: can't initialize service
Feb 25 14:46:26 pve2 pmxcfs[12117]: [dcdb] crit: cpg_initialize failed: CS_ERR_LIBRARY (failed to connect to corosync)
Feb 25 14:46:26 pve2 pmxcfs[12117]: [dcdb] crit: can't initialize service
Feb 25 14:46:26 pve2 pmxcfs[12117]: [status] crit: cpg_initialize failed: CS_ERR_LIBRARY (failed to connect to corosync)
Feb 25 14:46:26 pve2 pmxcfs[12117]: [status] crit: can't initialize service
Feb 25 14:46:27 pve2 systemd[1]: Started pve-cluster.service - The Proxmox VE cluster filesystem.
Feb 25 14:46:32 pve2 pmxcfs[12117]: [status] notice: update cluster info (cluster name  PVE-Cluster, version = 4)
Feb 25 14:46:32 pve2 pmxcfs[12117]: [dcdb] notice: members: 2/12117
Feb 25 14:46:32 pve2 pmxcfs[12117]: [dcdb] notice: all data is up to date
Feb 25 14:46:32 pve2 pmxcfs[12117]: [status] notice: members: 2/12117
Feb 25 14:46:32 pve2 pmxcfs[12117]: [status] notice: all data is up to date
Feb 25 14:48:51 pve2 pmxcfs[12117]: [status] notice: node has quorum
Feb 25 15:46:26 pve2 pmxcfs[12117]: [dcdb] notice: data verification successful
Feb 25 16:06:18 pve2 pmxcfs[12117]: [confdb] crit: cmap_dispatch failed: 2
Feb 25 16:06:18 pve2 pmxcfs[12117]: [quorum] crit: quorum_dispatch failed: CS_ERR_LIBRARY
Feb 25 16:06:18 pve2 pmxcfs[12117]: [status] notice: node lost quorum
Feb 25 16:06:18 pve2 pmxcfs[12117]: [dcdb] crit: cpg_dispatch failed: CS_ERR_LIBRARY
Feb 25 16:06:18 pve2 pmxcfs[12117]: [dcdb] crit: cpg_leave failed: CS_ERR_LIBRARY

Feb 25 14:34:34 pve2 systemd[1]: corosync.service - Corosync Cluster Engine was skipped because of an unmet condition check (ConditionPathExists=/etc/corosy>
Feb 25 14:46:26 pve2 systemd[1]: Starting corosync.service - Corosync Cluster Engine...
Feb 25 14:46:26 pve2 (corosync)[12114]: corosync.service: Referenced but unset environment variable evaluates to an empty string: COROSYNC_OPTIONS
Feb 25 14:46:26 pve2 corosync[12114]:   [MAIN  ] Corosync Cluster Engine  starting up
Feb 25 14:46:26 pve2 corosync[12114]:   [MAIN  ] Corosync built-in features: dbus monitoring watchdog augeas systemd xmlconf vqsim nozzle snmp pie relro bin>
Feb 25 14:46:26 pve2 corosync[12114]:   [TOTEM ] Initializing transport (Kronosnet).
Feb 25 14:46:27 pve2 corosync[12114]:   [TOTEM ] totemknet initialized
Feb 25 14:46:27 pve2 corosync[12114]:   [KNET  ] pmtud: MTU manually set to: 0
Feb 25 14:46:27 pve2 corosync[12114]:   [KNET  ] common: crypto_nss.so has been loaded from /usr/lib/x86_64-linux-gnu/kronosnet/crypto_nss.so
Feb 25 14:46:27 pve2 corosync[12114]:   [SERV  ] Service engine loaded: corosync configuration map access [0]
Feb 25 14:46:27 pve2 corosync[12114]:   [QB    ] server name: cmap
Feb 25 14:46:27 pve2 corosync[12114]:   [SERV  ] Service engine loaded: corosync configuration service [1]
Feb 25 14:46:27 pve2 corosync[12114]:   [QB    ] server name: cfg
Feb 25 14:46:27 pve2 corosync[12114]:   [SERV  ] Service engine loaded: corosync cluster closed process group service v1.01 [2]
Feb 25 14:46:27 pve2 corosync[12114]:   [QB    ] server name: cpg
Feb 25 14:46:27 pve2 corosync[12114]:   [SERV  ] Service engine loaded: corosync profile loading service [4]
Feb 25 14:46:27 pve2 corosync[12114]:   [SERV  ] Service engine loaded: corosync resource monitoring service [6]
Feb 25 14:46:27 pve2 corosync[12114]:   [WD    ] Watchdog not enabled by configuration
Feb 25 14:46:27 pve2 corosync[12114]:   [WD    ] resource load_15min missing a recovery key.
Feb 25 14:46:27 pve2 corosync[12114]:   [WD    ] resource memory_used missing a recovery key.
Feb 25 14:46:27 pve2 corosync[12114]:   [WD    ] no resources configured.
Feb 25 14:46:27 pve2 corosync[12114]:   [SERV  ] Service engine loaded: corosync watchdog service [7]
Feb 25 14:46:27 pve2 corosync[12114]:   [QUORUM] Using quorum provider corosync_votequorum
Feb 25 14:46:27 pve2 corosync[12114]:   [SERV  ] Service engine loaded: corosync vote quorum service v1.0 [5]
Feb 25 14:46:27 pve2 corosync[12114]:   [QB    ] server name: votequorum
Feb 25 14:46:27 pve2 corosync[12114]:   [SERV  ] Service engine loaded: corosync cluster quorum service v0.1 [3]
Feb 25 14:46:27 pve2 corosync[12114]:   [QB    ] server name: quorum
Feb 25 14:46:27 pve2 corosync[12114]:   [TOTEM ] Configuring link 0
Feb 25 14:46:27 pve2 corosync[12114]:   [TOTEM ] Configured link number 0: local addr: 192.168.178.33, port=5405
Feb 25 14:46:27 pve2 corosync[12114]:   [KNET  ] host: host: 1 (passive) best link: 0 (pri: 0)
Feb 25 14:46:27 pve2 corosync[12114]:   [KNET  ] host: host: 1 has no active links
Feb 25 14:46:27 pve2 corosync[12114]:   [KNET  ] host: host: 1 (passive) best link: 0 (pri: 1)
Feb 25 14:46:27 pve2 corosync[12114]:   [KNET  ] host: host: 1 has no active links
Feb 25 14:46:27 pve2 corosync[12114]:   [KNET  ] host: host: 1 (passive) best link: 0 (pri: 1)
Feb 25 14:46:27 pve2 corosync[12114]:   [KNET  ] host: host: 1 has no active links
Feb 25 14:46:27 pve2 corosync[12114]:   [KNET  ] link: Resetting MTU for link 0 because host 2 joined
Feb 25 14:46:27 pve2 corosync[12114]:   [QUORUM] Sync members[1]: 2

Wobei ich in diesem Abschnitt viele Fehler erhalte:

Code: 
Feb 25 14:46:26 pve2 pmxcfs[12117]: [quorum] crit: quorum_initialize failed: CS_ERR_LIBRARY (failed to connect to corosync)
Feb 25 14:46:26 pve2 pmxcfs[12117]: [quorum] crit: can't initialize service
Feb 25 14:46:26 pve2 pmxcfs[12117]: [confdb] crit: cmap_initialize failed: CS_ERR_LIBRARY (failed to connect to corosync)
Feb 25 14:46:26 pve2 pmxcfs[12117]: [confdb] crit: can't initialize service
Feb 25 14:46:26 pve2 pmxcfs[12117]: [dcdb] crit: cpg_initialize failed: CS_ERR_LIBRARY (failed to connect to corosync)
Feb 25 14:46:26 pve2 pmxcfs[12117]: [dcdb] crit: can't initialize service
Feb 25 14:46:26 pve2 pmxcfs[12117]: [status] crit: cpg_initialize failed: CS_ERR_LIBRARY (failed to connect to corosync)
Feb 25 14:46:26 pve2 pmxcfs[12117]: [status] crit: can't initialize service
Feb 25 14:46:27 pve2 systemd[1]: Started pve-cluster.service - The Proxmox VE cluster filesystem.
Feb 25 14:46:32 pve2 pmxcfs[12117]: [status] notice: update cluster info (cluster name  PVE-Cluster, version = 4)
Feb 25 14:46:32 pve2 pmxcfs[12117]: [dcdb] notice: members: 2/12117
Feb 25 14:46:32 pve2 pmxcfs[12117]: [dcdb] notice: all data is up to date
Feb 25 14:46:32 pve2 pmxcfs[12117]: [status] notice: members: 2/12117
Feb 25 14:46:32 pve2 pmxcfs[12117]: [status] notice: all data is up to date
Feb 25 14:48:51 pve2 pmxcfs[12117]: [status] notice: node has quorum
Feb 25 15:46:26 pve2 pmxcfs[12117]: [dcdb] notice: data verification successful
Feb 25 16:06:18 pve2 pmxcfs[12117]: [confdb] crit: cmap_dispatch failed: 2
Feb 25 16:06:18 pve2 pmxcfs[12117]: [quorum] crit: quorum_dispatch failed: CS_ERR_LIBRARY
Feb 25 16:06:18 pve2 pmxcfs[12117]: [status] notice: node lost quorum
Feb 25 16:06:18 pve2 pmxcfs[12117]: [dcdb] crit: cpg_dispatch failed: CS_ERR_LIBRARY
Feb 25 16:06:18 pve2 pmxcfs[12117]: [dcdb] crit: cpg_leave failed: CS_ERR_LIBRARY
 
You must log in or register to reply here.
Top Bottom
Back