# Bizarre Server Error I cannot fathome **URL:** \ **Category:** Plex Media Server\ **Tags:** metadata\ **Created:** [January 13, 2024, 12:52pm UTC](https://forums.plex.tv/t/bizarre-server-error-i-cannot-fathome/866123 "2024-01-13T12:52:03Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Rivers](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/rivers/32/349352_2.png) [@Rivers](https://forums.plex.tv/u/Rivers)\ **Post date:** [January 13, 2024, 12:52pm UTC](https://forums.plex.tv/t/bizarre-server-error-i-cannot-fathome/866123/1 "2024-01-13T12:52:03Z")
Server Version#: 1.32.8.7639 Player Version#: ATV 8.29 (7486) Log: I will have to upload logs later on due to having verbose logging enabled. OS: MacOS 13.6.3 Machine: Mac Mini Server 2012 2.3ghz Quad Event: Last week I was trying to watch a movie with my girlfriend on watch together, we got about five minutes into the movie before it crashed and became non responsive and went down. Observations: I remotely accessed the server and noticed that the CPU was grinding inbetween 650 and 750% approx. Instead of the remained there for quite some time, even though there was no transcoding scheduled tasks or any kind of activity going on. My first reaction was to shut down the Plex instance, which is what I did. After this, I tried again to play the same movie, and the same issue reoccurred. After this, I tried a viewing the details page and playing a whole host of different movies and tv shows to try and ascertain if this issue was widespread, it wasn’t. I also noticed just viewing the movie detail page or going into the collections would trigger the CPU usage event. There seems to be no issues playing media from any of the other libraries, eventually came to the conclusion that this issue was only affecting the films library, and after that I came to the conclusion it was only affecting a particular subset of films that had been recently added. Strange thing is all the new movies that were added after this batch of movies worked fine. Your first thought might be, It’s the encoding of particular movies, it’s not. So then I looked in the console and noticed a few yellow and red warnings, one red warning stated something about invalid meta data, or something to that effect. So I manually tried every single movie and found the range of movies which weren’t working, and I removed them from the library, cleaned the bundles and optimise the database, and then re-added a 3 back one at a time and tested inbetween. At first, it looked like it worked for the couple Of these test titles I added, so I added back the whole batch and then the issue resurfaced. At this point to rule out it was anything to do with the movie files themselves, I created a test library and pointed it directly to the folder where those batch of movies were, and everything worked like normal. The next thing I tried, was logging into a new user, starting a fresh Plex installation changed a few initial settings, shut down that instance, and then copied over the two main databases minus the metadata to see the database structure. Everything loaded minus the artwork, and when I tried to view the details page of those particular movies, the exact same thing happened on a fresh user with no meta data tied to it before I even attempted to play the movie. So at this point, I came to the conclusion, it’s definitely a database issue. So after this I placed a .plexignore file in the folder to remove the offending movies and combed through the logs, got nowhere and then just moved on because I haven’t had the time nor the patience to figure it out. I’ve never really had any major issues with Plex during the 12 years that I’ve been running a server, so I am not really that experienced with deciphering console logs and relating output to a particular issue let alone knowing how to fix them. So I was hoping some more experienced users here might know what the issue might be and how to help. ---
**Author:** ![joeboydotnet](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/joeboydotnet/32/315891_2.png) [@joeboydotnet](https://forums.plex.tv/u/joeboydotnet)\ **Post date:** [January 13, 2024, 3:25pm UTC](https://forums.plex.tv/t/bizarre-server-error-i-cannot-fathome/866123/2 "2024-01-13T15:25:30Z")
Can you share the error in log? ---
**Author:** ![Rivers](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/rivers/32/349352_2.png) [@Rivers](https://forums.plex.tv/u/Rivers)\ **Post date:** [January 13, 2024, 5:11pm UTC](https://forums.plex.tv/t/bizarre-server-error-i-cannot-fathome/866123/3 "2024-01-13T17:11:40Z")
I’m not sure how long I have to wait after turning verbose logging off before I can share the logs. Plus, I’m probably gonna have to re-create the issue to capture the problem in the logs ---
**Author:** ![Rivers](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/rivers/32/349352_2.png) [@Rivers](https://forums.plex.tv/u/Rivers)\ **Post date:** [January 13, 2024, 5:18pm UTC](https://forums.plex.tv/t/bizarre-server-error-i-cannot-fathome/866123/4 "2024-01-13T17:18:24Z")
I just managed to catch the error that I think I saw before in a quick screen. ![Image](https://global.discourse-cdn.com/plex/original/4X/d/f/e/dfec288f77838fc8c9623c4b98d59b19ef93997e.jpeg) I’ll share the full logs later on. ---
**Author:** ![joeboydotnet](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/joeboydotnet/32/315891_2.png) [@joeboydotnet](https://forums.plex.tv/u/joeboydotnet)\ **Post date:** [January 14, 2024, 7:01pm UTC](https://forums.plex.tv/t/bizarre-server-error-i-cannot-fathome/866123/5 "2024-01-14T19:01:16Z")
Sounds like the DB has just got its panties in a wad. Id start with an intergrity check on the database i guess, maybe force a index rebuild if that finds nothing of interest. Google “Plex SQLite PRAGMA integrity\_check” for instructions on how to check Google “Plex SQLite Re-index” for instuctions on how to attmept a repair ---
**Author:** ![tom80H](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/tom80h/32/19753_2.png) [@tom80H](https://forums.plex.tv/u/tom80H)\ **Post date:** [January 14, 2024, 8:21pm UTC](https://forums.plex.tv/t/bizarre-server-error-i-cannot-fathome/866123/6 "2024-01-14T20:21:41Z")
_ **IF** _ the logs show the database is corrupted, go by the official guide on how to repair it. [https://support.plex.tv/articles/repair-a-corrupted-database/](https://support.plex.tv/articles/repair-a-corrupted-database/) That being said… basic playback issues don’t necessarily indicate there’s a problem with the database. # The logs about `Unknown metadata type: folder` are just infos and can be ignored; that’s not impacting anything (has been discussed in the forum several times). ---
**Author:** ![shark2k](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/shark2k/32/305908_2.png) [@shark2k](https://forums.plex.tv/u/shark2k)\ **Post date:** [January 14, 2024, 8:55pm UTC](https://forums.plex.tv/t/bizarre-server-error-i-cannot-fathome/866123/7 "2024-01-14T20:55:51Z")
You can try @ChuckPa’s DB utility to make sure you DB is working well . > [@PlexDBRepair development](https://forums.plex.tv/t/plexdbrepair-development/822684): > > Any chance you could make it support binhex-plexpass docker? My library db is 1.4gb and my blobs one is 4.09 gb. #\_# I may need helps lol… I asked cause I got this error below when attempting to execute it inside my docker container for binhex Error: Unknown host. Currently supported hosts are: QNAP, Synology, Netgear, Mac, ASUSTOR, WD (OS5) and Linux Workstation/Server GitHub where you can download the release: [GitHub - ChuckPa/PlexDBRepair: Database repair utility for Plex Media Server databases](https://github.com/ChuckPa/PlexDBRepair) -Shark2k ---
**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\ **Post date:** [April 13, 2024, 8:56pm UTC](https://forums.plex.tv/t/bizarre-server-error-i-cannot-fathome/866123/8 "2024-04-13T20:56:18Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.