[SOLVED] Repeat system hangs


Go to solution Solved by JorgeB,

Recommended Posts

Diagnostics attached for this last hang. Essentially my system will either completely hang or allow GUI access but be unable to shut down (with docker services stopped/etc) after 1 to several days.

 

I am running pi-hole docker as my DNS and I believe everything setup correctly. I have my server and router (r9000 running DDWRT) setup for IPV6. From a couple of obscure threads, I have seen that unraid may not handle IPV6 correctly? I was hoping after the last update to rc6.10 that there would be some relief to this issue.

 

Anyone have any insight. At my wits end on this one.

skrumpy-diagnostics-20220528-0638.zip

Edited by Skrumpy
Problem solved
Link to comment
  • Solution
May 25 20:58:07 Skrumpy kernel: macvlan_broadcast+0x116/0x144 [macvlan]
May 25 20:58:07 Skrumpy kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]

 

Macvlan call traces are usually the result of having dockers with a custom IP address, 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/

Link to comment
5 hours ago, JorgeB said:
May 25 20:58:07 Skrumpy kernel: macvlan_broadcast+0x116/0x144 [macvlan]
May 25 20:58:07 Skrumpy kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]

 

Macvlan call traces are usually the result of having dockers with a custom IP address, 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/

 

Changed that setting to ipvlan. Hopefully that works! I'll give it a go here over the next few days and see what happens. I'll update the thread if it happens again otherwise I'll mark it as resolved.

 

Thanks JorgeB for an option to try at least.

Link to comment
On 5/28/2022 at 7:45 AM, JorgeB said:
May 25 20:58:07 Skrumpy kernel: macvlan_broadcast+0x116/0x144 [macvlan]
May 25 20:58:07 Skrumpy kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]

 

Macvlan call traces are usually the result of having dockers with a custom IP address, 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/

 

Think this may have been the major source if not the total problem. Up 3+ days so far (restarted for something else earlier) without issue.. keeping my finger's crossed. Thanks again!

  • Like 1
Link to comment
  • Skrumpy changed the title to [SOLVED] Repeat system hangs

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.