PVE becomes unreachable via ethernet but OS is running

A

AleXSR700

New Member
May 26, 2026
2
0
1
Hi everyone,
I am new to PVE but have setup most things I wanted in my test PVE.

Unfortunately, the PVE itself and all VMs/LXCs become unreachable via ethernet from time to time and become immediately reachable again as soon as I log in on the actual server (currently still have a monitor connected).

So it seems the server is up an running but the ethernet connection is down somehow.

I googled and tried so far:
✅ EEE disabled
✅ Offloading disabled
✅ ASPM disabled
✅ Runtime PM disabled
✅ No suspend/hibernate
✅ No overload
✅ No obvious NIC resets

Before I wipe the server and start fresh, does anybody have any idea what might be causing this?

The behavior seems independent of which VM or LXC is running. Last time it was just ESPHome and OPNSense and ESPHome suddenly became unavailable in the middle of some testing.

Running latest PVE on Lenovo M70q with Intel I219-V. But as I said, I tried the above "usual suspects" according to the forum.

Thank you for your help
Alex
 
AleXSR700 said:
Unfortunately, the PVE itself and all VMs/LXCs become unreachable via ethernet from time to time
Click to expand...
Triple check if there is an IP address conflict. Your systems have static addresses, right? I've seen conflicts too often...
 
