Proxmox stürzt regelmäßig ab

myssv · Wednesday at 11:09

Moin zusammen,

ich habe seit einiger Zeit das Problem, dass mein einer Proxmox Server einfriert.

Es hilft dann immer nur den Power Button lange gedrückt zu halten und danach wieder neu zu starten.

Die letzten Male war es immer gegen 22:40:

2025-12-30 22:45:00
2025-12-25 22:40:00

Kann ich irgendwo sehen, was zu dieser Zeit passiert?

Komme eher aus der Windows Welt und bin nur einfacher Linux Anwender. Dafür für jeden Tipp oder Hinweis sehr dankbar!

bl1mp · Wednesday at 11:33

Hi myssv,
prüfe mal das Logging via journalctl und dann ggf. noch dein BIOS Log (je nach mainboard)
In der Hostansicht der WebUI kannst du dir auch sehr bequem die Serverstatistiken anschauen. Ggf. findest du dort auch Hinweise, was die Ursache sein könnte.

BG, Lucas

myssv · Wednesday at 11:38

Ich habe zwar keine Ahnung, aber sieht komisch aus

Code:

[root@pve04 ~]# journalctl
Dec 31 06:00:01 pve04 systemd-journald[1160]: System Journal (/var/log/journal/0632c285c20e44399aa894c7e7028dbb) is 286.7M, max 281M, 0B free.
Dec 31 06:00:01 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr122i0
Dec 31 06:00:01 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:01 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr117i0
Dec 31 06:00:01 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:02 pve04 kernel: IPv4: martian source 192.168.115.14 from 192.168.115.114, on dev fwbr122i0
Dec 31 06:00:02 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff bc 24 11 5d 22 4d 08 06
Dec 31 06:00:02 pve04 kernel: IPv4: martian source 192.168.115.14 from 192.168.115.114, on dev fwbr117i0
Dec 31 06:00:02 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff bc 24 11 5d 22 4d 08 06
Dec 31 06:00:04 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.22, on dev fwbr122i0
Dec 31 06:00:04 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff 6c 1f f7 16 e3 2e 08 00
Dec 31 06:00:04 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.22, on dev fwbr117i0
Dec 31 06:00:04 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff 6c 1f f7 16 e3 2e 08 00
Dec 31 06:00:06 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr122i0
Dec 31 06:00:06 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:06 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr117i0
Dec 31 06:00:06 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:11 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr122i0
Dec 31 06:00:11 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:11 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr117i0
Dec 31 06:00:11 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:16 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr122i0
Dec 31 06:00:16 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:16 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr117i0
Dec 31 06:00:16 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:21 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr122i0
Dec 31 06:00:21 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:21 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr117i0
Dec 31 06:00:21 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:26 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr122i0
Dec 31 06:00:26 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:26 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr117i0
Dec 31 06:00:26 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:31 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr122i0
Dec 31 06:00:31 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:31 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr117i0
Dec 31 06:00:31 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:36 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr122i0
Dec 31 06:00:36 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:36 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr117i0
Dec 31 06:00:36 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:41 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr122i0
Dec 31 06:00:41 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:41 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr117i0
Dec 31 06:00:41 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:46 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr122i0
Dec 31 06:00:46 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:46 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr117i0
Dec 31 06:00:46 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:51 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr122i0
Dec 31 06:00:51 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:51 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr117i0
Dec 31 06:00:51 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:56 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr122i0
Dec 31 06:00:56 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:00:56 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr117i0
Dec 31 06:00:56 pve04 kernel: ll header: 00000000: ff ff ff ff ff ff b0 4a 39 fc 3f aa 08 00
Dec 31 06:01:01 pve04 kernel: IPv4: martian source 192.168.115.255 from 192.168.115.88, on dev fwbr122i0

Die 192.168.115.88 ist mein Roborock Staugsauger ....

UdoB · Wednesday at 12:00

Das Ende des relevanten vorherigen Journal kannst du dir so anzeigen lassen: journalctl -b -1 -e

( -b -1 = das vorherige Log; -e = zeige das Ende, nicht den Anfang. Mehr Details: man journalctl )

