May 8, 20179 yr Fix common problems started telling me yesterday that call traces were found on my server. FCP has never reported call traces until the scan on 07-May-2017 and it runs weekly. Diags are attached. I did notice that Plex Media Server wasn't actually WORKING, but the docker container was running. Upon restarting the docker container PMS resumed normal functionality but I had to force refresh of libraries to pick up new titles that were added since it "crashed". Server wasn't doing anything other than usenet searches, downloads, and PMS playback, that I am aware of. Scheduled parity check passed last night. One thing to note is that the array drives are VERY full with four under 50GB free and one around 300GB. I know that's not optimal operating condition. I'm putting in an additional drive for preclear after I post this. Thanks for any help! elsa-unraid-diagnostics-20170508-1306.zip
May 8, 20179 yr 3 hours ago, jonesy8485 said: Fix common problems started telling me yesterday that call traces were found on my server. FCP has never reported call traces until the scan on 07-May-2017 and it runs weekly. Diags are attached. I did notice that Plex Media Server wasn't actually WORKING, but the docker container was running. Upon restarting the docker container PMS resumed normal functionality but I had to force refresh of libraries to pick up new titles that were added since it "crashed". Server wasn't doing anything other than usenet searches, downloads, and PMS playback, that I am aware of. Scheduled parity check passed last night. One thing to note is that the array drives are VERY full with four under 50GB free and one around 300GB. I know that's not optimal operating condition. I'm putting in an additional drive for preclear after I post this. Thanks for any help! elsa-unraid-diagnostics-20170508-1306.zip Probably harmless. They were "page allocation stalls"... My understanding is the computer had a brain-fart. Looks like nzbGet started an unrar at the time. Probably ok to ignore, but if it continually happens, could consider limiting the RAM available to the nzbget app. Beyond that, you've got pointless logging from mover continually filling up the logs when it runs. If you've got no issues, would probably be a good idea to disable mover logging, as if the log happens to completely fill you'll have other problems, and it looks like you have good uptime (Settings - scheduler - mover settings)
May 8, 20179 yr Author 6 minutes ago, Squid said: Probably harmless. They were "page allocation stalls"... My understanding is the computer had a brain-fart. Looks like nzbGet started an unrar at the time. Probably ok to ignore, but if it continually happens, could consider limiting the RAM available to the nzbget app. Beyond that, you've got pointless logging from mover continually filling up the logs when it runs. If you've got no issues, would probably be a good idea to disable mover logging, as if the log happens to completely fill you'll have other problems, and it looks like you have good uptime (Settings - scheduler - mover settings) Great news. Thanks! And yeah since I've quit toying with the server so much, uptime has been great. I did have an issue with the log filling up one time. Thanks for tip. It's now disabled.
Archived
This topic is now archived and is closed to further replies.