January 3, 20224 yr I've had this server for a number of years, transferred it to a new chassis almost a year ago, and haven't had too many issues up until recently. A number of times within the past few weeks I've ran into the GUI just stopping to work even though the server is still up and running (I can access SMB shares via my laptop and can putty into it, but some/most of the time the dockers stop when this happens). Usually a reboot fixes it. I haven't made any large changes recently (no new dockers in a while, no new disks, no major config changes). Today the GUI did something different and was still accessible and showed most of the header but nothing below that and none of the tab names worked when you clicked on them. I tried a change a friend suggested to the settings.cfg file for the nvidia driver (set disable_xconfig=true) and rebooted. Now the GUI just shows ERR_CONNECTION_REFUSED. I can putty in so I grabbed the diagnostics file. If anyone can look through this as I'm not familiar with where to look for issues, I'd greatly appreciate it. tower-diagnostics-20220103-1054.zip
January 3, 20224 yr Community Expert Solution Jan 3 01:13:42 Tower kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Jan 3 01:13:42 Tower kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
January 3, 20224 yr Author 4 hours ago, JorgeB said: Jan 3 01:13:42 Tower kernel: macvlan_broadcast+0x10e/0x13c [macvlan] Jan 3 01:13:42 Tower kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, upgrading to v6.10 and switching to ipvlan might fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/ I was finally able to get into the UI so I upgraded to v6.10 and then disabled docker to change macvlan to ipvlan. The UI went down and I can't seem to figure out how to gain access back to it to continue, nor can I find where in some config file I can make the change. I disabled SSL, renamed the docker image, and was finally able to get into the UI to make the change. I then renamed the docker image back and rebooted again. Everything came back up. I finally turned SSL back on. If I notice it locking up in the future, I'll have to try creating the VLAN for my docker containers as the first link suggests. Thanks for the help and here's to hoping that change fixes things and keeps it running smoothly! Edited January 3, 20224 yr by snowborder714
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.