Problem loading Library content: Something went wrong An unexpected error occurred

Hello,

Server Version#: 1.41.6.9606

I have a problem for a few weeks.
I have a server installed remotely on a linuxserver (seedbox).
For a few weeks I started having a problem with Series Libraries.
I have two Libraries with series, and the content is not listed in both. Sometimes it works fine, sometimes not at all. It loads and loads and finally I get an error: Something went wrong An unexpected error occurred.
This is not the case with Libraries with Movies, only with Series.

I have already tried the following things:
1.Celan Bundles
2.Database Optimization
3.I have rebuilt and re-indexed the database according to a plex’s article. (repair-a-corrupted-database)
4.I restarted Rclone (I use the same mount together with a friend who also has a PMS on this server and everything works fine for him)
5.I rescanned and refreshed all the metadata for this library.

I just don’t know what to do. My friends who have access to this Library, tell me that even their Library doesn’t load with series very often. No matter what kind of device and Plex player…

Does anyone have any ideas? what the problem could be?

Thank you.

Can you grab (download) the PMS SERVER logs and attach its ZIP file here?

It’ll let me see where you’re having a problem

Ohh, sorry I forgot the logs file earlier.

Plex Media Server Logs_2025-04-03_03-17-12.zip (3.5 MB)

Can you help me with some advice, please? :folded_hands:

anyone who can help me? :smiling_face_with_tear:

Sorry I didn’t see this until now. (wasn’t notified)

There is some very serious database contention causing the whole thing to go into ‘timeout’ status (“something went wrong”)

Apr 02, 2025 12:52:58.977 [128584066804536] WARN - Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/MetadataItem.cpp:3933): 0.200000 seconds
Apr 02, 2025 12:53:00.687 [128584274422584] ERROR - Waited over 10 seconds for a busy database; giving up.
Apr 02, 2025 12:53:00.741 [128584291199800] ERROR - Waited over 10 seconds for a busy database; giving up.
Apr 02, 2025 12:53:00.741 [128584328948536] ERROR - Waited over 10 seconds for a busy database; giving up.
Apr 02, 2025 12:53:00.773 [128584257645368] ERROR - Waited over 10 seconds for a busy database; giving up.
Apr 02, 2025 12:53:01.619 [128584066804536] WARN - Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/MetadataItem.cpp:3933): 0.110000 seconds
Apr 02, 2025 12:53:01.624 [128584190536504] ERROR - [Req#167a1b] Unable to find client profile for device; platform=Tizen, platformVersion=5, device=19_MUSEL_UHD_BASIC, model=UE55RU7099UXZG
Apr 02, 2025 12:53:03.546 [128584270228280] ERROR - Waited over 10 seconds for a busy database; giving up.
Apr 02, 2025 12:53:06.622 [128584066804536] WARN - Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/MetadataItem.cpp:3933): 0.140000 seconds
Apr 02, 2025 12:53:06.622 [128584249256760] WARN - [Req#167a21] Took too long (0.140000 seconds) to start a transaction on /home/runner/_work/plex-media-server/plex-media-server/Library/MetadataItemSetting.cpp:467
Apr 02, 2025 12:53:06.622 [128584249256760] WARN - [Req#167a21] Transaction that was running was started on thread 128584066804536 at /home/runner/_work/plex-media-server/plex-media-server/Library/MetadataItem.cpp:1111
Apr 02, 2025 12:53:06.625 [128584249256760] ERROR - [Req#167a21] Unable to find client profile for device; platform=Tizen, platformVersion=6.5, device=22_PONTUSML_QTV, model=GQ65QN85BATXZG
Apr 02, 2025 12:53:09.409 [128584066804536] WARN - Held transaction for too long (/home/runner/_work/plex-media-server/plex-media-server/Library/MetadataItem.cpp:3933): 0.110000 seconds
Apr 02, 2025 12:53:10.905 [128584274422584] ERROR - Waited over 10 seconds for a busy database; giving up.
Apr 02, 2025 12:53:10.952 [128584291199800] ERROR - Waited over 10 seconds for a busy database; giving up.
Apr 02, 2025 12:53:12.350 [128584234576696] ERROR - [Req#167a49] Unable to find client profile for device; platform=Tizen, platformVersion=5, device=19_MUSEL_UHD_BASIC, model=UE55RU7099UXZG
Apr 02, 2025 12:53:14.186 [128584328948536] ERROR - Waited over 10 seconds for a busy database; giving up.
Apr 02, 2025 12:53:16.657 [128584190536504] WARN - [Req#167a28/Transcode] Got a transcode session ping without a valid session ID.
Apr 02, 2025 12:53:16.675 [128584257645368] ERROR - Waited over 10 seconds for a busy database; giving up.
Apr 02, 2025 12:53:17.479 [128584066804536] WARN - Held transaction for too long (/home/runner/_work/plex-media-serv

You have DEBUG logging turned off so it’s really difficult but the amount of ‘Busy Database’ errors are what’s killing it.

The DB is in serious need of cleanup / optimizing (beyond what PMS can do)

Read this, Take your time understanding how to use it with Docker, then run an “Auto” optimization on the DB

Let’s see what happens next.

Hello ChuckPa,

Thanks for your answer.

Unfortunately I’m not that good at scripts and linux servers.
I rent a seedbox only on a host where the PLEX application can be installed.
The administrator, the support from this server wrote to me that he already optimized the database and reindexed it and doesn’t think the problem comes from the database.

Do you think or have you noticed problems with the database that with that script could solve the problem with the database if it fixes it?

For a few hours I turned on the Debug option in the logs. Maybe you can see more information that way what could cause the problem?

Thanks for the help

@mozizz_online

The tool (script) corrects a lot of performance problems because it works on the DB with PMS shut down. (things PMS can’t do while the DB is active).

It optimizes the DB by completely exporting it as ascii and then rebuilding it in perfect compacted and sorted order with fresh search / lookup indexes.

When I looked at your logs, the “Busy DB” failures are common indicators of:

  1. Large, fragmented, database files
    -or-
  2. PMS on an iscsi drive
    -or-
  3. API hits constantly querying the DB to the point of CPU saturation.
    -or-
  4. A CPU grossly overloaded by software transcoding

Which applies?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.