Server Version#: 1.32.7.7571
Never seen anything above 100% before - glitch or feature? Synology 1019+ (4 core apollolake)
Can’t really tell anything without the server DEBUG logs ZIP file please.
Given it’s a Quad Core 400% CPU (4x 100%) is how Linux would report it.
This graph shows about 1 full core … which can easily be audio + tone mapping handling + remuxing and a spike because filling the player’s buffer (which will run at ‘full speed’ if it can)
This is why logs are important.
Sorry, no logs and it only happened once. It routinely pegs and holds 100% both in synology DSM and plex. It’s never shown above 100 let alone hundreds. They have always matched.
perhaps it was doing instant-analysis for playback (on-demand analysis occurs for newly added media not yet scanned during maintenance)
Yes it was while I was adding media
So knowing the Synology meter 100% means all cpu use, and that percentage, matches the graph in Plex, is above 100% a glitch would you say?
What the heck kind of Syno XPE box is that. They do not have any 52+ core machines.
Now I need logs.
where would you like it sent
It’s filled with all kinds of errors
Sep 30, 2023 11:35:40.308 [140191257033528] WARN - [Req#2ad14] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Sep 30, 2023 11:35:40.308 [140191257033528] WARN - [Req#2ad14] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Sep 30, 2023 11:35:44.232 [140191257033528] WARN - [Req#2ada3] QueryParser: Invalid field ‘libraryHubsOnly’ found, ignoring.
Sep 30, 2023 11:35:44.535 [140191330421560] WARN - [Req#2adab] QueryParser: Invalid field ‘libraryHubsOnly’ found, ignoring.
Sep 30, 2023 11:38:41.512 [140191330421560] WARN - [Req#2b262] QueryParser: Invalid field ‘libraryHubsOnly’ found, ignoring.
Sep 30, 2023 11:38:41.827 [140191300193080] WARN - [Req#2b24c] QueryParser: Invalid field ‘libraryHubsOnly’ found, ignoring.
Sep 30, 2023 11:45:53.349 [140191233768248] ERROR - [CreditsDetectionManager] BufferingLineReader: failed to read line (error: -1)
Sep 30, 2023 11:45:53.469 [140191233768248] WARN - [CreditsDetectionManager] Held transaction for too long (/data/jenkins/server/3536195808/Library/Scanner/CreditsDetector/CreditsDetectorManager.cpp:278): 0.160000 seconds
Sep 30, 2023 12:04:45.291 [140191330421560] WARN - [Req#2e363] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Btw all the strange behavior just started when I turned on credits detection. I’ve had it disabled from its release. Thought it would be cool to try.
See the server logs article on how to grab the logs and then just upload the zip to this thread.
I know how to get them. I’m not going to put them here for anyone to pull.
Check PM
Thanks again to Chuck for the quick help fixing the db via his repair tool script, which was in bad shape! All good now 
Is it running better for you now?
(The most obvious improvement should be when searching)
Even with the db mess, it was always operating just fine - it’s just as fast as it’s always been If I didn’t see that graph mistake I never would have known there was an issue lol
I’m keeping my eye on that one.
I don’t know how the math can fail. There aren’t 53+ cores running an a Synology.
I bought 15 of them, duct taped together
ROTFLMFAO
