Proxmox cluster does not work (freezes every time)

D

Daniel Haurich

New Member
Mar 19, 2024
4
0
1
Hello,
since yesterday nothing works anymore on my Proxmox server, I have already reinstalled both servers, with the official iso file, but on my first server "Proxmox" the cluster does not work, there is always the one with the question mark shown, and when I go to the server in /etc/pve/proxmox or server1 everything crashes, but on the other server everything works, everything is displayed correctly, and I can configure everything.
 

Attachments

  • Screenshot 2024-03-19 212905.png
    Screenshot 2024-03-19 212905.png
    19.6 KB · Views: 10
Hey,

can you ping and connect to "server1" via webgui?
Does dmesg output any errors about pve or any other kernel related things?
What are the technical specifications of your cluster's hosts

Past the output of the following commands/configs in a CODE-tag
/etc/pve/corosync.conf
/etc/pve/storage.cfg
/etc/network/interfaces
dmesg
pveversion -v

Best
 
  • Like
Reactions: Daniel Haurich
Hallo, danke für deine schnelle Antowort, nun geht beim Proxmox Server leider gar nichts mehr Ich kann mich nicht ein mal mehr einloggen, aber im Server1 Interface wird der Server als nicht ereichbar angezeigt :(
Hier die Spezifikatioen von meinen Server:
Proxmox:
Screenshot 20.03.2024 173903.png
Server1:
1710952768738.png
Hier sind die inhalte der Dateien:
Proxmox:
DMESG:
(Ist leider zu lang, hier als text datei: haurich.de/Proxmox_DMESG.txt)
/etc/pve/corosync.conf: Der Server ist da Abgestürtzt weder über ssh oder WinSCP :(:(
/etc/pve/storage.cfg: Der Server ist da Abgestürtzt weder über ssh oder WinSCP :(:(
/etc/network/interfaces:
Code: 
root@Proxmox:~# cat /etc/network/interfaces
Auto Lo
iface lo inet loopback

iface enp3s0 inet Bedienungsanleitung

auto vmbr0
iface vmbr0 inet statisch
 Adresse 192.168.178.40/24
 Gateway 192.168.178.1
 Bridge-Ports enp3s0
 bridge-stp aus
 brücke-fd 0


Quellcode /etc/network/interfaces.d/*
pveversion -v:
Code: 
root@Proxmox:~# pveversion -v
proxmox-ve: 8.1.0 (running kernel: 6.5.13-1-pve)
pve-manager: not correctly installed (running version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5.13-1-pve-signed: 6.5.13-1
proxmox-kernel-6.5: 6.5.13-1
proxmox-kernel-6.5.11-8-pve-signiert: 6.5.11-8
Ceph-Sicherung: 17.2.7-PVE2
CoroSync: 3.1.7-PVE3
Criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.2
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.1
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.1.0
libspice-server1: 0.15.1-1
LVM2: 2.03.16-2
lxc-pve: 5.0.2-4
LXCFS: 5.0.3-PVE4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.4-1
proxmox-backup-datei-wiederherstellung: 3.1.4-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.5
proxmox-widget-toolkit: 4.1.4
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.4
PVE-EDK2-Firmware: 4.2023.08-4
PVE-Firewall: 5.0.3
PVE-Firmware: 3.9-2
pve-ha-manager: 4.0.3
pve-i18n: 3.2.1
pve-qemu-kvm: 8.1.5-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
SmartMonTools: 7.3-PVE1
spiceBegriff: 3.3.0
SWTPM: 0.8.0+PVE1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve2
Server1:
DMESG:
(Ist leider zu lang, hier als text datei: haurich.de/Server1_DMESG.txt)
/etc/pve/corosync.conf:
Code: 
root@server1:~# cat /etc/pve/corosync.conf
Protokollierung {
Debuggen: Aus
to_syslog: Ja
}

nodelist {
  node {
Bezeichnung: Proxmox
    nodeid: 2
    quorum_votes: 1
    ring0_addr: 192.168.178.40
  }
  node {
Name: Server1
    nodeid: 1
    quorum_votes: 1
    ring0_addr: 192.168.178.45
  }
}

Quorum {
Anbieter: corosync_votequorum
}

totem {
  cluster_name: Cluster
  config_version: 2
Schnittstelle {
Linknummer: 0
  }
ip_version: IPv4-6
link_mode: passiv
secauth: ein
Ausführung: 2
}
/etc/pve/storage.cfg:
Code: 
root@server1:~# cat /etc/pve/corosync.conf
Protokollierung {
Debuggen: Aus
to_syslog: Ja
}

nodelist {
  node {
Bezeichnung: Proxmox
    nodeid: 2
    quorum_votes: 1
    ring0_addr: 192.168.178.40
  }
  node {
Name: Server1
    nodeid: 1
    quorum_votes: 1
    ring0_addr: 192.168.178.45
  }
}

Quorum {
Anbieter: corosync_votequorum
}

totem {
  cluster_name: Cluster
  config_version: 2
Schnittstelle {
Linknummer: 0
  }
ip_version: IPv4-6
link_mode: passiv
secauth: ein
Ausführung: 2
}

root@server1:~# cat /etc/pve/storage.cfg
Regie: Lokal
Pfad /var/lib/vz
Inhalt ISO,Sicherung,VZTMPL

LVMTHIN: lokal-lvm
Thinpool-Daten
        vgname pve
Inhalt Bilder,rootdir

dir: Sicherungen
Pfad /home/recover
Inhaltsbilder,Backup
        prune-backups keep-all=1
 geteilt 0
/etc/network/interfaces:
Code: 
root@server1:~# cat /etc/network/interfaces
Auto Lo
iface lo inet loopback

iface enp4s0 inet Bedienungsanleitung

auto vmbr0
iface vmbr0 inet statisch
Adresse 192.168.178.45/24
Gateway 192.168.178.1
Bridge-Ports ENP4S0
bridge-stp aus
brücke-fd 0


Quellcode /etc/network/interfaces.d/*
pveversion -v:
Code: 
root@server1:~# pveversion -v
proxmox-ve: 8.1.0 (mit Kernel: 6.5.13-1-pve)
pve-manager: 8.1.4 (laufende Version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5.13-1-pve-signiert: 6.5.13-1
proxmox-kernel-6.5: 6.5.13-1
proxmox-kernel-6.5.11-8-pve-signiert: 6.5.11-8
Ceph-Sicherung: 17.2.7-PVE2
CoroSync: 3.1.7-PVE3
Criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.1
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
LVM2: 2.03.16-2
lxc-pve: 5.0.2-4
LXCFS: 5.0.3-PVE4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.4-1
proxmox-backup-datei-wiederherstellung: 3.1.4-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.5
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
PVE-EDK2-Firmware: 4.2023.08-4
PVE-Firewall: 5.0.3
PVE-Firmware: 3.9-2
pve-ha-manager: 4.0.3
PVE-I18N: 3.2.0
pve-qemu-kvm: 8.1.5-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
SmartMonTools: 7.3-PVE1
spiceBegriff: 3.3.0
SWTPM: 0.8.0+PVE1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve2
 
Last edited:
Zudem sind hier die Angefragten pings:
Proxmox:
Code: 
root@Proxmox:~# ping google.de
PING google.de (142.250.185.67) 56(84) Byte Daten.
64 Byte von fra16s48-in-f3.1e100.net (142.250.185.67): icmp_seq=1 TTL=116 Zeit=15,7 ms
64 Byte von fra16s48-in-f3.1e100.net (142.250.185.67): icmp_seq=2 TTL=116 Zeit=14,0 ms
64 Byte von fra16s48-in-f3.1e100.net (142.250.185.67): icmp_seq=3 TTL=116 Zeit=14,2 ms
64 Byte von fra16s48-in-f3.1e100.net (142.250.185.67): icmp_seq=4 TTL=116 Zeit=15,6 ms
^C
--- google.de Ping-Statistiken ---
4 Pakete gesendet, 4 empfangen, 0% Paketverlust, Zeit 3005ms
rtt min/avg/max/mdev = 14,018/14,899/15,711/0,781 m
Interner Ping auf denn Anderen Server (Server1):
Code: 
root@Proxmox:~# ping 192.168.178.45
PING 192.168.178.45 (192.168.178.45) 56(84) Byte Daten.
64 Byte von 192.168.178.45: icmp_seq=1 TTL=64 Zeit=0,357 ms
64 Byte von 192.168.178.45: icmp_seq=2 TTL=64 Zeit=0,322 ms
64 Byte von 192.168.178.45: icmp_seq=3 TTL=64 Zeit=0,285 ms
^C
--- 192.168.178.45 Ping-Statistik ---
3 Pakete gesendet, 3 empfangen, 0% Paketverlust, Zeit 2042ms
rtt min/avg/max/mdev = 0,285/0,321/0,357/0,029 ms
Server1:
Code: 
root@server1:~# ping google.de
PING google.de (142.250.185.67) 56(84) Byte Daten.
64 Byte von fra16s48-in-f3.1e100.net (142.250.185.67): icmp_seq=1 TTL=116 Zeit=18,0 ms
^C
--- google.de Ping-Statistiken ---
1 Paket gesendet, 1 empfangen, 0% Paketverlust, Zeit 0ms
rtt min/avg/max/mdev = 18,035/18,035/18,035/0,000 ms
Interner Ping auf denn Anderen Server (Proxmox):
Code: 
root@server1:~# ping 192.168.178.40
PING 192.168.178.40 (192.168.178.40) 56(84) Byte Daten.
64 Byte von 192.168.178.40: icmp_seq=1 TTL=64 Zeit=0,271 ms
64 Byte von 192.168.178.40: icmp_seq=2 TTL=64 Zeit=0,264 ms
64 Byte von 192.168.178.40: icmp_seq=3 TTL=64 Zeit=0,297 ms
^C
--- 192.168.178.40 Ping-Statistik ---
3 Pakete gesendet, 3 empfangen, 0% Paketverlust, Zeit 2038ms
rtt min/avg/max/mdev = 0,264/0,277/0,297/0,014 ms
 
Last edited:
Code: 
root@server1:~# cat /etc/network/interfaces
Auto Lo
iface lo inet loopback

iface enp4s0 inet Bedienungsanleitung

auto vmbr0
iface vmbr0 inet statisch
Adresse 192.168.178.45/24
Gateway 192.168.178.1
>>>Bridge-Ports ENP4S0  ### Change to Bridge-Ports enp4s0 <<<
bridge-stp aus
brücke-fd 0


Quellcode /etc/network/interfaces.d/*
I believe that Linux interface names are case sensitive (e.g. if0 and IF0 are distinct). So that bridge-port should really read: Bridge-Ports enp4s0. I don't like the other capital letters, such as "Adresse " "Bridge.....", I've never encountered it before, nor the German language used here, but the port name itself I would defnitely change.
 
Last edited:
gfngfn256 said:
Code: 
root@server1:~# cat /etc/network/interfaces
Auto Lo
iface lo inet loopback

iface enp4s0 inet Bedienungsanleitung

auto vmbr0
iface vmbr0 inet statisch
Adresse 192.168.178.45/24
Gateway 192.168.178.1
>>>Bridge-Ports ENP4S0  ### Change to Bridge-Ports enp4s0 <<<
bridge-stp aus
brücke-fd 0


Quellcode /etc/network/interfaces.d/*
I believe that Linux interface names are case sensitive (e.g. if0 and IF0 are distinct). So that bridge-port should really read: Bridge-Ports enp4s0. I don't like the other capital letters, such as "Adresse " "Bridge.....", I've never encountered it before, nor the German language used here, but the port name itself I would defnitely change.
Click to expand...

Hello, thnak you for your answer, in my configuration everything was written in lower case, but unfortunately this did not help :( my server: "Proxmox" is still offline except via ssh :(
 
Your configuration files are translated into german language?

What you deferentially want is to have your interface configuration in english

Code: 
Auto Lo
iface lo inet loopback

iface enp4s0 inet manual

auto vmbr0
iface vmbr0 inet static
address 192.168.178.45/24
gateway 192.168.178.1
bridge-ports enp4s0  ### Change to Bridge-Ports enp4s0 <<<
bridge-stp off
bridge-fd 0


source /etc/network/interfaces.d/*

Is your ssh service running? systemctl status ssh
Is port 22 open on your host and listen to the interface? ss -tulpn | grep 22

Best
 
If you can SSH into the server, then check cat /etc/hosts
The IP/Hostname maybe wrong which would have a large impact.
 
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