Server Version#: 1.14.5488
Player Version#: web/iPhone/AppleTV/PS4, does not matter
Have been running PMS on my debian sever for some time, but started to notice general sluggishness and crashes recently. Tried upgrading from 1.13 to 1.14, but no difference. Tried to optimize the library, but no difference. Clean bundles, no difference. Manually remove the
$PLEX_HOME/Library/Application Support/Plex Media Server/Plug-in Support/Caches, no difference.
The server usually allows me to log in and browse, but refuses to play anything.
Restarting the service sometime takes forever and requires service plexmediaserver force-stop.
It installed without complaints about any dependency, so I don’t see what could be incompatible. This started before I tried to upgrade PMS and has been working for quite some time before that.
Oh! It’s a raid 6 array, but I do have had several drives fail on me the last year (all installed at the same time so along with the Debian 6 they might be on the tail end of their lifespan). I did originally have the PMS database on the boot disk (SSD), but it outgrew it. Database is around 80 GB at the moment, which is unresonable by itself).
Perhaps take it down, run a e2fsck -f on the file system and force out any bad drive which might pop up?
Perhaps I should re-phase my question. PMS has been running fine up until now, which means responsive, working, could search, play music and so on. My 10 year old CPU had no problem in coping with streaming Full HD video to several clients, but now I can’t even listen to 128 kbps MP3. The CPU is not the issue here.
I did consider something similar but ended up using ExportTools plugin to count number of songs and movies. I’ll link to the thread here. Anyhow, find and wc -l revealed the following:
music 37815
movies 15479
TV 18091
e2fsck -f is running overnight. EDIT: Took a few minutes. No complaints.
Your actual database is 194.8 MB. Your total metadata, including all the chapter images, might indeed be 80GB. The part which matters most with respects to this issue is the physical DB (194 MB)
This is where I think Debian 6 is your root evil. Debian 6 support was offered by one of the Plex Ninjas, as a gift to the community, with permission from Plex. He has since moved on. There is no support for Debian 6. There is no support for Debian 7. Official support for Debian begins at 8 when it migrated from being init based to systemd based.
Feb 04, 2019 09:20:31.035 [0x7fe18d3ff700] WARN - Waited one whole second for a busy database.
Feb 04, 2019 09:20:31.166 [0x7fe1927fc700] WARN - Waited one whole second for a busy database.
Feb 04, 2019 09:20:32.047 [0x7fe18d3ff700] ERROR - Failed to begin transaction (../Library/MetadataCollection.cpp:173) (tries=3): Cannot begin transaction. database is locked
Feb 04, 2019 09:20:32.189 [0x7fe174bf5700] WARN - Waited one whole second for a busy database.
Feb 04, 2019 09:20:33.369 [0x7fe18d3ff700] WARN - Waited one whole second for a busy database.
Feb 04, 2019 09:20:33.409 [0x7fe1927fc700] WARN - Waited one whole second for a busy database.
Feb 04, 2019 09:20:34.386 [0x7fe18d3ff700] ERROR - Failed to begin transaction (../Library/MetadataCollection.cpp:173) (tries=4): Cannot begin transaction. database is locked
Feb 04, 2019 09:20:34.433 [0x7fe174bf5700] WARN - Waited one whole second for a busy database.
the flock() runtime library call behaves differently in different versions of Linux because of the version of the GNU C library (glibc) packaged with them.
PMS must minimally have glibc 2.17 to operate.
I cannot tell what version you have. The online resources end here.
dpkg-query -l | grep gcc
ii gcc 4:4.9.2-2 amd64 GNU C compiler
ii gcc-4.8 4.8.4-1 amd64 GNU C compiler
ii gcc-4.8-base:amd64 4.8.4-1 amd64 GCC, the GNU Compiler Collection (base package)
ii gcc-4.9 4.9.2-10+deb8u1 amd64 GNU C compiler
ii gcc-4.9-base:amd64 4.9.2-10+deb8u1 amd64 GCC, the GNU Compiler Collection (base package)
ii lib32gcc1 1:4.9.2-10+deb8u1 amd64 GCC support library (32 bit Version)
ii libgcc-4.8-dev:amd64 4.8.4-1 amd64 GCC support library (development files)
ii libgcc-4.9-dev:amd64 4.9.2-10+deb8u1 amd64 GCC support library (development files)
ii libgcc1:amd64 1:4.9.2-10+deb8u1 amd64 GCC support library
ii linux-compiler-gcc-4.8-x86 3.16.43-2+deb8u5 amd64 Compiler for Linux on x86 (meta-package)
I will attempt to cross match that gcc version to glibc
This will take a while
To shortcut, check your actual files
-rwxr-xr-x. 1 root root 1901676 Aug 29 06:17 /lib/libc-2.26.so*
you want libc
I am also very concerned about this: Mixing 4.8 and 4.9 GCC… which apparently comes from Debian 8?
ii lib32gcc1 1:4.9.2-10+deb8u1 amd64 GCC support library (32 bit Version)
ii libgcc-4.8-dev:amd64 4.8.4-1 amd64 GCC support library (development files)
ii libgcc-4.9-dev:amd64 4.9.2-10+deb8u1 amd64 GCC support library (development files)
ii libgcc1:amd64 1:4.9.2-10+deb8u1 amd64 GCC support library
