HynesJeff

looks like it might be this: https://forums.plex.tv/t/library-db-size-more-than-doubled-in-latest-version/918851 EDIT: fixed after following this post: https://forums.plex.tv/t/library-db-size-more-than-doubled-in-latest-version/918851/64 the steps I took were to shut down plex, make a backup of the db. then follow the steps to connect to the sql database and run delete from statistics_bandwidth where account_id is NULL; this took HOURS... and then I ran this, which shrunk the size back down to ~300MB after the deletions (much faster): VACUUM;

looks like my db file com.plexapp.plugins.library.db went from ~300MB to over 20GB! between May 15 and 18... what? I didn't do anything.

Thanks for the reply! So its freezing again. not a lot of reads on my SSD but there are some. Other apps are running fine off it. Not much CPU activity either. What else is interesting is I could actually connect to the local ip:port but it said the backend was down .... so it wouldn't load any media. but the webui was up :D now the webui hangs as well. Does look like there was a job "optimizing databases" that seemed to have been running before i could reconnect. There's no array activity so its not accessing any of my media. EDIT: Yes looks like its thed database optimization that is being very slow... From the plex logs: May 22, 2025 10:00:50.674 [23294701501240] WARN - [Database optimization/com.plexapp.plugins.library.db/DatabaseFixups] Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/DatabaseFixups.cpp:234): 0.170000 seconds May 22, 2025 10:00:50.873 [23294701501240] WARN - [Database optimization/com.plexapp.plugins.library.db/DatabaseFixups] Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/DatabaseFixups.cpp:402): 0.130000 seconds May 22, 2025 10:00:52.172 [23294701501240] WARN - [Database optimization/com.plexapp.plugins.library.db] Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/FullTextSearch.cpp:58): 1.290000 seconds May 22, 2025 10:00:53.211 [23294701501240] WARN - [Database optimization/com.plexapp.plugins.library.db] Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/FullTextSearch.cpp:71): 0.770000 seconds May 22, 2025 10:00:55.879 [23294701501240] WARN - [Database optimization/com.plexapp.plugins.library.db] Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/FullTextSearch.cpp:81): 2.560000 seconds May 22, 2025 10:00:58.782 [23294701501240] WARN - [Database optimization/com.plexapp.plugins.library.db] Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/FullTextSearch.cpp:94): 2.710000 seconds May 22, 2025 10:25:59.627 [23294880897848] WARN - JobManager: Could not find job for handle 398

Started getting this today: Critical: libusb_init failed And the container seems to continue running but accessing the plex host:port spins forever.... A restart of the container fixes it but it has happened twice now. EDIT: Nevermind, the log line above it literally says that it can be ignored... lol, so that's a red herring i guess... Not sure why plex is hanging then all of a sudden

worked, ty!

For some reason I can't seem to update the plugin to the latest version. I still have the older version (2025.02.08), and when i go to the plugins page it says not available next to just this one. In community applications, it shows it installed.

I'm not sure who else is having this problem, but the container wont start up on a second run. A workaround is to remove and re-run the container. Using the User Scripts plugin, you can create a custom script to fix it and just re-run the script any time it breaks: #!/bin/bash # Ensure image is up to date docker pull zurdi15/romm # Remove container (expected to fail if container is running) docker container rm RomM # Re-create docker container docker run \ -d \ --name='RomM' \ --net='{DOCKER_NETWORK}' \ -e TZ="{TIMEZONE}" \ -e HOST_OS="Unraid" \ -e HOST_HOSTNAME="{HOSTNAME}" \ -e HOST_CONTAINERNAME="RomM" \ -e 'IGDB_CLIENT_ID'='{CLIENT_ID}' \ -e 'IGDB_CLIENT_SECRET'='{CLIENT_SECRET}' \ -e 'PGID'='100' \ -e 'PUID'='99' \ -l net.unraid.docker.managed=dockerman \ -l net.unraid.docker.webui='http://[IP]:[PORT:8080]' \ -l net.unraid.docker.icon='https://github.com/Eurotimmy/unraid-templates/blob/main/RomM/RomM.png?raw=1' \ -p '8091:8080/tcp' \ -v '/mnt/cache/appdata/romm/config.yml':'/romm/config.yml':'rw' \ -v '/mnt/user/roms':'/romm/library':'rw' \ -v '/mnt/cache/appdata/romm/resources':'/romm/resources':'rw' \ -v '/mnt/cache/appdata/romm/logs':'/romm/logs':'rw' \ -v '/mnt/cache/appdata/romm/database':'/romm/database':'rw' \ 'zurdi15/romm' All values with curly braces need to be updated to your own configuration, and modify whatever else you need. The volume mapping configs for instance is what I use, but yours might look different. I have it set to run at array startup.

Getting this error and then the container crashes: WARNING: [RomM][2023-12-23 03:21:19] Twitch token invalid: fetching a new one... happens randomly and often, sometimes i can't recover and need to start over.

