Network Card Turned of after Proxmox Update

[ardit.dani]

After Proxomox update both network show this error .

Apr 17 14:56:18 proxnew kernel: vmbr0: port 8(tap2001i0) entered blocking state
Apr 17 14:56:18 proxnew kernel: vmbr0: port 8(tap2001i0) entered forwarding state
Apr 17 14:56:18 proxnew kernel: vmbr0: port 6(tap1000i0) entered blocking state
Apr 17 14:56:18 proxnew kernel: vmbr0: port 6(tap1000i0) entered forwarding state
Apr 17 14:56:18 proxnew kernel: vmbr0: port 4(tap600i0) entered blocking state
Apr 17 14:56:18 proxnew kernel: vmbr0: port 4(tap600i0) entered forwarding state
Apr 17 14:56:18 proxnew kernel: vmbr0: port 3(tap501i0) entered blocking state
Apr 17 14:56:18 proxnew kernel: vmbr0: port 3(tap501i0) entered forwarding state
Apr 17 14:56:18 proxnew kernel: vmbr0: port 2(tap500i0) entered blocking state
Apr 17 14:56:18 proxnew kernel: vmbr0: port 2(tap500i0) entered forwarding state
Apr 17 14:56:18 proxnew kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vmbr0: link becomes ready
Apr 17 14:56:18 proxnew kernel: vmbr1: port 2(tap501i1) entered blocking state
Apr 17 14:56:18 proxnew kernel: vmbr1: port 2(tap501i1) entered forwarding state
Apr 17 14:56:18 proxnew systemd[1]: systemd-journal-optimize.service: Succeeded.
Apr 17 14:56:18 proxnew systemd[1]: Finished Systemd Journal Optimizer.
Apr 17 14:56:18 proxnew systemd[1]: systemd-journal-optimize.service: Consumed 1.156s CPU time.
Apr 17 14:56:19 proxnew kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vmbr1: link becomes ready
Apr 17 14:56:21 proxnew kernel: tg3 0000:02:00.0 eno1: Link is up at 1000 Mbps, full duplex
Apr 17 14:56:21 proxnew kernel: tg3 0000:02:00.0 eno1: Flow control is off for TX and off for RX
Apr 17 14:56:21 proxnew kernel: tg3 0000:02:00.0 eno1: EEE is disabled
Apr 17 14:56:21 proxnew kernel: vmbr0: port 1(eno1) entered blocking state
Apr 17 14:56:21 proxnew kernel: vmbr0: port 1(eno1) entered forwarding state
Apr 17 14:56:21 proxnew kernel: tg3 0000:02:00.1 eno2: Link is up at 1000 Mbps, full duplex
Apr 17 14:56:21 proxnew kernel: tg3 0000:02:00.1 eno2: Flow control is off for TX and off for RX
Apr 17 14:56:21 proxnew kernel: tg3 0000:02:00.1 eno2: EEE is disabled
Apr 17 14:56:21 proxnew kernel: vmbr1: port 1(eno2) entered blocking state
Apr 17 14:56:21 proxnew kernel: vmbr1: port 1(eno2) entered forwarding state
Apr 17 14:57:55 proxnew pveproxy[2133944]: worker exit
Apr 17 14:57:55 proxnew pveproxy[1904]: worker 2133944 finished
Apr 17 14:57:55 proxnew pveproxy[1904]: starting 1 worker(s)
Apr 17 14:57:55 proxnew pveproxy[1904]: worker 2144162 started

It keeps disconnecting every 2 hours

 

[IFC]

Yep!...i had the same experience over a week ago after an update|upgrade , i loose connection after some hours and the only way to get it back up was to either restart the pve host by simply unplugging and replugging the ethernet cable anytime it looses connection, i tried all troubleshooting including restarting the network service via cli, i checked and viewed all functions of the NIC and it was all fine..i concluded it must be a problem proxmox need to fix so i finally just 3 days ago i connected a new hp usb-ethernet adapter and configured it as my bridge port and i have not experience any connection lost since:
1. if you have multiple ethernet ports switch to another port, i have just one and reason i used a an external usb-ethernet adapter
2. update to the latest version of 8.4.1 , i have but yet to connect back to the previous port to see if its been resolved..
So basically simply change to a new port
as you can see from my attachment i have just a single onboard port(enp0s25) which used to be my bridge but moved that to the new external one enx9cebe8364e9d

i just went through my proxmox ve system log and released the issue has to do with the NIC card , it could be due to hardware issues like driver problems or OS conflicts