January 15, 20242 yr Anyone have any idea on how I can diagnose this and figure out what's causing it? I'm at a loss. I've also attached the diagnostics zip to see if someone can guide me in the right direction. What is all this??? Jan 14 22:47:01 Maverick kernel: docker0: port 21(veth43ecfbb) entered blocking state Jan 14 22:47:01 Maverick kernel: docker0: port 21(veth43ecfbb) entered disabled state Jan 14 22:47:01 Maverick kernel: device veth43ecfbb entered promiscuous mode Jan 14 22:47:01 Maverick kernel: docker0: port 23(veth4c2eae0) entered blocking state Jan 14 22:47:01 Maverick kernel: docker0: port 23(veth4c2eae0) entered disabled state Jan 14 22:47:01 Maverick kernel: device veth4c2eae0 entered promiscuous mode Jan 14 22:47:01 Maverick kernel: docker0: port 23(veth4c2eae0) entered blocking state Jan 14 22:47:01 Maverick kernel: docker0: port 23(veth4c2eae0) entered forwarding state Jan 14 22:47:01 Maverick kernel: eth0: renamed from veth713e186 Jan 14 22:47:01 Maverick kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4c2eae0: link becomes ready Jan 14 22:47:01 Maverick kernel: eth0: renamed from vethd56dbde Jan 14 22:47:02 Maverick kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth43ecfbb: link becomes ready Jan 14 22:47:02 Maverick kernel: docker0: port 21(veth43ecfbb) entered blocking state Jan 14 22:47:02 Maverick kernel: docker0: port 21(veth43ecfbb) entered forwarding state Jan 14 22:47:17 Maverick kernel: docker0: port 23(veth4c2eae0) entered disabled state Jan 14 22:47:17 Maverick kernel: veth713e186: renamed from eth0 Jan 14 22:47:17 Maverick kernel: docker0: port 23(veth4c2eae0) entered disabled state Jan 14 22:47:17 Maverick kernel: device veth4c2eae0 left promiscuous mode Jan 14 22:47:17 Maverick kernel: docker0: port 23(veth4c2eae0) entered disabled state Jan 14 22:47:17 Maverick kernel: vethd56dbde: renamed from eth0 Jan 14 22:47:17 Maverick kernel: docker0: port 21(veth43ecfbb) entered disabled state Jan 14 22:47:17 Maverick kernel: docker0: port 21(veth43ecfbb) entered disabled state Jan 14 22:47:17 Maverick kernel: device veth43ecfbb left promiscuous mode Jan 14 22:47:17 Maverick kernel: docker0: port 21(veth43ecfbb) entered disabled state maverick-diagnostics-20240114-2236.zip
January 15, 20242 yr Community Expert Those typically happen if you have a docker container continually trying to start and failing. You can normally determine which one by looking at the uptime, but if not it is a case of trial and error by stopping/starting containers manually.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.