PVE host not accessible after power shutdown; VMs working

Homer-S

Member
Nov 18, 2020
31
2
13
51
Hello,
we had an issue with our power supply. Proxmox server was killed by no power supply. After restarting the engine, I was able to SSH in and it looked quite ok.
After running for a few hours I am not able to access Web GUI neither SSH. Fun fact: all VMs / LXCs are running like expected.

Any ideas how to solve it or at least, where to search for the issue?

Thanks

Edit 1: I can not ping the internal ip; Router is showing ip with known IP address.
Edit 2: With a Display/keynoard I am able to log in directly at the server. The host can ping his ip address and others.
 
Last edited:
hi,

Any ideas how to solve it or at least, where to search for the issue?
check your journalctl, hopefully the filesystem wasn't corrupted by the power loss.

for the network issue, if your PVE host can reach the local network and internet but is not accessible, then take a look at your firewall settings and if the SSH and pveproxy service are still running.
 
When I plugged a display into the server, this showed up first


2022-08-01 15_48_45-Einstellungen.jpg

192.168.100.22 is accessible by others
 
I checked status of sshd/ssh/pveproxy services. all are active
afaik there I have no firewall on this server only on router

checking dmesg I have a lot of this one:
 

Attachments

  • 20220801_160611.jpg
    20220801_160611.jpg
    970.8 KB · Views: 13
  • 20220801_160611.jpg
    20220801_160611.jpg
    970.8 KB · Views: 12
  • 20220801_160620.jpg
    20220801_160620.jpg
    362.5 KB · Views: 10
  • 20220801_160654.jpg
    20220801_160654.jpg
    355 KB · Views: 9
  • 20220801_160709.jpg
    20220801_160709.jpg
    380.7 KB · Views: 10
  • 20220801_160721.jpg
    20220801_160721.jpg
    410.7 KB · Views: 10
  • 20220801_160746.jpg
    20220801_160746.jpg
    373.1 KB · Views: 12
error in your dmesg about ACPI shouldn't case issues, though i see that you have docker installed on the PVE host. this is not recommended because it can mess with the networking stack of the host, i'd suggest removing docker from the host and check if the network issue still occurs.
 
docker is installed in some LXC but not directly on the host. ..?!
are you sure?

if you run ip a on the host what do you get?
 
are you sure?

if you run ip a on the host what do you get?
I receive this:
but if I am doing
docker -v
I am receiving an error???

6: tap122i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr122i0 state UNKNOWN group default qlen 1000 link/ether 16:b6:77:9f:a3:b7 brd ff:ff:ff:ff:ff:ff 7: fwbr122i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether e6:0e:d7:a5:62:af brd ff:ff:ff:ff:ff:ff 8: fwpr122p0@fwln122i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000 link/ether b6:03:d4:71:b3:5e brd ff:ff:ff:ff:ff:ff 9: fwln122i0@fwpr122p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr122i0 state UP group default qlen 1000 link/ether 1e:f9:fa:a3:dd:55 brd ff:ff:ff:ff:ff:ff 10: tap111i0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master fwbr111i0 state UNKNOWN group default qlen 1000 link/ether 9e:00:37:a3:05:1a brd ff:ff:ff:ff:ff:ff 11: fwbr111i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether e6:c4:c5:2d:3a:a2 brd ff:ff:ff:ff:ff:ff 12: fwpr111p0@fwln111i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000 link/ether 0e:61:89:18:79:fd brd ff:ff:ff:ff:ff:ff 13: fwln111i0@fwpr111p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr111i0 state UP group default qlen 1000 link/ether 96:1d:11:d7:33:e1 brd ff:ff:ff:ff:ff:ff 14: veth302i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr302i0 state UP group default qlen 1000 link/ether fe:e2:4b:85:b4:a3 brd ff:ff:ff:ff:ff:ff link-netnsid 0 15: fwbr302i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether d2:b0:d0:f0:e4:bb brd ff:ff:ff:ff:ff:ff 16: fwpr302p0@fwln302i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000 link/ether 3a:59:0e:8f:11:74 brd ff:ff:ff:ff:ff:ff 17: fwln302i0@fwpr302p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr302i0 state UP group default qlen 1000 link/ether d6:54:85:5d:6d:27 brd ff:ff:ff:ff:ff:ff 22: veth314i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr314i0 state UP group default qlen 1000 link/ether fe:e2:25:95:91:6b brd ff:ff:ff:ff:ff:ff link-netnsid 1 23: fwbr314i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 86:a8:4d:e5:8d:50 brd ff:ff:ff:ff:ff:ff 24: fwpr314p0@fwln314i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000 link/ether fe:16:11:24:4c:f1 brd ff:ff:ff:ff:ff:ff 25: fwln314i0@fwpr314p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr314i0 state UP group default qlen 1000 link/ether ce:67:ff:72:04:52 brd ff:ff:ff:ff:ff:ff 26: veth313i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr313i0 state UP group default qlen 1000 link/ether fe:f1:fb:a0:5d:2f brd ff:ff:ff:ff:ff:ff link-netnsid 2 27: fwbr313i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 12:2e:09:61:a4:f6 brd ff:ff:ff:ff:ff:ff 28: fwpr313p0@fwln313i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000 link/ether 72:a9:ff:41:11:f4 brd ff:ff:ff:ff:ff:ff 29: fwln313i0@fwpr313p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr313i0 state UP group default qlen 1000 link/ether 32:26:94:de:64:3d brd ff:ff:ff:ff:ff:ff 30: veth312i0@if2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr312i0 state UP group default qlen 1000 link/ether fe:00:ee:02:cc:dd brd ff:ff:ff:ff:ff:ff link-netnsid 3 31: fwbr312i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether ce:6f:94:62:32:83 brd ff:ff:ff:ff:ff:ff 32: fwpr312p0@fwln312i0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP group default qlen 1000 link/ether e2:55:6b:49:ac:03 brd ff:ff:ff:ff:ff:ff 33: fwln312i0@fwpr312p0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master fwbr312i0 state UP group default qlen 1000 link/ether ba:d4:6f:be:a4:ee brd ff:ff:ff:ff:ff:ff
 

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!