Docker Network Issue's?

[Spritzup]

Evening all,

 

I'm having an intermittent problem with my containers becoming inaccessible, in that I attempt to access the webpage, but it simply endlessly spins.  The after a random amount of time, everything is accessible until it happens again.  When this happens, the unRaid GUI is fully accessible, as well as any containers that are not bridged (eg - have a dedicated IP).  The only thing I see the in log (though I've attached my full log) is that what I assume are the container ports become disabled.  Curiously, I also see it trying to get an IPv6 address, despite the fact that it should be disabled...

 

May 23 14:46:16 Dyson emhttpd: Starting services...
May 23 14:46:17 Dyson emhttpd: shcmd (22523): /etc/rc.d/rc.samba restart
May 23 14:46:19 Dyson root: Starting Samba:  /usr/sbin/smbd -D
May 23 14:46:19 Dyson root:                  /usr/sbin/nmbd -D
May 23 14:46:19 Dyson root:                  /usr/sbin/wsdd 
May 23 14:46:19 Dyson root:                  /usr/sbin/winbindd -D
May 23 14:46:19 Dyson wsdd[109770]: set_multicast: Failed to set IPv4 multicast
May 23 14:46:19 Dyson wsdd[109770]: Failed to add multicast for WSDD: Address already in use
May 23 14:46:19 Dyson wsdd[109770]: set_multicast: Failed to set IPv4 multicast
May 23 14:46:49 Dyson kernel: veth1bd4b6a: renamed from eth0
May 23 14:46:49 Dyson kernel: docker0: port 9(vethdc56c05) entered disabled state
May 23 14:46:49 Dyson kernel: docker0: port 9(vethdc56c05) entered disabled state
May 23 14:46:49 Dyson kernel: device vethdc56c05 left promiscuous mode
May 23 14:46:49 Dyson kernel: docker0: port 9(vethdc56c05) entered disabled state
May 23 14:46:53 Dyson kernel: veth188f45b: renamed from eth0
May 23 14:46:53 Dyson kernel: docker0: port 10(vethc70e6f9) entered disabled state
May 23 14:46:53 Dyson kernel: docker0: port 10(vethc70e6f9) entered disabled state
May 23 14:46:53 Dyson kernel: device vethc70e6f9 left promiscuous mode
May 23 14:46:53 Dyson kernel: docker0: port 10(vethc70e6f9) entered disabled state
May 23 14:46:57 Dyson kernel: veth0f85da6: renamed from eth0
May 23 14:46:57 Dyson kernel: docker0: port 11(veth9b57cdc) entered disabled state
May 23 14:46:57 Dyson kernel: docker0: port 11(veth9b57cdc) entered disabled state
May 23 14:46:57 Dyson kernel: device veth9b57cdc left promiscuous mode
May 23 14:46:57 Dyson kernel: docker0: port 11(veth9b57cdc) entered disabled state
May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered blocking state
May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered disabled state
May 23 14:59:19 Dyson kernel: device veth79fed20 entered promiscuous mode
May 23 14:59:19 Dyson kernel: IPv6: ADDRCONF(NETDEV_UP): veth79fed20: link is not ready
May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered blocking state
May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered forwarding state
May 23 14:59:19 Dyson kernel: docker0: port 4(veth79fed20) entered disabled state
May 23 14:59:20 Dyson kernel: eth0: renamed from veth9fce0fd
May 23 14:59:20 Dyson kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth79fed20: link becomes ready
May 23 14:59:20 Dyson kernel: docker0: port 4(veth79fed20) entered blocking state
May 23 14:59:20 Dyson kernel: docker0: port 4(veth79fed20) entered forwarding state
May 23 14:59:46 Dyson kernel: docker0: port 9(veth4bfae45) entered blocking state
May 23 14:59:46 Dyson kernel: docker0: port 9(veth4bfae45) entered disabled state
May 23 14:59:46 Dyson kernel: device veth4bfae45 entered promiscuous mode
May 23 14:59:46 Dyson kernel: IPv6: ADDRCONF(NETDEV_UP): veth4bfae45: link is not ready
May 23 14:59:47 Dyson kernel: eth0: renamed from vethc1dbbde
May 23 14:59:47 Dyson kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth4bfae45: link becomes ready
May 23 14:59:47 Dyson kernel: docker0: port 9(veth4bfae45) entered blocking state
May 23 14:59:47 Dyson kernel: docker0: port 9(veth4bfae45) entered forwarding state
May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered blocking state
May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered disabled state
May 23 15:00:11 Dyson kernel: device veth9a9edae entered promiscuous mode
May 23 15:00:11 Dyson kernel: IPv6: ADDRCONF(NETDEV_UP): veth9a9edae: link is not ready
May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered blocking state
May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered forwarding state
May 23 15:00:11 Dyson kernel: docker0: port 10(veth9a9edae) entered disabled state
May 23 15:00:12 Dyson kernel: eth0: renamed from vethff20ae0
May 23 15:00:12 Dyson kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth9a9edae: link becomes ready
May 23 15:00:12 Dyson kernel: docker0: port 10(veth9a9edae) entered blocking state

 

