May 14, 20233 yr Hello My server version is 6.11.5 and I have been experiencing crashes and crashes recently I read the system log and found that it is a kernel error I hope to get your help here Supermicro X10SRL-F Intel® Xeon® CPU E5-2618L v3 @ 2.30GHz Linux 5.19.17-Unraid x86_64 bond0: fault-tolerance (active-backup), mtu 1500 May 13 01:12:03 Tower kernel: WARNING: CPU: 6 PID: 1845 at net/netfilter/nf_conntrack_core.c:1208 __nf_conntrack_confirm+0xa5/0x2cb [nf_conntrack] syslog-192.168.1.9.log Edited May 14, 20233 yr by yanju
May 14, 20233 yr Author May 14 09:07:16 Tower mcelog: Kernel in lockdown. Cannot enable DIMM error location reporting syslog.txt
May 15, 20233 yr Community Expert On 5/14/2023 at 2:55 AM, yanju said: Cannot enable DIMM error location reporting This is harmless, these are not: May 10 00:19:52 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] May 10 00:19:52 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
May 15, 20233 yr Author 51 minutes ago, JorgeB said: This is harmless, these are not: May 10 00:19:52 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] May 10 00:19:52 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)). Thanks I will try to do this
May 18, 20233 yr Author On 5/15/2023 at 6:23 PM, JorgeB said: This is harmless, these are not: May 10 00:19:52 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] May 10 00:19:52 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)). Hello I switched to ipvlan But my custom docker server SHH can't connect, is there any way to solve it? There is no problem under Macvlan
May 18, 20233 yr Community Expert If using ipvlan doesn't work for you, other options are disabling bridge and use macvlan if no VM needs it or use two NICs.
May 18, 20233 yr Author 4 hours ago, JorgeB said: If using ipvlan doesn't work for you, other options are disabling bridge and use macvlan if no VM needs it or use two NICs. Thanks I will try to do this
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.