techlovin

Members
  • Posts

    45
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

techlovin's Achievements

Rookie

Rookie (2/14)

0

Reputation

  1. Issues with my Plex db caused the container to consume all available RAM, eventually grinding my server to a complete halt killing off most functionality. After several hours Unraid would kill the process consuming all available memory and service would be restored. No issues with the Plex scheduled tasks turned off. I noticed some Plex log entries about this that made me believe the scanner was getting hung up trying to match some of the files. I deleted my hentai library which was using the hama.bundle plugin. Turned the tasks back on yesterday after deleting a few libraries, and did not notice the memory issue or my server locking up. Will monitor for a couple days and If no more issues crop up I'll mark this as resolved.
  2. This is absolutely an issue with my Plex docker. Memory keeps ballooning during PlexScan and locking up the server until the process is killed.
  3. Agreed, I may have been too hasty in assuming it was a crash. It happened again this morning and I just ignored it, left it to go to work and noticed it was online without requiring me to force shutdown. Reviewed the logs (mirrored to flash) and I see a massive wall of stuff happening around 5-6hrs after it went offline. I've attached the log, can anyone explain what I'm seeing there at line 2544, at Jan 1 09:13:30? Update: Well damn! Just noticed I have scheduled tasks to begin in Plex at 3AM, this is when my issues are popping up around 3:15am!!! Referencing the syslog I can see an out of memory warning... Not sure where things went wrong but I must've accidentally mis-configured something. Though I haven't touched my Plex settings in several months as far as I recall. Any tips on what to check for these memory issues with Plex? (Reminder, my RAM passed an exhaustive memtest.) Update2: My working theory is my Plex db may have corruption. Running an integrity check on it now. Following this guide. Not sure how long it will take, need to sleep, will check back in the morning.
  4. 10 passes, 18+ hrs and no errors. Definitely looks like its not a memory issue. I've replaced the flash drive, and I've disabled C states globally. I'm pretty sure this is a software issue, whether thats something with my dockers, or something Ive configured in Unraid.
  5. I'm currently on Pass 3 of Memtest without any errors. Planning to go for the rest of the day.
  6. Attached the most recent diagnostics, friday-diagnostics-20231231-0337.zip
  7. Shutdown again, at exactly 3:15am, nothing in the syslog. Froze, couldn't access the GUI, shares, or any containers. Is there someway I can check to see what it may be doing at that time? I've connected a monitor to it so that I might be able to see something. I've set up the syslog to mirror to flash in-case something is being missed. Edit: Each time it's done this the last three days I could see the light blinking on my Unraid flash drive. I waited it out once for a couple hours but it was still down. The last two days I've just been doing an unclean shutdown and rebooting. While it happens I'm just streaming Plex from my server. Edit2: Went down again, less than 45mins after the first freeze. Running MemTest now, will update this thread after an extended test.
  8. Noticed a warning in my syslog. 2023-12-30T22:35:01-08:00 Friday kernel: TCP: request_sock_TCP: Possible SYN flooding on port 8181. Sending cookies. Check SNMP counters. :8181 is my Tautulli container. Checked logs and found the following. 2023-12-30 22:35:40 - ERROR :: CP Server Thread-9 : Failed to access uri endpoint /status/sessions. Request timed out: HTTPConnectionPool(host='192.168.1.10', port=32400): Read timed out. (read timeout=15) 2023-12-30 22:35:40 - WARNING :: CP Server Thread-9 : Tautulli Pmsconnect :: Unable to parse XML for get_current_activity: 'NoneType' object has no attribute 'getElementsByTagName'. 2023-12-30 22:35:40 - WARNING :: CP Server Thread-9 : Unable to retrieve data for get_activity. 2023-12-30 22:35:44 - ERROR :: Thread-17 (run) : Failed to access uri endpoint /status/sessions. Request timed out: HTTPConnectionPool(host='192.168.1.10', port=32400): Read timed out. (read timeout=15) 2023-12-30 22:35:44 - WARNING :: Thread-17 (run) : Tautulli Pmsconnect :: Unable to parse XML for get_current_activity: 'NoneType' object has no attribute 'getElementsByTagName'. 2023-12-30 22:35:59 - ERROR :: Thread-17 (run) : Failed to access uri endpoint /status/sessions. Request timed out: HTTPConnectionPool(host='192.168.1.10', port=32400): Read timed out. (read timeout=15) 2023-12-30 22:35:59 - WARNING :: Thread-17 (run) : Tautulli Pmsconnect :: Unable to parse XML for get_current_activity: 'NoneType' object has no attribute 'getElementsByTagName'. {REPEATED} 2023-12-30 22:57:00 - ERROR :: CP Server Thread-7 : Failed to access uri endpoint /status/sessions. Request timed out: HTTPConnectionPool(host='192.168.1.10', port=32400): Read timed out. (read timeout=15) 2023-12-30 22:57:00 - WARNING :: CP Server Thread-7 : Tautulli Pmsconnect :: Unable to parse XML for get_current_activity: 'NoneType' object has no attribute 'getElementsByTagName'. 2023-12-30 22:57:00 - WARNING :: CP Server Thread-7 : Unable to retrieve data for get_activity. 2023-12-30 22:57:27 - WARNING :: CP Server Thread-11 : Failed to get image /library/metadata/281641/thumb, falling back to poster. 2023-12-30 22:57:27 - WARNING :: CP Server Thread-8 : Failed to get image /library/metadata/281635/thumb, falling back to poster. Now this looks like something that could bring my server down, doing some research it looks like I may need to adjust some settings in the container or on my firewall.
  9. I have not, I've been avoiding it. It's my Plex server and I'm addicted, LOL. All of the issues I had with the Web GUI partially loading have been resolved by deleting all of my plugins. The only issue that remains is it locking up at night around 3:15am.
  10. That directory does not appear to exist. I did look through the cron.d directory and found one file named root, and have attached a screenshot of its contents.
  11. Server locked up again, it seems to be happening every night/morning at 3:15am approximately. Syslog had no meaningful info around the crash/lock/freeze. 2023-12-29T21:52:48-08:00 Friday monitor: Stop running nchan processes 2023-12-29T23:18:52-08:00 Friday webGUI: Successful login user root from 192.168.1.203 2023-12-29T23:19:21-08:00 Friday monitor: Stop running nchan processes 2023-12-29T23:41:24-08:00 Friday monitor: Stop running nchan processes 2023-12-30T00:23:28-08:00 Friday monitor: Stop running nchan processes 2023-12-30T01:43:02-08:00 Friday monitor: Stop running nchan processes 2023-12-30T03:07:20-08:00 Friday webGUI: Successful login user root from 192.168.1.203 2023-12-30T03:08:05-08:00 Friday monitor: Stop running nchan processes 2023-12-30T03:16:27-08:00 Friday emhttpd: Starting services... I'm currently using a new flash drive, though considering the consistency in timing I don't think this is a hardware issue.
  12. I've prepared a new flash drive, hopefully it's not my RAM cause I don't have any spares on hand.
  13. Woke up again to my server completely frozen. Tried removing unraidsafemode from boot to look at my plugins but the WEB Gui would fail to load as it did in the screenshot above. Booted back into Safe Mode. Noticed these entries in the syslog before it went down. 2023-12-28T14:10:01-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || : 2023-12-28T15:07:00-08:00 Friday monitor: Stop running nchan processes 2023-12-28T15:07:01-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || : 2023-12-28T16:05:01-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || : 2023-12-28T17:03:01-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || : 2023-12-28T18:00:02-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || : 2023-12-28T18:58:01-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || : 2023-12-28T19:56:01-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || : 2023-12-28T20:54:01-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || : 2023-12-28T21:20:58-08:00 Friday webGUI: Successful login user root from 192.168.1.69 2023-12-28T21:21:35-08:00 Friday monitor: Stop running nchan processes 2023-12-28T21:28:08-08:00 Friday monitor: Stop running nchan processes 2023-12-28T21:43:01-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || : 2023-12-28T22:42:01-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || : 2023-12-28T23:41:01-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || : 2023-12-29T01:09:01-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || : 2023-12-29T02:07:01-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || : 2023-12-29T03:00:57-08:00 Friday crond[1866]: failed parsing crontab for user root: *"2,4,¶,8(90,12 1˛ $(date +%e -d -7days) -le w ]] && /usr/local/sbin/mdcmd check NOCORReCT &> /dev/null || :
  14. Set "Power Supply Idle Control" to Typical Current Idle, and also disabled C-States from the BIOS. I'm not concerned with the power consumption of my server and would prefer as much stability as possible with my Ryzen build. Will update this post tomorrow with status.
  15. I don't recall ever adjusting power control in the BIOS to mitigate issues with C-States. I'll work on addressing that issue, and will follow back up tomorrow.