Ethernet Port keeps getting renamed?

[Ben deBoer]

I recently upgraded to 6.11 from 6.8, and I have noticed that my ethernet has been cutting out sometimes.  Has anyone else seen this?

 

Nov 13 22:06:18 Tower kernel: eth0: renamed from vethe781b3d
Nov 13 22:06:18 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth69db3b0: link becomes ready
Nov 13 22:06:20 Tower  avahi-daemon[23070]: Joining mDNS multicast group on interface veth69db3b0.IPv6 with address fe80::c00e:26ff:fe95:afb6.
Nov 13 22:06:20 Tower  avahi-daemon[23070]: New relevant interface veth69db3b0.IPv6 for mDNS.
Nov 13 22:06:20 Tower  avahi-daemon[23070]: Registering new address record for fe80::c00e:26ff:fe95:afb6 on veth69db3b0.*.
Nov 13 22:06:25 Tower kernel: br-5180425399c9: port 2(veth69db3b0) entered disabled state
Nov 13 22:06:25 Tower kernel: vethe781b3d: renamed from eth0
Nov 13 22:06:25 Tower  avahi-daemon[23070]: Interface veth69db3b0.IPv6 no longer relevant for mDNS.
Nov 13 22:06:25 Tower  avahi-daemon[23070]: Leaving mDNS multicast group on interface veth69db3b0.IPv6 with address fe80::c00e:26ff:fe95:afb6.
Nov 13 22:06:25 Tower kernel: br-5180425399c9: port 2(veth69db3b0) entered disabled state
Nov 13 22:06:25 Tower kernel: device veth69db3b0 left promiscuous mode
Nov 13 22:06:25 Tower kernel: br-5180425399c9: port 2(veth69db3b0) entered disabled state
Nov 13 22:06:25 Tower  avahi-daemon[23070]: Withdrawing address record for fe80::c00e:26ff:fe95:afb6 on veth69db3b0.
Nov 13 22:06:26 Tower kernel: br-5180425399c9: port 2(veth05ce39d) entered blocking state
Nov 13 22:06:26 Tower kernel: br-5180425399c9: port 2(veth05ce39d) entered disabled state
Nov 13 22:06:26 Tower kernel: device veth05ce39d entered promiscuous mode
Nov 13 22:06:26 Tower kernel: br-5180425399c9: port 2(veth05ce39d) entered blocking state
Nov 13 22:06:26 Tower kernel: br-5180425399c9: port 2(veth05ce39d) entered forwarding state
Nov 13 22:06:26 Tower kernel: eth0: renamed from veth686bcb1
Nov 13 22:06:26 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth05ce39d: link becomes ready
Nov 13 22:06:28 Tower  avahi-daemon[23070]: Joining mDNS multicast group on interface veth05ce39d.IPv6 with address fe80::208f:d4ff:fed1:8f54.
Nov 13 22:06:28 Tower  avahi-daemon[23070]: New relevant interface veth05ce39d.IPv6 for mDNS.
Nov 13 22:06:28 Tower  avahi-daemon[23070]: Registering new address record for fe80::208f:d4ff:fed1:8f54 on veth05ce39d.*.

tower-diagnostics-20221114-2156.zip

Edited November 15, 2022 by Ben deBoer
added diagnostics

[JorgeB]

The renames are normal, have you been losing access to the server?

[Ben deBoer]

I was running a Pi-Hole docker container on this server, and the WebUI was hanging every 5 - 10 minutes, and that message was the only thing scrolling in the logs.  I have since removed the Pi-Hole docker container, but I am still getting the messages but a lot less frequently.  I haven't experienced loss of the WebUI recently, however, I can't say for sure that it doesn't happen.  Whenever the WebUI used to hang, and I get back in, there was always a new string like that.

If it is normal that it renames like that all the time, that is fine.  I am just wondering if it is failing when it has increased networking traffic, which would be a big problem as I am looking to add Jellyfin to the server.

Edited November 15, 2022 by Ben deBoer

[Ben deBoer]

Yes, I have confirmed that the web UI is basically freezing/locking up on me. Any other logs or things to list?

[JorgeB]

Enable the syslog server and post that after the problem.