Logs spammed with eth port forwarding/disabled/blocking state?

[adamf]

Hi, 

 

I am getting this repeated in my logs:

 

Jan 4 16:35:38 Tower kernel: eth0: renamed from vetheb13b06

Jan 4 16:35:38 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth33e51aa: link becomes ready

Jan 4 16:35:38 Tower kernel: docker0: port 1(veth33e51aa) entered blocking state

Jan 4 16:35:38 Tower kernel: docker0: port 1(veth33e51aa) entered forwarding state

Jan 4 16:35:38 Tower kernel: docker0: port 1(veth33e51aa) entered disabled state

Jan 4 16:35:38 Tower kernel: vetheb13b06: renamed from eth0

Jan 4 16:35:38 Tower kernel: docker0: port 1(veth33e51aa) entered disabled state

Jan 4 16:35:38 Tower kernel: device veth33e51aa left promiscuous mode

Jan 4 16:35:38 Tower kernel: docker0: port 1(veth33e51aa) entered disabled state

Jan 4 16:36:38 Tower kernel: docker0: port 1(veth447cdf3) entered blocking state

Jan 4 16:36:38 Tower kernel: docker0: port 1(veth447cdf3) entered disabled state

Jan 4 16:36:38 Tower kernel: device veth447cdf3 entered promiscuous mode

Jan 4 16:36:38 Tower kernel: docker0: port 1(veth447cdf3) entered blocking state

Jan 4 16:36:38 Tower kernel: docker0: port 1(veth447cdf3) entered forwarding state

Jan 4 16:36:38 Tower kernel: docker0: port 1(veth447cdf3) entered disabled state

Jan 4 16:36:38 Tower kernel: eth0: renamed from veth430d7c6

 

What is this message and how can I resolve it? I am not using IPv6 to my knowledge.... and i only have 2 dockers running, cloudflared and Jellyfin....

 

Thanks.

 

-Adam

[JorgeB]

Those are normal.

[adamf]

is it normal to have them every minute? they seem to be spamming the logs...

 

-Adam

[JorgeB]

Depends on and how many dockers you have.

[dlandon]

Stop all your dockers and then start them one at a time to see which one is causing the logging.

[adamf]

I have all of them stopped, the only ones running are Cloudflared and Jellyfin...

 

-Adam

[dlandon]

Are the log messages continuing?  If they are, stop those dockers and find out which one has the problem.

Edited January 5, 2022 by dlandon

[adamf]

Looks like it was cloudflared... and likely because I have the docker running but it not setup with Cloudflare... will keep it off until I set it up... thanks!

 

-Adam

[Masterwishx]

On 1/5/2022 at 4:23 PM, dlandon said:

Stop all your dockers and then start them one at a time to see which one is causing the logging.

 

also having this problem from proxynet ...

What should i do after finded what docker couse it ?

 

[dlandon]

Post on the support forum for the specific docker container.