Server crashing - Just halts

[Fuzzydamnt]

Seeing this after a server halt and reset:
 

Feb 20 11:01:08 unraid1 kernel: CPU: 17 PID: 2239 Comm: kworker/17:2 Not tainted 5.10.28-Unraid #1
Feb 20 11:01:08 unraid1 kernel: Hardware name: empty empty/ S7050 , BIOS V1.09 07/01/2014
Feb 20 11:01:08 unraid1 kernel: Workqueue: events macvlan_process_broadcast [macvlan]
Feb 20 11:01:08 unraid1 kernel: RIP: 0010:__nf_conntrack_confirm+0x9b/0x1e6 [nf_conntrack]
Feb 20 11:01:08 unraid1 kernel: Code: e8 dc f8 ff ff 44 89 fa 89 c6 41 89 c4 48 c1 eb 20 89 df 41 89 de e8 36 f6 ff ff 84 c0 75 bb 48 8b 85 80 00 00 00 a8 08 74 18 <0f> 0b 89 df 44 89 e6 31 db e8 6d f3 ff ff e8 35 f5 ff ff e9 22 01
Feb 20 11:01:08 unraid1 kernel: RSP: 0018:ffffc90006740dd8 EFLAGS: 00010202
Feb 20 11:01:08 unraid1 kernel: RAX: 0000000000000188 RBX: 0000000000009958 RCX: 00000000543248e6
Feb 20 11:01:08 unraid1 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffffa00d9760
Feb 20 11:01:08 unraid1 kernel: RBP: ffff8883866788c0 R08: 00000000f01bcf21 R09: 0000000000000000
Feb 20 11:01:08 unraid1 kernel: R10: 0000000000000098 R11: ffff88811efe9400 R12: 0000000000005c24
Feb 20 11:01:08 unraid1 kernel: R13: ffffffff8210b440 R14: 0000000000009958 R15: 0000000000000000
Feb 20 11:01:08 unraid1 kernel: FS: 0000000000000000(0000) GS:ffff88903fcc0000(0000) knlGS:0000000000000000
Feb 20 11:01:08 unraid1 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 20 11:01:08 unraid1 kernel: CR2: 0000152b19cdf020 CR3: 000000000200a004 CR4: 00000000000626e0
Feb 20 11:01:08 unraid1 kernel: Call Trace:
Feb 20 11:01:08 unraid1 kernel: <IRQ>
Feb 20 11:01:08 unraid1 kernel: nf_conntrack_confirm+0x2f/0x36 [nf_conntrack]
Feb 20 11:01:08 unraid1 kernel: nf_hook_slow+0x39/0x8e
Feb 20 11:01:08 unraid1 kernel: nf_hook.constprop.0+0xb1/0xd8
Feb 20 11:01:08 unraid1 kernel: ? ip_protocol_deliver_rcu+0xfe/0xfe
Feb 20 11:01:08 unraid1 kernel: ip_local_deliver+0x49/0x75
Feb 20 11:01:08 unraid1 kernel: __netif_receive_skb_one_core+0x74/0x95
Feb 20 11:01:08 unraid1 kernel: process_backlog+0xa3/0x13b
Feb 20 11:01:08 unraid1 kernel: net_rx_action+0xf4/0x29d
Feb 20 11:01:08 unraid1 kernel: __do_softirq+0xc4/0x1c2
Feb 20 11:01:08 unraid1 kernel: asm_call_irq_on_stack+0x12/0x20
Feb 20 11:01:08 unraid1 kernel: </IRQ>
Feb 20 11:01:08 unraid1 kernel: do_softirq_own_stack+0x2c/0x39
Feb 20 11:01:08 unraid1 kernel: do_softirq+0x3a/0x44
Feb 20 11:01:08 unraid1 kernel: netif_rx_ni+0x1c/0x22
Feb 20 11:01:08 unraid1 kernel: macvlan_broadcast+0x10e/0x13c [macvlan]
Feb 20 11:01:08 unraid1 kernel: macvlan_process_broadcast+0xf8/0x143 [macvlan]
Feb 20 11:01:08 unraid1 kernel: process_one_work+0x13c/0x1d5
Feb 20 11:01:08 unraid1 kernel: worker_thread+0x18b/0x22f
Feb 20 11:01:08 unraid1 kernel: ? process_scheduled_works+0x27/0x27
Feb 20 11:01:08 unraid1 kernel: kthread+0xe5/0xea
Feb 20 11:01:08 unraid1 kernel: ? __kthread_bind_mask+0x57/0x57
Feb 20 11:01:08 unraid1 kernel: ret_from_fork+0x22/0x30
Feb 20 11:01:08 unraid1 kernel: ---[ end trace adb94111a3fb6545 ]---

 

Can anyone tell by looking at that what is going on?

 

I see "OS Critical Stop" and "Run-Timei Critical Stop - Asserted" is the IMPI event logs.

 

and no timei is not a typo

 

[Hoopster]

52 minutes ago, Fuzzydamnt said:

Can anyone tell by looking at that what is going on?

 

You probably have a custom IP address assigned to one or more docker containers which are causing your crashes.

Edited February 20, 2022 by Hoopster

[JorgeB]

Also 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))