I've just had this happen again on my server after about 180 days uptime so I have no idea what is causing it. Has anyone had any luck? My server became unresponsive May 2 approx 8:59 and I rebooted at 13:33.
I did enable mirroring syslog to flash so I have this but it doesn't appear useful to me:
May 2 05:31:40 NASsy kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8a7d9f3: link becomes ready
May 2 05:31:40 NASsy kernel: docker0: port 7(veth8a7d9f3) entered blocking state
May 2 05:31:40 NASsy kernel: docker0: port 7(veth8a7d9f3) entered forwarding state
May 2 05:32:00 NASsy CA Backup/Restore: #######################
May 2 05:32:00 NASsy CA Backup/Restore: appData Backup complete
May 2 05:32:00 NASsy CA Backup/Restore: #######################
May 2 05:32:00 NASsy CA Backup/Restore: Deleting /mnt/user/backups/AppdataBackup/
[email protected]
May 2 05:32:00 NASsy CA Backup/Restore: Backup / Restore Completed
May 2 05:32:12 NASsy nginx: 2022/05/02 05:32:12 [error] 17190#17190: *14284161 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /admin/api.php?version HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "127.0.0.1"
May 2 05:32:12 NASsy nginx: 2022/05/02 05:32:12 [error] 17190#17190: *14284163 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 127.0.0.1, server: , request: "GET /admin/api.php?version HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost"
May 2 07:42:45 NASsy apcupsd[14578]: Power failure.
May 2 07:42:45 NASsy apcupsd[14578]: Power is back. UPS running on mains.
May 2 07:42:46 NASsy apcupsd[14578]: Power failure.
May 2 07:42:46 NASsy apcupsd[14578]: Power is back. UPS running on mains.
May 2 07:43:02 NASsy kernel: TCP: request_sock_TCP: Possible SYN flooding on port 32033. Sending cookies. Check SNMP counters.
May 2 08:33:01 NASsy kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
May 2 08:33:01 NASsy kernel: caller _nv000712rm+0x1af/0x200 [nvidia] mapping multiple BARs
May 2 13:33:33 NASsy kernel: Linux version 5.10.21-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Sun Mar 7 13:39:02 PST 2021
Additionally, I thought maybe it was an out of memory issue so I wrote a script to log memory usage (free -m) every minute to a file. Seems to be plenty of memory available but this has the added benefit of knowing when the server became unresponsive:
date time total used free shared buff/cache available
2022-05-02 08:57:52 32095 10222 417 1661 21455 19770
2022-05-02 08:58:52 32095 10235 398 1661 21461 19757
2022-05-02 08:59:52 32095 10245 379 1661 21470 19747