Server suddenly not reachable

[geefle]

Hi My server is a couple of weeks old. I am almost done setting everything up and it has been running stable for over two weeks.

Suddenly it is not reachable over the network.

 

Plugging in a monitor does not show a picture. Because I experienced this before I mirrored the syslog to flash:

 

Mar 14 11:47:10 host kernel: ret_from_fork+0x1f/0x30
Mar 14 11:47:10 host kernel: ---[ end trace 391c513f82e9a404 ]---
Mar 14 13:52:58 host webGUI: Successful login user root from 192.168.0.206
Mar 14 14:06:55 host emhttpd: spinning down /dev/sdf
Mar 14 15:19:54 host emhttpd: read SMART /dev/sdb
Mar 14 16:41:53 host kernel: Linux version 5.10.28-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Wed Apr 7 08:23:18 PDT 2021
Mar 14 16:41:53 host kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot
Mar 14 16:41:53 host kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Mar 14 16:41:53 host kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'

 

Because today I installed pihole, I can pinpoint the time it stopped working pretty well around 16:30. The Syslog does not seem to contain any info that is helpful.

 

Does anyone have any idea how I can have more info in the logs?

[geefle]

The server just crashed again. Suddenly all the fans spun up and I could not reach it. This time there was a weird message in sys log at ~17:16

 

I now turned off the pihole docker container, since this is the only thing I changed today.

Still any ideas are welcome.

syslog(1)

[Hoopster]

6 minutes ago, geefle said:

any ideas are welcome.

Full diagnostics are much more helpful than just syslog or syslog snippets.  Tools-->Diagnostics in the GUI or 'diagnostics' typed from the command line.  Attach the *.zip file to a new post.

[geefle]

Diagonostics

nashorn2-diagnostics-20220314-2123.zip

[geefle]

Now that I stopped the pi-hole container, the system has been running without a problem. I wonder if it could be a ram problem

[geefle]

The system has been running fine for about 4 weeks, and since middle of last week I keep having that effect where the system is not reachable. the last instance was sometime today. When I connected a monitor to the NAS I could see the logon prompt and interact with it. It would tell me when the logon was incorrect. When it was correct (presumeably) nothing happened.

 

Since the issues from March, I have the syslog mirrored to the flash drive. I attached it in addition to the diagnostics. Can anyone see what is going wrong? At the moment this is so unreliable It is unusable.

 

nashorn2-diagnostics-20220605-1408.zip syslog(3).zip

[JorgeB]

Jun  4 09:09:41 NASHorn2 kernel: macvlan_broadcast+0x116/0x144 [macvlan]
Jun  4 09:09:41 NASHorn2 kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan]

 

Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan should 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/

[geefle]

Thank you for the quick reply. I will look into that. Just out of curiosity: Is that a Linux bug then?