Okay, so, `journcalctl -k` of this morning'S incident:
I think the server becomes unreachable only when i am connected to it and using it (either the proxmox ui or one of the vms/lxcs.
It does not seem to happen just because I was offline for a while.
This time, after logging in, the server did not become reachable again. It stayed unreachable for a while.

I was able to ping the proxmox ip from the proxmox servers shell (physically logging in to the server).

tcpdump was empty.

kernel.log:
Code: 
May 26 23:32:44 pve01 kernel: veth103i0: entered promiscuous mode
May 26 23:32:44 pve01 kernel: eth0: renamed from veth2SF1X9
May 26 23:32:45 pve01 kernel: vmbr1: port 2(veth103i0) entered blocking state
May 26 23:32:45 pve01 kernel: vmbr1: port 2(veth103i0) entered forwarding state
May 27 00:31:58 pve01 kernel: audit: type=1400 audit(1779834718.647:134): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=13639 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 00:31:58 pve01 kernel: audit: type=1400 audit(1779834718.647:135): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=13639 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 00:31:58 pve01 kernel: audit: type=1400 audit(1779834718.647:136): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=13639 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 00:31:58 pve01 kernel: audit: type=1400 audit(1779834718.647:137): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=13639 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 00:31:58 pve01 kernel: audit: type=1400 audit(1779834718.647:138): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=13639 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 01:58:46 pve01 kernel: perf: interrupt took too long (2503 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
May 27 03:41:38 pve01 kernel: perf: interrupt took too long (3130 > 3128), lowering kernel.perf_event_max_sample_rate to 63000
May 27 08:17:44 pve01 kernel: audit: type=1400 audit(1779862664.578:139): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=99972 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:17:44 pve01 kernel: audit: type=1400 audit(1779862664.578:140): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=99972 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:17:44 pve01 kernel: audit: type=1400 audit(1779862664.578:141): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=99972 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:17:44 pve01 kernel: audit: type=1400 audit(1779862664.578:142): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=99972 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:17:44 pve01 kernel: audit: type=1400 audit(1779862664.578:143): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=99972 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none

so, `tcpdump -ni nic0 icmp` showed nothing during the incident ((physically logged in to the shell to check).

I was able to ping to proxmox ip (server to itself). I was not able to ping any VMs or LXCs or the other devices on LAN.

I think the issue is actually not prolonged sleep but it seems that this only happens when I am actually connected either to the UI or to a VM/LXC via that respective WebUI. I have not seen it happen just because I was offline overnight.

I would be surprised to see a second device using the same IP as the proxmox server given the the DHCP range starts much higher. Not even sure how to check because the DHCP server is my vodafone cable router. It should not assign an IP identical to my PVE. It unfortunately does not have a proper logging function so I am not sure how to verify.

MY PVE system log from around that time:
Code: 
May 27 08:13:36 pve01 pveproxy[9019]: authentication failure: 401 permission denied - invalid PVE ticket
May 27 08:13:36 pve01 pveproxy[9020]: authentication failure: 401 permission denied - invalid PVE ticket
May 27 08:13:36 pve01 pveproxy[9021]: authentication failure: 401 permission denied - invalid PVE ticket
May 27 08:13:36 pve01 pveproxy[9019]: authentication failure: 401 permission denied - invalid PVE ticket
May 27 08:13:36 pve01 unix_chkpwd[99177]: password check failed for user (root)
May 27 08:13:36 pve01 IPCC.xs[99175]: pam_unix(proxmox-ve-auth:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=::ffff:192.168.0.70  user=root
May 27 08:13:37 pve01 pveproxy[9020]: authentication failure: 401 permission denied - invalid PVE ticket
May 27 08:13:38 pve01 pvedaemon[1246]: authentication failure; rhost=::ffff:192.168.0.70 user=root@pam msg=Authentication failure
May 27 08:14:35 pve01 pvedaemon[1245]: <root@pam> successful auth for user 'root@pam'
May 27 08:14:42 pve01 pvedaemon[99407]: starting vnc proxy UPID:pve01:0001844F:002FFF66:6A168BD2:vncproxy:104:root@pam:
May 27 08:14:42 pve01 pvedaemon[1245]: <root@pam> starting task UPID:pve01:0001844F:002FFF66:6A168BD2:vncproxy:104:root@pam:
May 27 08:14:46 pve01 pvedaemon[1245]: <root@pam> end task UPID:pve01:0001844F:002FFF66:6A168BD2:vncproxy:104:root@pam: OK
May 27 08:14:46 pve01 pvedaemon[1246]: <root@pam> starting task UPID:pve01:00018454:003000D8:6A168BD6:vncproxy:109:root@pam:
May 27 08:14:46 pve01 pvedaemon[99412]: starting vnc proxy UPID:pve01:00018454:003000D8:6A168BD6:vncproxy:109:root@pam:
May 27 08:17:01 pve01 CRON[99843]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
May 27 08:17:01 pve01 CRON[99845]: (root) CMD (cd / && run-parts --report /etc/cron.hourly)
May 27 08:17:01 pve01 CRON[99843]: pam_unix(cron:session): session closed for user root
May 27 08:17:44 pve01 kernel: audit: type=1400 audit(1779862664.578:139): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=99972 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:17:44 pve01 kernel: audit: type=1400 audit(1779862664.578:140): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=99972 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:17:44 pve01 kernel: audit: type=1400 audit(1779862664.578:141): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=99972 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:17:44 pve01 kernel: audit: type=1400 audit(1779862664.578:142): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=99972 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:17:44 pve01 kernel: audit: type=1400 audit(1779862664.578:143): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=99972 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:20:41 pve01 kernel: audit: type=1400 audit(1779862841.121:144): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=100539 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:20:41 pve01 kernel: audit: type=1400 audit(1779862841.121:145): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=100539 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:20:41 pve01 kernel: audit: type=1400 audit(1779862841.121:146): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=100539 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:20:41 pve01 kernel: audit: type=1400 audit(1779862841.121:147): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=100539 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:20:41 pve01 kernel: audit: type=1400 audit(1779862841.121:148): apparmor="DENIED" operation="create" class="net" info="failed protocol match" error=-13 profile="tcpdump" pid=100539 comm="tcpdump" family="unix" sock_type="stream" protocol=0 requested="create" denied="create" addr=none
May 27 08:21:24 pve01 pvedaemon[1245]: <root@pam> successful auth for user 'root@pam'
May 27 08:21:25 pve01 pvedaemon[1246]: <root@pam> starting task UPID:pve01:0001893D:00309CC9:6A168D65:vncproxy:109:root@pam:
May 27 08:21:25 pve01 pvedaemon[100669]: starting vnc proxy UPID:pve01:0001893D:00309CC9:6A168D65:vncproxy:109:root@pam:
May 27 08:23:43 pve01 kernel: usb 2-3: USB disconnect, device number 2
May 27 08:23:44 pve01 QEMU[1599]: kvm: libusb_release_interface: -4 [NO_DEVICE]
May 27 08:23:49 pve01 kernel: usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd
May 27 08:23:49 pve01 kernel: usb 2-3: New USB device found, idVendor=0951, idProduct=1666, bcdDevice= 1.10
May 27 08:23:49 pve01 kernel: usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 27 08:23:49 pve01 kernel: usb 2-3: Product: DataTraveler 3.0
May 27 08:23:49 pve01 kernel: usb 2-3: Manufacturer: Kingston
May 27 08:23:49 pve01 kernel: usb 2-3: SerialNumber: 0C9D9211BD96B330195B1120
May 27 08:23:49 pve01 kernel: usb-storage 2-3:1.0: USB Mass Storage device detected
May 27 08:23:49 pve01 kernel: scsi host6: usb-storage 2-3:1.0
May 27 08:23:50 pve01 kernel: usb 2-3: reset SuperSpeed USB device number 3 using xhci_hcd
May 27 08:26:27 pve01 kernel: usb 2-3: USB disconnect, device number 3
May 27 08:26:28 pve01 QEMU[1599]: kvm: libusb_release_interface: -4 [NO_DEVICE]
May 27 08:26:30 pve01 kernel: usb 2-3: new SuperSpeed USB device number 4 using xhci_hcd
May 27 08:26:30 pve01 kernel: usb 2-3: New USB device found, idVendor=0951, idProduct=1666, bcdDevice= 1.10
May 27 08:26:30 pve01 kernel: usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 27 08:26:30 pve01 kernel: usb 2-3: Product: DataTraveler 3.0
May 27 08:26:30 pve01 kernel: usb 2-3: Manufacturer: Kingston
May 27 08:26:30 pve01 kernel: usb 2-3: SerialNumber: 0C9D9211BD96B330195B1120
May 27 08:26:30 pve01 kernel: usb-storage 2-3:1.0: USB Mass Storage device detected
May 27 08:26:30 pve01 kernel: scsi host6: usb-storage 2-3:1.0
May 27 08:26:31 pve01 kernel: scsi 6:0:0:0: Direct-Access     Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6
May 27 08:26:31 pve01 kernel: sd 6:0:0:0: Attached scsi generic sg0 type 0
May 27 08:26:32 pve01 kernel: sd 6:0:0:0: [sda] 121061376 512-byte logical blocks: (62.0 GB/57.7 GiB)
May 27 08:26:32 pve01 kernel: sd 6:0:0:0: [sda] Write Protect is off
May 27 08:26:32 pve01 kernel: sd 6:0:0:0: [sda] Mode Sense: 00 00 00 00
May 27 08:26:32 pve01 kernel: sd 6:0:0:0: [sda] Asking for cache data failed
May 27 08:26:32 pve01 kernel: sd 6:0:0:0: [sda] Assuming drive cache: write through
May 27 08:26:32 pve01 kernel: sd 6:0:0:0: [sda] Attached SCSI removable disk
May 27 08:26:33 pve01 kernel: usb 2-3: reset SuperSpeed USB device number 4 using xhci_hcd
May 27 08:26:40 pve01 pvedaemon[1246]: <root@pam> end task UPID:pve01:0001893D:00309CC9:6A168D65:vncproxy:109:root@pam: OK
May 27 08:26:42 pve01 pvedaemon[1245]: <root@pam> starting task UPID:pve01:00018D40:003118A2:6A168EA2:vncshell::root@pam:
May 27 08:26:42 pve01 pvedaemon[101696]: starting termproxy UPID:pve01:00018D40:003118A2:6A168EA2:vncshell::root@pam:
May 27 08:26:42 pve01 pvedaemon[1246]: <root@pam> successful auth for user 'root@pam'
May 27 08:26:42 pve01 login[101699]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
May 27 08:26:42 pve01 systemd-logind[856]: New session 28 of user root.
May 27 08:26:42 pve01 systemd[1]: Started session-28.scope - Session 28 of User root.
May 27 08:26:42 pve01 login[101699]: ROOT LOGIN ON pts/0
May 27 08:27:01 pve01 login[101699]: pam_unix(login:session): session closed for user root
May 27 08:27:01 pve01 systemd[1]: session-28.scope: Deactivated successfully.
May 27 08:27:01 pve01 systemd-logind[856]: Session 28 logged out. Waiting for processes to exit.
May 27 08:27:01 pve01 systemd-logind[856]: Removed session 28.
May 27 08:27:01 pve01 pvedaemon[1245]: <root@pam> end task UPID:pve01:00018D40:003118A2:6A168EA2:vncshell::root@pam: OK
May 27 08:27:05 pve01 pvedaemon[1245]: <root@pam> starting task UPID:pve01:00018D99:00312177:6A168EB9:vncshell::root@pam:
May 27 08:27:05 pve01 pvedaemon[101785]: starting termproxy UPID:pve01:00018D99:00312177:6A168EB9:vncshell::root@pam:
May 27 08:27:05 pve01 pvedaemon[1246]: <root@pam> successful auth for user 'root@pam'
May 27 08:27:05 pve01 login[101788]: pam_unix(login:session): session opened for user root(uid=0) by root(uid=0)
May 27 08:27:05 pve01 systemd-logind[856]: New session 29 of user root.
May 27 08:27:05 pve01 systemd[1]: Started session-29.scope - Session 29 of User root.
May 27 08:27:05 pve01 login[101788]: ROOT LOGIN ON pts/0
May 27 08:27:21 pve01 login[101788]: pam_unix(login:session): session closed for user root
May 27 08:27:21 pve01 pvedaemon[1245]: <root@pam> end task UPID:pve01:00018D99:00312177:6A168EB9:vncshell::root@pam: OK
May 27 08:27:21 pve01 systemd[1]: session-29.scope: Deactivated successfully.
May 27 08:27:21 pve01 systemd-logind[856]: Session 29 logged out. Waiting for processes to exit.
May 27 08:27:21 pve01 systemd-logind[856]: Removed session 29.
May 27 08:39:11 pve01 pveproxy[9019]: problem with client ::ffff:192.168.0.70; No route to host
May 27 08:39:11 pve01 pvedaemon[1246]: <root@pam> end task UPID:pve01:00018454:003000D8:6A168BD6:vncproxy:109:root@pam: OK
May 27 08:50:37 pve01 postfix/qmgr[1188]: 48ED4E1585: from=<root@pve01.homeeee.local>, size=8719, nrcpt=1 (queue active)
May 27 08:50:37 pve01 postfix/smtp[106130]: 48ED4E1585: host mx01.gmail.com[74.208.5.22] refused to talk to me: 554-gmail.com (mxgmxus003) Nemesis ESMTP Service not available 554-No SMTP service 554-Bad DNS PTR resource record. 554 For explanation visit https://postmaster.gmail.com/en/case?c=r0601&i=ip&v=31.16.254.219&r=1MzkGF-1xEiXU1rjV-0115nQ
May 27 08:50:37 pve01 postfix/smtp[106130]: 48ED4E1585: to=<myname@gmail.com>, relay=mx00.gmail.com[74.208.5.20]:25, delay=30000, delays=30000/0.01/0.62/0, dsn=4.0.0, status=deferred (host mx00.gmail.com[74.208.5.20] refused to talk to me: 554-gmail.com (mxgmxus001) Nemesis ESMTP Service not available 554-No SMTP service 554-Bad DNS PTR resource record. 554 For explanation visit https://postmaster.gmail.com/en/case?c=r0601&i=ip&v=31.16.254.219&r=1MkoG9-1xArAI2zWB-00nZQk)
May 27 09:17:01 pve01 CRON[111025]: pam_unix(cron:session): session opened for user root(uid=0) by root(uid=0)
 
You must log in or register to reply here.
Top Bottom
Back