October 6, 20241 yr Made some hardware changes yesterday to the server, replacing the motherboard, CPU, RAM. I also installed a couple of 256GB SSDs that I plan to use for cache, but haven't done anything with them other than clearing them. Everything seemed to be working fine. Woke up this morning and couldn't access the server via WebGUI. I could ping it, but that was all. So I grabbed the keyboard and rebooted from the command line. Hoping someone can help me with the diagnostics. mytower-diagnostics-20241006-1040.zip
October 6, 20241 yr Community Expert The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field.
October 6, 20241 yr Author I ran diagnostics from the command line before I rebooted. I'm not sure how to retrieve that one though.
October 6, 20241 yr Author OK, I managed to figure it out. I believe this was from before the reboot. mytower-diagnostics-20241006-1027.zip
October 6, 20241 yr Community Expert Server is running out of RAM, and jellyfin appears to be the culprit, limit its Ram usage and check its settings.
October 6, 20241 yr Author 1 hour ago, JorgeB said: Server is running out of RAM, and jellyfin appears to be the culprit, limit its Ram usage and check its settings. OK. I only had 8GB before the hardware upgrade yesterday and never had a crash. Odd that I now have twice as much and ran out. Hmmm Edited October 6, 20241 yr by In2Photos
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.