My server has been crashing on a daily basis for the past couple of weeks. I restart it manually after the crash, which triggers a parity check. The log looks to me like a kernel panic, which immediately made me think it could be hardware related since I swapped my motherboard recently. However, the motherboard swap happened about 10 days before it started crashing daily. In that time, I remember trying to set up a docker compose for some new containers which continually locked up my server when I tried to run them. I moved the stack into portainer to be managed there and it seems to be fine from there.

 

I have run a memtest86 and it passed after running overnight.

 

I've attached the logs from right before the crash last night!

syslog-192.168.1.2.log.1

I'm having similar symptoms and I have not found any solutions yet. Does it still error when you put it in safe mode?

Dec 18 21:18:29 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Dec 18 21:18:29 Tower kernel: ? _raw_spin_unlock+0x14/0x29
Dec 18 21:18:29 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

 

Macvlan call traces will usually 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)), then reboot.