highspeed Posted February 28, 2017 Share Posted February 28, 2017 I've just noticed in my logs that the virtual interfaces in docker appear to be going into a blocking mode, then cycling back to forwarding: Feb 28 12:54:11 NAS kernel: docker0: port 2(vethd01f0ec) entered disabled state Feb 28 12:54:12 NAS kernel: docker0: port 2(vethd01f0ec) entered disabled state Feb 28 12:54:12 NAS kernel: device vethd01f0ec left promiscuous mode Feb 28 12:54:12 NAS kernel: docker0: port 2(vethd01f0ec) entered disabled state Feb 28 12:54:16 NAS kernel: docker0: port 2(veth1a33bbc) entered blocking state Feb 28 12:54:16 NAS kernel: docker0: port 2(veth1a33bbc) entered disabled state Feb 28 12:54:16 NAS kernel: device veth1a33bbc entered promiscuous mode Feb 28 12:54:16 NAS kernel: docker0: port 2(veth1a33bbc) entered blocking state Feb 28 12:54:16 NAS kernel: docker0: port 2(veth1a33bbc) entered forwarding state Feb 28 12:54:16 NAS kernel: docker0: port 2(veth1a33bbc) entered disabled state Feb 28 12:54:18 NAS kernel: eth0: renamed from veth12e0e95 Feb 28 12:54:18 NAS kernel: docker0: port 2(veth1a33bbc) entered blocking state Feb 28 12:54:18 NAS kernel: docker0: port 2(veth1a33bbc) entered forwarding state This appears to be happening on multiple ports about every hour or two. Does anyone have experience with this? Quote Link to comment
Recommended Posts
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.