Full Logs


Recommended Posts

Feb 22 18:33:49 MOORETOWER kernel: macvlan_broadcast+0x10e/0x13c [macvlan]
Feb 22 18:33:49 MOORETOWER 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/

Link to comment
16 minutes ago, Its Andrew said:

Does ipvlan work if my switch doesn't support vlans?

I think this is only within Unraid.

 

44 minutes ago, Its Andrew said:

my docker image seems to be getting corrupt on a weekly basis with the unclean shutdowns that are occurring

Might be the shutdowns, might be an issue with your RAM. You should run a few passes of Memtest to be sure there are no issues there.

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.