[SOLVED] Node IPs different in /etc/pve/corosync.conf & /etc/pve/.members

Nov 17, 2023
187
6
18
Moin,
ich habe heute versucht meinen ersten Cluster zu erstellen.

Leider hat das nicht wirklich geklappt.

Node IPs different in /etc/pve/corosync.conf & /etc/pve/.members

In /etc/pve/corosync.conf stehen die Adressen des ClusterNetzwerk 192.168.20.xx

und in der /etc/pve/.members steht nur die Adresse des eigenen Node 192.168.2.xx aus dem Verwaltungsnetzwerk.

Wie kann ich das wieder anpassen.

Also ich hatte vorher extra 2 Netzwerk angelegt

Eine vmbr0 mit dem 192.168.2.xx aus dem Verwaltungsnetzwerk.

und die IP Adresse direkt auf die Netzwekrkarte aus dem ClusterNetzwerk 192.168.20.xx

In der /etc/pve/.members steht immer noch die eine

{
"nodename": "node1",
"version": 3,
"cluster": { "name": "cluster", "version": 2, "nodes": 2, "quorate": 0 },
"nodelist": {
"node1": { "id": 1, "online": 1, "ip": "192.168.2.14"},
"node2": { "id": 2, "online": 0}
}
}

Zum einen ist das die falsche IP Adresse und es steht nur eine IP Adresse darin.

Hat jemand eine Idee wie ich wieder hin bekommen?

Danke
 
Hier die Daten aus dem Log:

Nov 28 19:20:55 node1 pveproxy[1205]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:20:55 node1 pveproxy[1204]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:21:25 node1 pveproxy[1205]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:21:45 node1 sshd[3186]: Accepted password for root from 192.168.2.15 port 38742 ssh2
Nov 28 19:21:45 node1 sshd[3186]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Nov 28 19:21:45 node1 systemd-logind[677]: New session 10 of user root.
Nov 28 19:21:45 node1 systemd[1]: Started session-10.scope - Session 10 of User root.
Nov 28 19:21:45 node1 sshd[3186]: pam_env(sshd:session): deprecated reading of user environment enabled
Nov 28 19:21:45 node1 sshd[3186]: Received disconnect from 192.168.2.15 port 38742:11: disconnected by user
Nov 28 19:21:45 node1 sshd[3186]: Disconnected from user root 192.168.2.15 port 38742
Nov 28 19:21:45 node1 sshd[3186]: pam_unix(sshd:session): session closed for user root
Nov 28 19:21:45 node1 systemd[1]: session-10.scope: Deactivated successfully.
Nov 28 19:21:45 node1 systemd-logind[677]: Session 10 logged out. Waiting for processes to exit.
Nov 28 19:21:45 node1 systemd-logind[677]: Removed session 10.
Nov 28 19:21:55 node1 pveproxy[1205]: proxy detected vanished client connection
Nov 28 19:21:55 node1 pveproxy[1206]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:21:57 node1 pvedaemon[1089]: <root@pam> successful auth for user 'root@pam'
Nov 28 19:21:57 node1 pveproxy[1206]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:21:57 node1 pveproxy[1205]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:22:02 node1 pveproxy[1204]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:22:04 node1 pveproxy[1205]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:22:04 node1 pveproxy[1206]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:22:24 node1 pveproxy[1205]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:22:25 node1 pveproxy[1206]: proxy detected vanished client connection
Nov 28 19:22:27 node1 pveproxy[1206]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:22:27 node1 pveproxy[1205]: proxy detected vanished client connection
Nov 28 19:22:32 node1 pveproxy[1204]: proxy detected vanished client connection
Nov 28 19:22:33 node1 pvedaemon[1089]: <root@pam> successful auth for user 'root@pam'
Nov 28 19:22:34 node1 pveproxy[1205]: proxy detected vanished client connection
Nov 28 19:22:34 node1 pveproxy[1206]: proxy detected vanished client connection
Nov 28 19:22:36 node1 pveproxy[1205]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:22:36 node1 pveproxy[1204]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:22:36 node1 pveproxy[1204]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:22:38 node1 pvedaemon[1090]: <root@pam> successful auth for user 'root@pam'
Nov 28 19:22:39 node1 pveproxy[1204]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:22:39 node1 pveproxy[1205]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:22:39 node1 pveproxy[1204]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:22:54 node1 pveproxy[1205]: proxy detected vanished client connection
Nov 28 19:22:55 node1 pveproxy[1205]: '/etc/pve/nodes/node2/pve-ssl.pem' does not exist!
Nov 28 19:22:57 node1 pveproxy[1206]: proxy detected vanished client connection
Nov 28 19:23:06 node1 pveproxy[1205]: proxy detected vanished client connection
Nov 28 19:23:06 node1 pveproxy[1204]: proxy detected vanished client connection
Nov 28 19:23:06 node1 pveproxy[1204]: proxy detected vanished client connection
Nov 28 19:23:09 node1 pveproxy[1204]: proxy detected vanished client connection
Nov 28 19:23:09 node1 pveproxy[1204]: proxy detected vanished client connection
Nov 28 19:24:21 node1 chronyd[872]: Selected source 116.203.96.227 (2.debian.pool.ntp.org)
Nov 28 19:26:52 node1 pvedaemon[1089]: <root@pam> successful auth for user 'root@pam'
Nov 28 19:27:48 node1 systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories...
Nov 28 19:27:48 node1 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Nov 28 19:27:48 node1 systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
Nov 28 19:27:48 node1 systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
Nov 28 19:41:52 node1 pvedaemon[1089]: <root@pam> successful auth for user 'root@pam'
 
Problem gelöst.....

Da in jedem der Nodes 2 x 10 GBit und 2 x 1 Gbit Port sind hatte ich ausersehen das Kabel bei beiden Node an den falschen 10 GBit Port gesteckt.
;)
Kabel umgesteckt und es läuft sofort...
 
  • Like
Reactions: Falk R.

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!