September 11, 20241 yr Hey All, I have a power outage and on restart, I've had some weird network issues since restarting. When I restart and remove I mount the array, I have full network on unraid, I can ping google etc. When I mount the array (which starts all my docker containers) I have a connection for about 10 seconds and then it dies, I can still access the web Ui but unraid can't reach Google and all my docker containers show they are up but the web UI and stuff are unreachable and the logs show it is timing out as the try reach external things. Pinging during the array start, the 400ms change ``` root@Rocinante:~# ping google.com PING google.com (142.250.70.206) 56(84) bytes of data. 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=1 ttl=60 time=2.74 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=2 ttl=60 time=1.90 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=3 ttl=60 time=1.94 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=4 ttl=60 time=2.80 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=5 ttl=60 time=2.00 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=6 ttl=60 time=2.14 ms ... 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=65 ttl=60 time=2.10 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=66 ttl=60 time=2.12 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=67 ttl=60 time=2.74 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=68 ttl=60 time=2.72 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=69 ttl=110 time=404 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=70 ttl=110 time=405 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=71 ttl=110 time=404 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=72 ttl=110 time=405 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=73 ttl=110 time=405 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=74 ttl=110 time=405 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=75 ttl=110 time=404 ms 64 bytes from mel05s01-in-f14.1e100.net (142.250.70.206): icmp_seq=76 ttl=110 time=407 ms ``` After ``` root@Rocinante:~# ping google.com PING google.com (142.250.70.174) 56(84) bytes of data. ^C --- google.com ping statistics --- 8 packets transmitted, 0 received, 100% packet loss, time 7149ms ``` I noticed this getting spammed in my syslog ``` Sep 11 20:26:05 Rocinante kernel: vethd9cdd38: renamed from eth0 Sep 11 20:26:05 Rocinante kernel: br-fa8dec63aaac: port 2(vethcb937c5) entered disabled state Sep 11 20:26:06 Rocinante kernel: br-fa8dec63aaac: port 2(vethcb937c5) entered disabled state Sep 11 20:26:06 Rocinante kernel: device vethcb937c5 left promiscuous mode Sep 11 20:26:06 Rocinante kernel: br-fa8dec63aaac: port 2(vethcb937c5) entered disabled state Sep 11 20:26:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered blocking state Sep 11 20:26:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered disabled state Sep 11 20:26:08 Rocinante kernel: device veth7108d6a entered promiscuous mode Sep 11 20:26:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered blocking state Sep 11 20:26:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered forwarding state Sep 11 20:26:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered disabled state Sep 11 20:26:10 Rocinante kernel: eth0: renamed from vetha9d430b Sep 11 20:26:10 Rocinante kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7108d6a: link becomes ready Sep 11 20:26:10 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered blocking state Sep 11 20:26:10 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered forwarding state Sep 11 20:29:02 Rocinante kernel: veth653fe1e: renamed from eth0 Sep 11 20:29:02 Rocinante kernel: br-fa8dec63aaac: port 1(veth247469c) entered disabled state Sep 11 20:29:02 Rocinante kernel: br-fa8dec63aaac: port 1(veth247469c) entered disabled state Sep 11 20:29:02 Rocinante kernel: device veth247469c left promiscuous mode Sep 11 20:29:02 Rocinante kernel: br-fa8dec63aaac: port 1(veth247469c) entered disabled state Sep 11 20:29:05 Rocinante kernel: br-fa8dec63aaac: port 1(vethbceda4d) entered blocking state Sep 11 20:29:05 Rocinante kernel: br-fa8dec63aaac: port 1(vethbceda4d) entered disabled state Sep 11 20:29:05 Rocinante kernel: device vethbceda4d entered promiscuous mode Sep 11 20:29:06 Rocinante kernel: eth0: renamed from veth9a12e9a Sep 11 20:29:06 Rocinante kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethbceda4d: link becomes ready Sep 11 20:29:06 Rocinante kernel: br-fa8dec63aaac: port 1(vethbceda4d) entered blocking state Sep 11 20:29:06 Rocinante kernel: br-fa8dec63aaac: port 1(vethbceda4d) entered forwarding state Sep 11 20:29:07 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered disabled state Sep 11 20:29:07 Rocinante kernel: vetha9d430b: renamed from eth0 Sep 11 20:29:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered disabled state Sep 11 20:29:08 Rocinante kernel: device veth7108d6a left promiscuous mode Sep 11 20:29:08 Rocinante kernel: br-fa8dec63aaac: port 2(veth7108d6a) entered disabled state Sep 11 20:29:10 Rocinante kernel: br-fa8dec63aaac: port 2(veth69c3a92) entered blocking state Sep 11 20:29:10 Rocinante kernel: br-fa8dec63aaac: port 2(veth69c3a92) entered disabled state Sep 11 20:29:10 Rocinante kernel: device veth69c3a92 entered promiscuous mode Sep 11 20:29:12 Rocinante kernel: eth0: renamed from vethc75d97f Sep 11 20:29:12 Rocinante kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth69c3a92: link becomes ready Sep 11 20:29:12 Rocinante kernel: br-fa8dec63aaac: port 2(veth69c3a92) entered blocking state Sep 11 20:29:12 Rocinante kernel: br-fa8dec63aaac: port 2(veth69c3a92) entered forwarding state ``` I have DHCP starting at 100 and have a static IP set on the unraid machine below DHCP. Im honestly kinda stumped at what might be causing things.
September 11, 20241 yr Community Expert 8 minutes ago, ALameLlama said: I noticed this getting spammed in my syslog This suggest a container continually trying to restart. You should be able to work out which one by looking at the uptime on the docker tab.
September 11, 20241 yr Author I ended up shutting down all the docker containers to see if that was messing with the interfaces but even with them all down, unraid still doesn't seem to have internet connection outbound
September 12, 20241 yr Author Solution This ended up being gluetun messing up my interfaces on the host. reset it gluetun and that resolved my issues after a reboot
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.