July 10, 20232 yr In 15 years, this is the first time ever my server was completely unresponsive when I tried to log in this morning. I also could not SSH. I had to do a manual shut down and reboot. I'm not sure if the logs will be revealing, but they are attached. For what it's worth, I did a parity drive upgrade last week (larger drive) and then I upgraded one of the drives to a larger one. There were no errors during either procedure. The server has been running fine since (several days). Thanks for any advice. tower-diagnostics-20230710-0826.zip
July 10, 20232 yr Community Expert Diagnostics contains current syslog, which is in RAM like the rest of the OS. So diagnostics after reboot can only tell us what happened after boot. Setup syslog server
July 10, 20232 yr Community Expert Syslog starts over after every boot, if it happens again enable the syslog server and then post that after a crash.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.