Log filling up kernel: docker0: port 1(vethaf4f482) entered blocking state

[mikeofoslo]

I have had a setup running for over 2 weeks testing and figuring out how to set up my system. 

 

I have had frigate running in docker for most of the time with a pcie coral tpu chip.

After a reboot of the system last night the frigate docker refuses to start. The frigate container restarts and will not come online. I have already had it running and was just doing some tweaking of the frigate config when it stopped working. 

 

My log is filling up with:

May 30 09:26:13 NEST  avahi-daemon[7954]: Withdrawing address record for fe80::f458:52ff:fe07:8805 on veth8dc7042.
May 30 09:26:14 NEST kernel: docker0: port 1(veth2564b00) entered blocking state
May 30 09:26:14 NEST kernel: docker0: port 1(veth2564b00) entered disabled state
May 30 09:26:14 NEST kernel: device veth2564b00 entered promiscuous mode
May 30 09:26:14 NEST kernel: docker0: port 1(veth2564b00) entered blocking state
May 30 09:26:14 NEST kernel: docker0: port 1(veth2564b00) entered forwarding state
May 30 09:26:14 NEST kernel: docker0: port 1(veth2564b00) entered disabled state
May 30 09:26:16 NEST kernel: eth0: renamed from vethbd13dac
May 30 09:26:16 NEST kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2564b00: link becomes ready
May 30 09:26:16 NEST kernel: docker0: port 1(veth2564b00) entered blocking state
May 30 09:26:16 NEST kernel: docker0: port 1(veth2564b00) entered forwarding state

 

Enclosing the logs hope some one has a minute to review them an give me a pointer. 
 

nest-diagnostics-20230530-0912.zip

[mikeofoslo]

SOLVED: 

- enabled ip6 on the unraid server and on my router 

 

Tip: try checking the frigate log. I hade removed mqtt section from settings. That caused it to stop loading.