dapiedude

Members
  • Posts

    12
  • Joined

  • Last visited

About dapiedude

  • Birthday February 1

dapiedude's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. This problem is happening again. It started while I was watching some TV. Now my console logs are just repeating the "Starting Plex Media Player" message after I restarted the container. Console messages below: ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 45-plex-claim: executing... [cont-init.d] 45-plex-claim: exited 0. [cont-init.d] 50-gid-video: executing... [cont-init.d] 50-gid-video: exited 0. [cont-init.d] 60-plex-update: executing... Docker is used for versioning skip update check [cont-init.d] 60-plex-update: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. Starting Plex Media Server. EDIT: It looks like the database is corrupt: Apr 13, 2021 19:44:58.310 [0x152f62038700] INFO - Plex Media Scanner v1.22.2.4282-a97b03fad - Docker Docker Container (LinuxServer.> Apr 13, 2021 19:44:58.310 [0x152f62038700] INFO - Linux version: 5.10.28-Unraid, language: en-US Apr 13, 2021 19:44:58.310 [0x152f62038700] INFO - Processor AMD Ryzen 5 2600 Six-Core Processor Apr 13, 2021 19:44:58.310 [0x152f62038700] INFO - /usr/lib/plexmediaserver/Plex Media Scanner --scan --refresh --section 2 --activi> Apr 13, 2021 19:44:58.315 [0x152f62527780] DEBUG - Opening 20 database sessions to library (com.plexapp.plugins.library), SQLite 3.> Apr 13, 2021 19:44:58.316 [0x152f62527780] INFO - SQLITE3:(nil), 283, recovered 5 frames from WAL file /config/Library/Application > Apr 13, 2021 19:44:58.316 [0x152f62527780] ERROR - SQLITE3:(nil), 11, database corruption at line 66053 of [bf8c1b2b7a] Apr 13, 2021 19:44:58.316 [0x152f62527780] ERROR - SQLITE3:(nil), 11, database disk image is malformed in "PRAGMA cache_size=2000" I'm PUMPED to have a direction to go! lol Any advice on the best way to fix this issue? I just saw the official Plex documentation on potentially fixing this issue but it's from 2019 and I'm not sure if that's still up to date.
  2. Hey all, I have been having a very odd problem and I cannot seem to find any solution to it. I have been running a plex container on UnRAId for nearly 2 years. I'm currently running the latest docker image in 6.9.2 but this issue has been happening since before 6.9.0. I have a P2000 that I use for HW transcoding and 32GB of RAM. -- Every once in a while (every 24 hours up to just once in 3 weeks), I will receive a message from Uptime Robot that my Plex server is unreachable. I will be unable to access my content and am met with a message explaining that it is unable to connect. None of my libraries will load and I cannot access the server's settings. After some amount of time (1-5 hours) Plex will be available again. Usually, I've restarted the container a few times but I'm not sure if the restart was effective because Plex will still be unavailable for a while after the restart. Occasionally, I'll restart UnRAID which usually seems to fix the problem right away. I can't remember if I've ever NOT restarted the Plex container. This problem happened this morning and I spent nearly an hour troubleshooting. After nearly 90 minutes, I was suddenly able to access Plex again. I wish that I could be more specific on what fixed it, but I had restarted the container and was typing up this post when it became accessible again. The only change I've made is changing the Network Type from Bridge to Host (back and forth a few times). I don't really understand what the network type is lol but it was working on Bridge for about a week, then I changed it to Host after it stopped working and now it's working again. Probably a correlation and not causal since the last time it stopped working I changed it from Host back to Bridge and it started working again after some time. This most recent time, I also changed my Appdata path from /mnt/user/appdata/plex to /mnt/cache/appdata/plex. Again, I don't think that this made any difference but if it did then awesome! -- While watching the Plex console logs, this is what I'll see for the entire time that the server is down: ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 45-plex-claim: executing... [cont-init.d] 45-plex-claim: exited 0. [cont-init.d] 50-gid-video: executing... [cont-init.d] 50-gid-video: exited 0. [cont-init.d] 60-plex-update: executing... Docker is used for versioning skip update check [cont-init.d] 60-plex-update: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done. If I restart the container, then this will be appended after the message above: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... usermod: no changes I was having the same problem, albeit at a much higher frequency (every day), with the Binhex-Plexpass container. While the issue is occurring, I am unable to access Plex from my local IP (192.168.x.x:32400) as the page never loads. However, I am still able to access the GUI via app.plex.tv That's where I encounter the error message that says my Plex is unavailable. I'm hoping to stop having issues where Plex becomes unavailable and any insight on what I've done wrong or ways to fix this issue is incredibly helpful! I've attached the server logs as well as my docker config info. There are a few unmapped paths (/movies, /tv, /music) which reappear after re-pulling the docker but all of my libraries are accessible. Plex Media Server Logs_2021-04-13_08-41-03.zip
  3. I'm having the same issue - I've been running the MineOS-node from hexparrot for about 6 months now. I just switched to binhex' (love your stuff man) and have started to encounter this issue, which was not a problem on hexparrot's.
  4. @HaveAGitGat - I am running the UnRAID Tdarr_aio docker and using the haveagitgat/tdarr_aio repo. How would I make sure that I get the 1.2068 beta? Is it a different repo?
  5. I hadn't filled up the 20G but I was at around 90% of that 20G and kept getting notifications that the docker.img was close to full. Honestly, it was more out of laziness in finding that notification and turning it off so I just upped it to 80G. Currently I'm using 23.4G with 30 dockers. I just checked the mappings for each of them and they all seemed correct. I've turned down the allocation to 30G though, that way I can watch for bloat! Is there a good way to see how much space each of my dockers are using within the docker.img? I have cadvisor but that isn't helpful when looking at the general docker allocations. Thanks for helping me with all of this and being so forward thinking too!
  6. Everything came back without issue. I checked all of my dockets and VMs and everything is running fine. I removed any of the Docker stuff that I could find that wasn't in my cash!
  7. Answered my own question! I remounted the NVMe drive, stopped the array, assigned the Cache drive to be the NVMe drive and now we're good to go! Thank you very much @trurl and @JorgeB for your help
  8. @trurl - I just reconnected the cache to the same M.2 port and now have my new diagnostics (attached). It is showing up as an unassigned drive right now. Is it possible to have it be the Cache drive again without formatting / wiping the contents? tower-diagnostics-20200902-1455.zip
  9. @trurl - I'll post new diagnostics when it's finished, about an hour or so left. Thanks!! @JorgeB - does this suggest that it dropped offline due to a hardware disconnect or is this a software drop? Also, would I be able to reconnect the dropped NVME from the Tower GUI, or is it something a reboot should fix, or simply a full shut-down then disconnect + reconnect of the NVME? Thanks a lot
  10. Hi all, I've been running UnRAID for about a year now. My current uptime is 25 days. Last night around 10pm MT (90 minutes after my parity check started) all of dockers suddenly stopped working. Here are all of the funky things going on in the server, which I am guessing is due to the Cache drive not being accessible (or something similar wrong with the Cache drive). -- I checked out Fix Common Problems and I have these two issues: Error Found: Unable to write to cache. Suggested Fix: Drive mounted read-only or completely full Error Found: Unable to write to Docker Image Suggested Fix: Docker Image either full or corrupted. -- On my dashboard, I see my Cache as available, SMART shows the healthy thumbs up, and the utilization is 44% [453GB / 1TB] (which is normal as I have Plex writing thumbnails to the Cache). So nothing wrong here. -- When clicking on my Cache drive and scrolling to the Self-Test section, I can download the SMART report (attached) but the SMART self-test history, error logs, short self-test, and extended self-test buttons are grayed out. The "Last SMART test result" shows "SPIN UP" with a note reading "Unavailable - disk must be spun up." After clicking it, it takes me back to the top of the page and nothing further seems to happen as the SPIN UP is still there. -- When I go into the web terminal and type ls /mnt I see /bin/ls: cannot access '/mnt/user': Input/output error /bin/ls: cannot access '/mnt/cache': Input/output error and my other disks are available like normal. -- In my settings --> Docker, I have just disabled the docker so the status is stopped. I see the following: Docker vDisk location: /mnt/user/system/docker/docker.img (orange triangle with a white exclamation mark) Path does not exist Default appdata storage location: /mnt/user/appdata/ (orange triangle with a white exclamation mark) Path does not exist When attempting to re-enable the docker, the docker-tab in the top bar pops back up but the message shows "Docker Service failed to start." -- When I click on the Shares tab at the top, I see the following: There are no exportable user shares There are no exportable disk shares -- When I click Main at the top and then view each of the individual array devices' contents, I see that all of my array disks still have their folders and data. However, the Cache disk shows 0 objects: 0 directories, 0 files -- The parity check is still running, it is about 92% done. It has currently found 0 errors. -- Other information The cache drive is a 1 TB M.2 NVME The file system type for the Cache drive is xfs -- I believe that that's just about everything I've looked at. I haven't done a server reboot since it is going through the parity check right now. I haven't deleted / recreated my docker image since the problem seems to be more related to the Cache drive (even though the docker problems are what tipped me off to it). I've attached the diagnostics as well as the SMART report for the cache drive. Thanks in advance for the help. I'm not really sure where to start with correcting this problem and any help / advice / pointers are appreciated! tower-diagnostics-20200902-1017.zip tower-smart-20200902-1033.zip
  11. For anyone on Google Domains using Google's Dynamic DNS and this DDclient, I've been able to this working using the following: daemon=600 syslog=yes pid=/var/run/ddclient/ddclient.pid ssl=yes protocol=dyndns2 use=web server=domains.google.com login=generated-login, password=generated-password my.domain.tld No need to have anything else uncommented. Should be simple enough
  12. I picked unraid for my server specifically because of how easy it is to add drives without needing to worry about how data is allocated! For 2020, I'd like to see some native usage reporting. For example, CPU usage per docker, how much RAM each APP is using. Similar to Grafana, but something native.