January 22, 20206 yr Hi, My server has crashed about once every 1-2 days ever since I got it up and running. By crashed I mean that it continues to be powered on, but its not response to any connection requests of any kind, neither is my network equipment reading the server as being connected to the network. I see no errors in the log when the server should have crashed. Actually I see no entries of note at all. The following is an example from a log: Jan 22 06:45:16 Vault webGUI: Successful login user root from 192.168.1.10 Jan 22 06:50:58 Vault nginx: 2020/01/22 06:50:58 [error] 3704#3704: *445774 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.10, server: , request: "GET /webGui/include/ShareList.php?compute=yes&path=Shares&scale=-1&number=.%2C&fill=ssz HTTP/2.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "vault", referrer: "https://vault/Shares" Jan 22 07:24:56 Vault kernel: mdcmd (97): spindown 2 Jan 22 07:30:08 Vault kernel: mdcmd (98): spindown 3 Jan 22 10:19:18 Vault kernel: mdcmd (99): spindown 2 Jan 22 10:19:19 Vault kernel: mdcmd (100): spindown 3 Jan 22 11:26:43 Vault kernel: mdcmd (101): spindown 3 Jan 22 12:33:46 Vault kernel: mdcmd (102): spindown 3 Jan 22 13:03:22 Vault kernel: mdcmd (103): spindown 2 Jan 22 13:13:35 Vault kernel: mdcmd (104): spindown 3 Jan 22 16:39:06 Vault kernel: mdcmd (105): spindown 0 Jan 22 16:39:07 Vault kernel: mdcmd (106): spindown 1 Jan 22 19:48:47 Vault kernel: Linux version 4.19.94-Unraid (root@Develop) (gcc version 9.2.0 (GCC)) #1 SMP Thu Jan 9 08:20:36 PST 2020 The server has crashed somewhere between 10:00:00, where I know there was a succesfull Plex connection, and 19:48:47 when I forced the server to reboot. The server is connected to a UPS and all hardware was pretested before being put to use in the system... Anyone have any idea why my server keeps dying?
January 22, 20206 yr Community Expert Are you using a Ryzen based server by any chance? You should always post the diagnostics: Tools -> Diagnostics
January 22, 20206 yr Author 23 minutes ago, johnnie.black said: Are you using a Ryzen based server by any chance? You should always post the diagnostics: Tools -> Diagnostics Yep, Ryzen 1700. Diagnostics attached. vault-diagnostics-20200122-2039.zip
January 22, 20206 yr Community Expert Ryzen on Linux can lock up due to issues with c-states, make sure bios is up to date, then look for "Power Supply Idle Control" (or similar) and set it to "typical current idle" (or similar), or completely disable C-sates. More info here: https://forums.unraid.net/bug-reports/prereleases/670-rc1-system-hard-lock-r354/
February 1, 20206 yr Author I let it run for a few days after changing the C-states and now it runs without hickups
Archived
This topic is now archived and is closed to further replies.