Any assistance would be appreciated!

~Spritz

dyson-syslog-20200523-2207.zip

[akamemmnon]

im having the same problem, any one figure this out?

[johnny121b]

I don't have an answer, but have a similar problem. 

 

I landed here while searching for an explanation RE: why my HTTP interface has slowed.  I'm also seeing loads of 'docker0 port 1 ......entered blocking/forwarding/disabled state' messages in my log.  My dockers seem to load/work correctly, but clicking on anything in the http interface- means a wait of about 60-seconds.  DASHBOARD -> MAIN = wait 60 seconds......MAIN -> SHARES = wait 60-seconds.....you get the idea. 

 

Wondering if you stumbled upon a solution?

[akamemmnon]

18 minutes ago, johnny121b said:

I don't have an answer, but have a similar problem. 

 

I landed here while searching for an explanation RE: why my HTTP interface has slowed.  I'm also seeing loads of 'docker0 port 1 ......entered blocking/forwarding/disabled state' messages in my log.  My dockers seem to load/work correctly, but clicking on anything in the http interface- means a wait of about 60-seconds.  DASHBOARD -> MAIN = wait 60 seconds......MAIN -> SHARES = wait 60-seconds.....you get the idea. 

 

Wondering if you stumbled upon a solution?

I ended up changing some network settings in unraid (had IPV4, 6 addresses, and DNS server assignment be automatic) and I haven't had the problem again. not sure if this is the solution, but thats all I got.

[kirsco]

I had a similar problem, I discovered that it was an IP address conflict. It popped up suddenly when I had a power outage and the Pi I had assigned the same IP address to on my router powered up and snatched it first and then Unraid had the IP set in the configuration. I've literally been tearing my hair out over this for a few days before I uncovered the issue. The moral of the story is, make it your practice to allocate IPs in the router only rather than configuring on any devices.

 

Jan 16 20:54:11 Prometheus kernel: docker0: port 11(veth16f28b6) entered disabled state
Jan 16 20:54:11 Prometheus kernel: vethaf11fd3: renamed from eth0
Jan 16 20:54:11 Prometheus  avahi-daemon[3945]: Interface veth16f28b6.IPv6 no longer relevant for mDNS.
Jan 16 20:54:11 Prometheus  avahi-daemon[3945]: Leaving mDNS multicast group on interface veth16f28b6.IPv6 with address <MAC Address>.
Jan 16 20:54:11 Prometheus kernel: docker0: port 11(veth16f28b6) entered disabled state
Jan 16 20:54:11 Prometheus kernel: device veth16f28b6 left promiscuous mode
Jan 16 20:54:11 Prometheus kernel: docker0: port 11(veth16f28b6) entered disabled state
Jan 16 20:54:11 Prometheus  avahi-daemon[3945]: Withdrawing address record for <MAC Address> on veth16f28b6.
Jan 16 20:54:11 Prometheus kernel: docker0: port 11(veth1a1e368) entered blocking state
Jan 16 20:54:11 Prometheus kernel: docker0: port 11(veth1a1e368) entered disabled state
Jan 16 20:54:11 Prometheus kernel: device veth1a1e368 entered promiscuous mode
Jan 16 20:54:11 Prometheus kernel: docker0: port 11(veth1a1e368) entered blocking state
Jan 16 20:54:11 Prometheus kernel: docker0: port 11(veth1a1e368) entered forwarding state
Jan 16 20:54:11 Prometheus kernel: eth0: renamed from vethd84bad5
Jan 16 20:54:11 Prometheus kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth1a1e368: link becomes ready
Jan 16 20:54:13 Prometheus  avahi-daemon[3945]: Joining mDNS multicast group on interface veth1a1e368.IPv6 with address <MAC Address>.
Jan 16 20:54:13 Prometheus  avahi-daemon[3945]: New relevant interface veth1a1e368.IPv6 for mDNS.
Jan 16 20:54:13 Prometheus  avahi-daemon[3945]: Registering new address record for <MAC Address> on veth1a1e368.*.

[Lee B]

I have the same issue, anyone resolved this ?