Proxmox loses ethernet connection when I try to update HA

eduardoll

New Member
Feb 6, 2021
11
0
1
39
Im new to the proxmox environment and I have no idea where I should start to investigate.

The issue is weird.. There are some commands I do on Home Assistant that make my proxmox lose the ethernet connection. When that happens, I have to unplug and plug the ethernet cable and everything starts to work again. Important to note that is only the internet connection that stops working, the proxmox server and VMs continue to working without any issue.

It is easy to reproduce this issue when I try to update the Home Assistant or to deploy big changes in a node red flow.

Does anyone have any suggestion about this issue?

Last lines of dmesg after the issue occurred:
[102608.273026] device tap100i0 entered promiscuous mode [102608.302536] vmbr0v10: port 3(tap100i0) entered blocking state [102608.302539] vmbr0v10: port 3(tap100i0) entered disabled state [102608.302657] vmbr0v10: port 3(tap100i0) entered blocking state [102608.302659] vmbr0v10: port 3(tap100i0) entered forwarding state [102794.696001] vmbr0v10: port 3(tap100i0) entered disabled state [102796.769821] device tap101i0 entered promiscuous mode [102796.840811] fwbr101i0: port 1(fwln101i0) entered blocking state [102796.840815] fwbr101i0: port 1(fwln101i0) entered disabled state [102796.840993] device fwln101i0 entered promiscuous mode [102796.841106] fwbr101i0: port 1(fwln101i0) entered blocking state [102796.841109] fwbr101i0: port 1(fwln101i0) entered forwarding state [102796.848218] vmbr0v100: port 2(fwpr101p0) entered blocking state [102796.848221] vmbr0v100: port 2(fwpr101p0) entered disabled state [102796.848322] device fwpr101p0 entered promiscuous mode [102796.848375] vmbr0v100: port 2(fwpr101p0) entered blocking state [102796.848378] vmbr0v100: port 2(fwpr101p0) entered forwarding state [102796.854618] fwbr101i0: port 2(tap101i0) entered blocking state [102796.854621] fwbr101i0: port 2(tap101i0) entered disabled state [102796.854761] fwbr101i0: port 2(tap101i0) entered blocking state [102796.854763] fwbr101i0: port 2(tap101i0) entered forwarding state [103132.024743] fwbr101i0: port 2(tap101i0) entered disabled state [103132.046136] fwbr101i0: port 1(fwln101i0) entered disabled state [103132.046292] vmbr0v100: port 2(fwpr101p0) entered disabled state [103132.046443] device fwln101i0 left promiscuous mode [103132.046446] fwbr101i0: port 1(fwln101i0) entered disabled state [103132.062321] device fwpr101p0 left promiscuous mode [103132.062325] vmbr0v100: port 2(fwpr101p0) entered disabled state [179315.362094] usb 1-5: USB disconnect, device number 19 [179315.676856] usb 1-5: new full-speed USB device number 20 using xhci_hcd [179315.830448] usb 1-5: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00 [179315.830451] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [179315.830453] usb 1-5: Product: ConBee II [179315.830454] usb 1-5: Manufacturer: dresden elektronik ingenieurtechnik GmbH [179315.830455] usb 1-5: SerialNumber: DE2213484 [179315.831646] cdc_acm 1-5:1.0: ttyACM0: USB ACM device [179317.609348] usb 1-5: reset full-speed USB device number 20 using xhci_hcd [179319.167800] usb 1-5: USB disconnect, device number 20 [179319.549301] usb 1-5: new full-speed USB device number 21 using xhci_hcd [179324.805867] usb 1-5: unable to read config index 0 descriptor/all [179324.805875] usb 1-5: can't read configurations, error -110 [179324.933839] usb 1-5: new full-speed USB device number 22 using xhci_hcd [179325.083501] usb 1-5: New USB device found, idVendor=1cf1, idProduct=0030, bcdDevice= 1.00 [179325.083505] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [179325.083507] usb 1-5: Product: ConBee II [179325.083508] usb 1-5: Manufacturer: dresden elektronik ingenieurtechnik GmbH [179325.083510] usb 1-5: SerialNumber: DE2213484 [179325.084708] cdc_acm 1-5:1.0: ttyACM0: USB ACM device [179325.610130] usb 1-5: reset full-speed USB device number 22 using xhci_hcd [179611.758040] r8169 0000:03:00.0 enp3s0: Link is Down [179611.758167] vmbr0: port 1(enp3s0) entered disabled state [179611.758289] vmbr0v10: port 1(enp3s0.10) entered disabled state [179611.758400] vmbr0v100: port 1(enp3s0.100) entered disabled state [179615.134641] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control off [179615.134659] vmbr0: port 1(enp3s0) entered blocking state [179615.134661] vmbr0: port 1(enp3s0) entered forwarding state [179615.134777] vmbr0v10: port 1(enp3s0.10) entered blocking state [179615.134780] vmbr0v10: port 1(enp3s0.10) entered forwarding state [179615.134820] vmbr0v100: port 1(enp3s0.100) entered blocking state [179615.134821] vmbr0v100: port 1(enp3s0.100) entered forwarding state

Thanks
 

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 your own in 60 seconds.

Buy now!