Jump to content

Unraid crash Unresponsive v6.10.rc8


Recommended Posts

May  8 15:38:25 Mongo kernel: macvlan_broadcast+0x116/0x144 [macvlan]
May  8 15:38:25 Mongo 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

Ok, I have changed to IPVLAN ( I tried this a few days ago and the vpntunnel stopped working). This time I set the flag "Host access to custom networks" to Disabled as suggested on another thread. Will update on any effects/changes.

 

Just a question. Is this issue unique to unRaid? I have been using docker macvlans on other servers for years with no issues. It seems I am forfeiting some serious capability by abandoning macvlan functionality and wonder if there is an effort in development to resolve this issue, or if this is purely hardware related.

 

Thanks,

Donn

Link to comment

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.

×
×
  • Create New...