Internet connection to Proxmox failing

[jmvdb22]

Hi,

I've recently switched my home assistant instance to a refurbished HP Elitedesk running proxmox. It's all running fine except for that once every few weeks or so it seems to lose it's internet connection making both HA and Proxmox unreachable. The fix at that moment is quite simple, just take out the ethernet cable and plug it back in after a few seconds. I've tried to see if there is a fault logged in proxmox, but can't see where this would be. I did see that the uptime is over 3 weeks, suggesting that proxmox didn't even recognise that it's lost its connection, although this might not be related.

At this moment I don't know where to start looking to find where the problem originates/what to fix. Does anybody have an idea on where I can start?

 

[d.oishi]

Have you checked journalctl?

 

[Impact]

Please share this

lspci -vnnk | awk '/Ethernet/{print $0}' RS=
ls -l /sys/class/net/*/device/driver

 

[jmvdb22]

Have you checked journalctl?

I just did, it only comes up with lines from May 12 (That's when I set it up), nothing after that

 

[jmvdb22]

Please share this

lspci -vnnk | awk '/Ethernet/{print $0}' RS=
ls -l /sys/class/net/*/device/driver

this is the response:

00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (7) I219-LM [8086:15bb] (rev 10)
DeviceName: Onboard Lan
Subsystem: Hewlett-Packard Company Ethernet Connection (7) I219-LM [103c:83e2]
Flags: bus master, fast devsel, latency 0, IRQ 123, IOMMU group 7
Memory at e1100000 (32-bit, non-prefetchable) [size=128K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: e1000e
Kernel modules: e1000e
lrwxrwxrwx 1 root root 0 Jun 1 13:55 /sys/class/net/eno1/device/driver -> ../../../bus/pci/drivers/e1000e

 

[Impact]

E1000E is known to cause issues.

 

[jmvdb22]

E1000E is known to cause issues.

I've tried this now, let's hope it fixes the issue, thanks for the help!

 

[gfngfn256]

I just did, it only comes up with lines from May 12 (That's when I set it up), nothing after that

Error lines or general lines? If you have no output post-May 12, then you have other serious problems except for the NW issue.

Please be aware that by default, journalctl displays output in a pager format, so you have to use keys to navigate/scroll through the output - hence you will only initially see the beginning of the journal, which in your case actually begins on May 12th when you set it up.