February 2, 20251 yr Hi, After upgrading to Unraid 7 (did not notice this problem on the beta that i was running before upgrading), i have a problem with my network seem to reset every night at alittle bit after 04 each night. This results in VM's loosing connection to their shares, same with dockers and that that server becomes unreachable for a short while. I have tasks running on the vm's and dockers 24/7, and the result is that all of this tasks errors out. The only thing i find in the logs are: Feb 2 04:40:02 Enterprise kernel: docker0: port 8(vethc0899d8) entered blocking state Feb 2 04:40:02 Enterprise kernel: docker0: port 8(vethc0899d8) entered disabled state Feb 2 04:40:02 Enterprise kernel: vethc0899d8: entered allmulticast mode Feb 2 04:40:02 Enterprise kernel: vethc0899d8: entered promiscuous mode Feb 2 04:40:05 Enterprise kernel: eth0: renamed from veth5008833 Feb 2 04:40:05 Enterprise kernel: docker0: port 8(vethc0899d8) entered blocking state Feb 2 04:40:05 Enterprise kernel: docker0: port 8(vethc0899d8) entered forwarding state Feb 2 04:42:30 Enterprise kernel: docker0: port 8(vethc0899d8) entered disabled state Feb 2 04:42:30 Enterprise kernel: veth5008833: renamed from eth0 Feb 2 04:42:30 Enterprise kernel: docker0: port 8(vethc0899d8) entered disabled state Feb 2 04:42:30 Enterprise kernel: vethc0899d8 (unregistering): left allmulticast mode Feb 2 04:42:30 Enterprise kernel: vethc0899d8 (unregistering): left promiscuous mode Feb 2 04:42:30 Enterprise kernel: docker0: port 8(vethc0899d8) entered disabled state I guess these messages is related to what is happening. Any idea of what is going on here, and eventually how to fix it?
February 2, 20251 yr Community Expert those messages just let you know that a container started and stopped. Otherwise without any diagnostics, its akin to fortune telling
February 2, 20251 yr Author Aha , don't know why i have containers restarting at the middle of the night for that sake either, but thats a problem for another day. Anyway, have run the diagnostic tool, and supplying the logs here. enterprise-diagnostics-20250202-1301.zip
February 2, 20251 yr Community Expert you must have something scheduled that starts that container at 4:40 and turns off after its done whatever its doing. But what that container is and what that container does 🤷♂️ There isnt anything else in there, at that time, that suggest any issue with networking.
February 2, 20251 yr Community Expert 4:40 is the default daily schedule cron entry, see if you have a script doing something daily.
February 2, 20251 yr Community Expert Don't see anything in the logs that explains that, try disabling any scripts or plugins that you have running during the night, or boot in safe mode and retest.
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.