Later versions of Plex losing Movie Library

Plex Media Server
1

Server Version#: 1.26.0.5715-6000
Player Version#: 4.76.1

For the past month, I’ve tried to upgrade my Plex app on my Synology NAS (whenever ANOTHER new release came out). EACH time, I had to revert to the version above, because my “Movie” Library would show “A Problem Occurred.” When I uninstalled Plex, then reinstalled the version above, the Movie Library showed up, fully intact.

I’ve done these upgrade(s) for the past three+ new versions, and always had to revert back. Every reversion back to the version listed, brought the library back.

Has anyone else seen a problem like this?

My movie path: Media/Movies - 0-G/(Movie Title} (Release Date)
(Other sub-paths are “Movies - H-L”, “Movies - M-S”, “Movies - T”, “Movies U-Z”.)

I split up the movies, because Plex was having difficulties with the number of movies [3K+] in a single sub-directory.

Thanks in advance,

Dave

2

Dave,
This kind of error occurs when then the server doesn’t send data to the player fast enough.
The player doesn’t know really what’s happening so it gives a very non-descript error.

Your log files will tell us what’s happening.

Based on the number of files you’re putting in a library section, I suspect your database is becoming fragmented and the newer version of the player/web-browser probably isn’t as tolerant as it could be.

Can you get the DEBUG log files (ZIP file you download) – Settings - Server - Troubleshooting (left panel) - Download Logs — and attach that here please?

I’ll look at what’s happening. (timeout errors will show in the logs)

3

Thanks very much! I’ll work on it tonight. Honestly, I
GREATLY appreciate your help! I fragmented my file
directories to the level (5) that worked at the time.

I’ll send you the debug files when I can. (Thanks for the
path to do so.) I don’t have PREMIUM internet access.
That may have something to deal with, even though it’s
just me,…surfing the web.

4

https://
ChuckPa: Thanks VERY MUCH (Much Mahalo) for responding!

I’m a little disappointed that Plex might consider my collection a “lot.” I’m a little queasy about sending NAS info over this medium,
but appreciate your help!

There were indications of slow Internet (Movie content was blocked), but overall content eked through). What has thrown
me off, was that TV content got through…

Dave
Plex Media Server Logs_2022-07-10_21-26-57.zip (5.6 MB)

5

@dgroe1

Please turn VERBOSE logging off . It only makes the log file harder to follow.
(It gets THAT verbose! lol)

I’ve just started going through your logs and will post again here when complete (Busy day for me so far)

6

Chuck,

I appreciate any time you can spare! If it is difficult to go through the verbose log, I can re-install the new version, turn off verbosity, and generate a new log.

Dave

7

You should be able to just go into the settings and turn off verbose logging,

8

I found the problem.

The database is corrupted / damaged.

Jul 09, 2022 02:00:30.149 [0x7f6c202f8b38] DEBUG - Activity: registered new activity d66b590a-54d7-4891-9d68-5301acc84574 - "Butler tasks"
Jul 09, 2022 02:00:30.149 [0x7f6c202f8b38] DEBUG - [Database backup/com.plexapp.plugins.library.db] Activity: registered new activity ad05baba-00d9-47d9-93fc-311df036dabb - "Database"
Jul 09, 2022 02:00:30.652 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.652 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.652 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.652 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.652 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.652 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 67007 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.663 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Jul 09, 2022 02:00:30.686 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Jul 09, 2022 02:00:30.686 [0x7f6c202f8b38] ERROR - [Database backup/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]

I have the procedure here. Let me go get it.

9

Understood. Thanks for the assistance!

But, I’ve got the old (workable) version installed now, so to generate a less-verbose log that shows the error, I’ll have to load the new/current version, before I generate a new log.

Dave

10

If I may …

Changing version won’t work around the damaged database.
It must be repaired -or- a working backup copied into position.

How long has the server been operating this way?

Knowing when it started,

Open FileStation,
Navigate to PlexMediaServer/AppData/Plex Media Server/Plug-in Support/Databases

Look at the dates of backups available to use.

Do you find any which precede the start of the problem?

11

Chuck,

The only reason I mentioned going to the newer versions, was if we needed a less-verbose log that would represent the problem.

As to a backup to the database that precede the start of the problem:
The only time the problem (Movie Library is blank/errored) shows up, is when I install later version(s) of Plex. I understand the database is still corrupted. I’ll look into getting the database clean with the downrev version, then trying the upgrade again.

Thanks again!

Dave

12

I have the procedure at the ready.

Would you like me to post it here?

13

Please do!

14

Looking at the dates you have there for database backups

Pick one which you know predates when the problem occurred. That’s the one we’ll use.

The procedure from here is:

  1. Stop PMS

  2. COPY the database backup file you’ve selected to any other location you want.

  3. RENAME the copy to be com.plexapp.plugins.library.db

  4. COPY it back to the Databases directory and OVERWRITE the one which is there.

  5. DELETE com.plexapp.plugins.library.db-shm if it still exists (it should not)

  6. DELETE com.plexapp.plugins.library.db-wal if it sill exists (it should not)

  7. Start PMS.

  8. WAIT until the CPU is completely idle in the Syno health widget
    We’re waiting to give PMS time to update this older DB to be current with this version of PMS.

  9. When it’s idle again, Scan Files (so it can look for new/changed media files)

  10. When complete, you should have everything back as it was.

  11. As final cleanup, delete the copy you made in that other location before you forget it’s there :wink:

1 Like
15

@ChuckPa I keep getting an error on my Android App that the database on my server is corrupt.

Screenshot_20220718-095428
Screenshot_20220718-095428480×1041 67.8 KB

Running DSM 7.1-42661
PMS 1.25.8.5663-7000

I have tried the Optimize Database, but the error came back. I see no other notifications/errors in PMS.

Attached my logs:

Plex Media Server Logs_2022-07-18_10-05-07.zip (5.3 MB)

16

@tlef805 The database is corrupt.

Jul 18, 2022 06:14:11.311 [0x7fb67fbc3b38] ERROR - [DatabaseFixups] SQLITE3:0x80000001, 267, statement aborts at 163: [update metadata_items set extra_data=? where metadata_type=? and library_section_id=? and id=?] database disk image is malformed
Jul 18, 2022 06:14:11.312 [0x7fb67fbc3b38] ERROR - [DatabaseFixups] Exception inside transaction (inside=1) (/data/jenkins/server/3540783331/Library/MetadataCollection.cpp:479): sqlite3_statement_backend::loadOne: database disk image is malformed
Jul 18, 2022 06:14:11.312 [0x7fb67fbc3b38] ERROR - [DatabaseFixups] Fixup 29DatabaseFixupsSyncCollections threw an exception: sqlite3_statement_backend::loadOne: database disk image is malformed

You have three options:

  1. Repair.
  2. Restore from a backup.
  3. Delete and start over.

The database is located in /PlexMediaServer/AppData/Plex Media Server/Plug-in Support/Databases (Where is the Plex Media Server data directory located?).

Repair a Corrupted Database has instructions on how to repair the database.

If the repair is unsuccessful, you can try restoring from a backup. Choose a backup from before the problem started, otherwise it may also be corrupt. You can use the procedures in the repair article to check for corruption and attempt repair if needed. See Restore a Database Backed Up via ‘Scheduled Tasks’ and Synology FAQ #17: Recover from a corrupt database for details.

If repair or restoration does not work, then you can delete the database. You will have to re-create your libraries. Your media is not touched. See the Repair article for additional info.

1 Like
17

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