system becomes unresponsive after >= 8 Hours of inactivity.

[Marco Mosso]

As usual, after first installation (trial version) and initial setup, the system becomes unresponsive after more of 8 hours of inactivity. See attached diagnostic and file messages.txt (syslog from my qnap server).

I really don't have idea what could be the problem...

I've read something of similar in the thead but the suggested solution (ipvlan) is already set.

Please help me to find the problem I can't really where crash my head...

Thank

Marco

domain.cfg cache.cfg docker.cfg rsyslog.conf super.dat rsyslog.cfg ident.cfg share.cfg network.cfg go.txt disk.cfg smart-one.cfg Patriot_M.2_P300_512GB_P300EDCB22122802311-20230402-1140 cache2 (nvme1).txt nvme.1e4b-50333030454443423232313232383032333131-50617472696f74204d2e322050333030203531324742-00000001-20230402-1140 cache2 (nvme1).txt Samsung_SSD_870_QVO_2TB_S5RPNF0TB13876E-20230402-1140 parity (sdb).txt Intenso_SSD_Sata_III_AA00000000000750-20230402-1140 (sdd).txt Patriot_M.2_P300_512GB_P300EDCB22122802131-20230402-1140 cache (nvme0).txt Samsung_SSD_870_QVO_2TB_S5RPNF0TB13932Y-20230402-1140 disk1 (sdc).txt USB_SanDisk_3.2Gen1_0501077b19cd2f4c4e4b6f6e5ab646dec2702dcfd47a732c27a32397c804464464ee000000000000000000004a2feb9fff080610835581078cac198f-0-0-20230402-1140 flash (sda).txt nvme.1e4b-50333030454443423232313232383032313331-50617472696f74204d2e322050333030203531324742-00000001-20230402-1140 cache (nvme0).txt cmdline.txt btrfs-usage.txt drm.txt unraid-api.txt plugins.txt motherboard.txt iommu_groups.txt ethtool.txt folders.txt lsmod.txt lsscsi.txt loads.txt memory.txt lspci.txt meminfo.txt lsusb.txt urls.txt top.txt ps.txt vars.txt lscpu.txt lsof.txt df.txt ifconfig.txt dhcplog.txt docker.txt syslog.txt unraid-6.11.5.txt appdata.cfg domains.cfg L---a.cfg isos.cfg U-------------a (1).cfg A----s.cfg system.cfg N----e.cfg shareDisks.txt U-------------a.cfg n-------d.cfg m---o.cfg messages.txt

[JorgeB]

Next time please post the single diagnostics zip instead, enable the syslog server and post that after a crash.

[Marco Mosso]

Excuse me for wrong attachment. The syslog is the last before the "suspend". I've made diagnostic when I've restarded the pc.

[JorgeB]

Regular syslog starts over after every reboot.

[Marco Mosso]

Again excuse me for long syslog. The syslog of my snap is continuous. Please any suggestion about this problem ?

[JorgeB]

And where is that syslog?

[Marco Mosso]

the file is message.txt and at the bottom of this file you can find the last messages before the problem. This log contains more days and I've decided to maintain all because in previous days was reported the same error in continuous (but I don't have idea what is the problem).

[JorgeB]

There are basically continuous call traces on the 25th, not clear to me the cause, possibly hardware related, if it's only after some inactivity try disabling C-Sates in the BIOS, one other thing you can try is to boot the server in safe mode with all docker/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.

[Marco Mosso]

Ok. Domani provo.

[Marco Mosso]

I've made as suggested.

1 - Saturday morning started Unraid with only array up and docker down.

2 - At 12:00 AM I've started Docker DuckDns, Swag and MariaDB. Nextcloud off. No problems for all the next night.  

3 - Sunday morning at 8:00 AM I've seen that network for MariaDB was set to Bridge instead of the other attached docker (Nextcloud and Swag have network setting with a custom network "proxy net"). Set network for MariaDB same as Nextcloud and Swag.

4 Now is Monday 10 18:54 PM and all works fine. No more problems. 

I think I've found the problem.

Thank you.

Edited April 10, 2023 by Marco Mosso
Wrong word