Now I had some crashes and freezes with this server for some time now but wasn't able to find out what was wrong. In the last thread (

) I was advised to completely redo my cache array, which I did, and hoped for the best. But unfortunately the server has crashed again. However I did set up a syslog server in order to be able to see what was going on before the crash and I captured this as the last dying gasp:

Azeroth kernel: RIP: 0010:nf_nat_setup_info+0x12f/0x6d9 [nf_nat]

 

I have the whole syslog leading up to this in the attachements.

 

I have found a thread with people saying it has to do with their mikrotik network gear but I don't use any mikrotik gear. Has anyone any idea what this is and what I could do?

Thanks

All-Messages-search-result.csv

See if this applies to you, if yes, 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)), 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/

I am on 6.10 RC for a while now which has not changed this behaviour. Unfortunately this prticular server is in a network which does not support VLANs. I will probably upgrade this network to something that supports VLANs but not at the moment unfortunately. I do however use a custom docker net so the containers have an internal IP in the 172.18.0.0/16 range and the external IP (not external on the WAN but external on the LAN) of the server.