February 5, 20233 yr I have this deployed on a R730, and has been stable for over 2 years. But recently I find that everything becomes unresponsive and weird, and docker containers will show up but will not load or is unresponsive. I found that this time I was able to see a kernel panic in the log. This has been happening every 3ish days for a couples weeks now. Seems that it could be network releated but I figured I'd see if I could get soms support from the community. Feb 4 01:24:02 dot kernel: Call Trace: Feb 4 01:24:02 dot kernel: <IRQ> Feb 4 01:24:02 dot kernel: nf_conntrack_confirm+0x25/0x54 [nf_conntrack] Feb 4 01:24:02 dot kernel: nf_hook_slow+0x3d/0x96 Feb 4 01:24:02 dot kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Feb 4 01:24:02 dot kernel: NF_HOOK.constprop.0+0x79/0xd9 Feb 4 01:24:02 dot kernel: ? ip_protocol_deliver_rcu+0x164/0x164 Feb 4 01:24:02 dot kernel: ip_sabotage_in+0x4a/0x58 [br_netfilter] Feb 4 01:24:02 dot kernel: nf_hook_slow+0x3d/0x96 Feb 4 01:24:02 dot kernel: ? ip_rcv_finish_core.constprop.0+0x3b7/0x3b7 Feb 4 01:24:02 dot kernel: NF_HOOK.constprop.0+0x79/0xd9 Feb 4 01:24:02 dot kernel: ? ip_rcv_finish_core.constprop.0+0x3b7/0x3b7 Feb 4 01:24:02 dot kernel: __netif_receive_skb_one_core+0x77/0x9c Feb 4 01:24:02 dot kernel: process_backlog+0x8c/0x116 Feb 4 01:24:02 dot kernel: __napi_poll.constprop.0+0x2b/0x124 Feb 4 01:24:02 dot kernel: net_rx_action+0x159/0x24f Feb 4 01:24:02 dot kernel: __do_softirq+0x129/0x288 Feb 4 01:24:02 dot kernel: do_softirq+0x7f/0xab Feb 4 01:24:02 dot kernel: </IRQ> Feb 4 01:24:02 dot kernel: <TASK> Feb 4 01:24:02 dot kernel: __local_bh_enable_ip+0x4c/0x6b Feb 4 01:24:02 dot kernel: netif_rx+0x52/0x5a Feb 4 01:24:02 dot kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Feb 4 01:24:02 dot kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Feb 4 01:24:02 dot kernel: process_one_work+0x1ab/0x295 Feb 4 01:24:02 dot kernel: worker_thread+0x18b/0x244 Feb 4 01:24:02 dot kernel: ? rescuer_thread+0x281/0x281 Feb 4 01:24:02 dot kernel: kthread+0xe7/0xef Feb 4 01:24:02 dot kernel: ? kthread_complete_and_exit+0x1b/0x1b Feb 4 01:24:02 dot kernel: ret_from_fork+0x22/0x30 Feb 4 01:24:02 dot kernel: </TASK> Feb 4 01:24:02 dot kernel: ---[ end trace 0000000000000000 ]---
February 5, 20233 yr Community Expert 45 minutes ago, novistion said: Feb 4 01:24:02 dot kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Feb 4 01:24:02 dot kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] macvlan docker network type is the likely culprit, known issue and such a common problem in recent releases that it is no longer a default setting. To change, go to SETTINGS > DOCKER, then with advanced view toggled, set Enable Docker: No, then set Docker custom network type: ipvlan Once complete, set Enable Docker: Yes to restart docker service.
February 5, 20233 yr Author Solution 10 minutes ago, tjb_altf4 said: macvlan docker network type is the likely culprit, known issue and such a common problem in recent releases that it is no longer a default setting. To change, go to SETTINGS > DOCKER, then with advanced view toggled, set Enable Docker: No, then set Docker custom network type: ipvlan Once complete, set Enable Docker: Yes to restart docker service. I checked my settings and the docker network type was already macvlan. I do have the option for IP VLAN, but without tags unsure how I would be able to make that work if needed.
February 5, 20233 yr Community Expert 7 hours ago, novistion said: and the docker network type was already macvlan That's why you should change to ipvlan.
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.