Thanks, I fixed it by moving it to /var/log/nextcloud and mapping that to another dir inside .../appdata/nexcloud However, now it looks like that data directory contains another file that is being opened; /data/files_external/rootcerts.crt and I can't figure out how to move this. For this i raised a bug: https://github.com/linuxserver/docker-nextcloud/issues/309

looks like nextcloud.log may be causing it... why is this written to the array and not appdata

One of my drives keeps spinning up and i cant tell what is causing it. Any advice?

this does not work for me, i've been stuck on what looks like a version from 2 years ago: 2.1.496 I tried clicking update now, and going to updates and clicking install. Still on the same version EDIT: Started over from scratch by running 2 containers side-by-side and re-configuring new one by copying old settings.... Works now.

decided to reformat to xfs - encrypted, and move docker to Directory. Everything seems to be working fine now.

a lot my files on my cache drive appear to be corrupted... any way to fix taht or is it a loss at this point? (I have appdata backups on the array fortunately but they are a few days old) EDIT: it appears a server reboot fixed the input/output errors while copying.

I guess I will take this as the opportunity to move to encrypted cache drive. Should i keep btrfs, or move to xfs?

thanks @JorgeB Here's the diag: mothership-diagnostics-20230416-1133.zip

This just started to happen all of a sudden. I cant start docker or create any files on the FS. The mover wont move anything off it.... Any help is appreciated Btw the drive didn't fill up, smart checks all pass. I don't see any hardware problems. Its been happening randomly recently but a restart usually fixed it. This time it does not seem to be working.

how do i continue from a crashed/unfinished move ? I tried moving all my data off a disk to encrypt it, and 3/4 of the wya through, the plugin somehow died, had ti disable and re-enable. now most of the data exists on both disks - how do i remove the duplicates and continue where it left off? EDIT: Trying to re-run tells me there's not enough space on target disk, so i found that choosing a few subdirs at a time was slow, but worked.

for some reason there is no way for me to see the show log or download the log for the user scripts when i run in the background: going to the path in the terminal, can see it: /tmp/user.scripts/tmpScripts/ ... /log.txt Any ideas? Another issue is my drive is only going 5MB/s writes.... seems very slow

this doesn't seem to work for me - any ideas? UI still says "The library pdlib is not available."

been getting this error: NO LOG FILE! - [] Failed to up file descriptor limit Operation not permitted NO LOG FILE! - [] setting up server logging... [2022-01-22 12:18:20:702 INFO] Starting Server [2022-01-22 12:18:20:702 INFO] Version 1.18.2.03 [2022-01-22 12:18:20:702 INFO] Session ID 1afaab32-b2fe-4518-9117-b7bee205e37d [2022-01-22 12:18:20:702 INFO] Level Name: Family Server [2022-01-22 12:18:20:703 INFO] Game mode: 0 Survival [2022-01-22 12:18:20:703 INFO] Difficulty: 1 EASY [2022-01-22 12:18:21:823 INFO] opening worlds/Family Server/db [2022-01-22 12:18:21:823 ERROR] DBStorage chain is invalid. Possibly encryption-related, or bad DBStorageConfig passed. Reason: Unable to decipher/decrypt LevelDB. [2022-01-22 12:18:21:834 ERROR] Network port occupied, can't start server. Edit: NVM... looks like a corrupt world

my appdata is set to cache only but i just confirmed there are no appdata directories on any of my array drives, only on my ssd cache drive. What do you mean by "top tabs"? Are you referring to the unraid UI?

its been almost a year but I finally found the root cause to this (Been dealing with random crashes since) All my docker containers used /mnt/user/appdata - i have a lot of containers, and plex being one of them Changing them all to /mnt/cache/appdata not only hugely improved the performance of unraid and my docker containers (and plex from locking up/crashing), but it stopped unraid from crashing!!!! So in conclusion, unraid was crashing unraid. Nothing hardware related at all. And for anyone that is skeptical: # time find /mnt/user/appdata | wc -l 458909 real 0m33.611s user 0m0.842s sys 0m7.161s vs # time find /mnt/cache/appdata | wc -l 458910 real 0m0.770s user 0m0.178s sys 0m0.635s 33.6 seconds vs 0.77 seconds... the difference is HUGE

its been almost a year but I finally found the root cause to this (Been dealing with random crashes since) All my docker containers used /mnt/user/appdata - i have a lot of containers, and plex being one of them Changing them all to /mnt/cache/appdata not only hugely improved the performance of unraid and my docker containers (and plex from locking up/crashing), but it stopped unraid from crashing!!!! So in conclusion, unraid was crashing unraid. Nothing hardware related at all. I suspect the speed of my SSD (sabrent rocket 4.0), the number of files i have in appdata, my plex directory, and sheer size of my media library overloaded it somehow.

No, but its only crashed now once since I made the bios change, in the ~2 weeks since ive made it. It made a huge difference.