Die Marsianer zeigen, dass die Netze nicht wirksam getrennt sind - es kommen (IP-) Pakete herein, die auf dem Interface nicht erwartet wurden. https://de.wikipedia.org/wiki/Martian_Packet

myssv · Wednesday at 12:03

Ich habe nur ein Netzwerk, wo zur Zeit alles drüber läuft. 192.168.115.0/24.

UdoB · Wednesday at 12:17

Zeige bitte mal cat /etc/network/interfaces + ergänzend den aktuellen Zustand ip address show ; ip route show . Am besten in [code] ... [/code]-Blöcken - oder per "</>" Symbol im Editor.

myssv · Wednesday at 13:39

Code:

[root@pve04 ~]# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto eno1
iface eno1 inet manual
        accept_ra 1

iface wlp2s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.115.14/24
        gateway 192.168.115.254
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

source /etc/network/interfaces.d/*

Code:

[root@pve04 ~]# ip address show ; ip route show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq master vmbr0 state UP group default qlen 1000
    link/ether 6c:24:08:66:45:3a brd ff:ff:ff:ff:ff:ff
    altname enp0s31f6
    altname enx6c240866453a
3: wlp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 20:2b:20:51:76:a5 brd ff:ff:ff:ff:ff:ff
4: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 6c:24:08:66:45:3a brd ff:ff:ff:ff:ff:ff
    inet 192.168.115.14/24 scope global vmbr0
       valid_lft forever preferred_lft forever
    inet6 fe80::6e24:8ff:fe66:453a/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever
5: tap117i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq master fwbr117i0 state UNKNOWN group default qlen 1000
    link/ether 6e:db:57:30:cb:78 brd ff:ff:ff:ff:ff:ff
6: fwbr117i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 2e:68:67:7c:bd:39 brd ff:ff:ff:ff:ff:ff
7: fwpr117p0@fwln117i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether 7e:72:e6:3b:fc:99 brd ff:ff:ff:ff:ff:ff
8: fwln117i0@fwpr117p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr117i0 state UP group default qlen 1000
    link/ether 2e:68:67:7c:bd:39 brd ff:ff:ff:ff:ff:ff
9: tap122i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc fq master fwbr122i0 state UNKNOWN group default qlen 1000
    link/ether 4a:0d:78:e3:94:f0 brd ff:ff:ff:ff:ff:ff
10: fwbr122i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 76:5e:c9:f6:2a:07 brd ff:ff:ff:ff:ff:ff
11: fwpr122p0@fwln122i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000
    link/ether a6:86:eb:6d:4f:da brd ff:ff:ff:ff:ff:ff
12: fwln122i0@fwpr122p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr122i0 state UP group default qlen 1000
    link/ether 76:5e:c9:f6:2a:07 brd ff:ff:ff:ff:ff:ff
default via 192.168.115.254 dev vmbr0 proto kernel onlink
192.168.115.0/24 dev vmbr0 proto kernel scope link src 192.168.115.14

UdoB · Wednesday at 14:38

Tja, danke.

myssv said:
auto eno1
iface eno1 inet manual
accept_ra 1

Die erste Zeile sollte (ohne konkreten Grund) nicht vorhanden sein, "auto vmbr0" bei der Bridge genügt. Vergleiche: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_default_configuration_using_a_bridge

"Router Advertisement akzeptieren" macht ohne funktionierendes IPv6 keinen Sinn. Verwendest du das?

Mehr fällt mir nicht auf...

myssv · Wednesday at 15:02

Sorry, Du hast mich mitten Im Umbau erwischt.

Ich habe heute mein Unifi Gateway bekommen und baue gerade um. IPv6 ist auf den Containern und VMs in Nutzung. Bei den Hosts habe ich es noch nicht wirklich aktiviert.

Also sollte die interfaces so aussehen?

Code:

auto lo
iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.115.14/24
        gateway 192.168.115.254
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0

source /etc/network/interfaces.d/*

Wobei mir die 2. Netzwerkkarte immer noch angezeigt wird:

Search

Search

Proxmox stürzt regelmäßig ab

myssv

Member

bl1mp

Active Member

myssv

Member

UdoB

Distinguished Member

myssv

Member

UdoB

Distinguished Member

myssv

Member

UdoB

Distinguished Member

myssv

Member

We value your privacy