hfuhruhurr Posted May 12, 2022 Share Posted May 12, 2022 I have updated to the v6.10.rc8 version and have been able to setup the new VPN capability. However, I still have system crashes every few days. I have attached the latest log and diagnostics for review. syslog-192.168.1.140_after_crash_5-11-21.log mongo-diagnostics-20220511-1702.zip Quote Link to comment
JorgeB Posted May 12, 2022 Share Posted May 12, 2022 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/ Quote Link to comment
hfuhruhurr Posted May 12, 2022 Author Share Posted May 12, 2022 Thank you for the suggestion. I don't have any docker containers with a custom IP address. Is this error relevant if I am not using any custom IP adresses? Thanks, Donn Quote Link to comment
hfuhruhurr Posted May 12, 2022 Author Share Posted May 12, 2022 Also, the crashes occurred on 5/10 and 5/11. Quote Link to comment
JorgeB Posted May 12, 2022 Share Posted May 12, 2022 Should still change that, something is using macvlan, and those call traces later usually result in a total server crash. Quote Link to comment
hfuhruhurr Posted May 12, 2022 Author Share Posted May 12, 2022 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 Quote Link to comment
Recommended Posts
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.