Movie menu acting strangely

Today Plex stopped displaying my movie collection correctly. I was trying to view my movie library on the Samsung Tizen Plex app and got a blank screen. Just the menu at the top of the screen.

Tried the same with Plex Media Player on my mac mini and got the same result.

When I then tried to view all movies on the plex web app only a small number of the total movies show up. If I switch the display to recently added or recently released all the movies seem to show up, however they are really slow to display. Movies still show up on the home screen.

All the movies are still in their folder on the server as always and all displayed fine just yesterday. All tv shows and music seem to be displaying as normal.

Network issue? Plex Server machine issue? Have you tried rebooting the Plex Server computer?

I’ve tried restarting the plex server and I’ve rebooted the mac mini that is my Plex server.

I’ve attached a screenshot of the movie menu. There should be more movies displayed above these but I get a bunch of blank space.

The same kind of thing will happen further down where the movies will stop displaying when the titles get in the H’s. Also when scrolling through it seems like its struggling. Again this doesn’t happen with any other menus (tv shows, music, etc.) which have their files stored on the same drive.

Did you try optimising the database?

Just did. I get the message “There was a problem optimizing the database.”

Perhaps if I delete the library and recreate it?

@deanruffolo said:
Just did. I get the message “There was a problem optimizing the database.”

Perhaps if I delete the library and recreate it?

No, there’s a database problem going on. Need to check that out first.

Stop the Plex Server, wait one minute, restart it, wait two minutes, do an optimization, after it finishes and you get the error, download the logs and post them so we can see what’s going on.

Tried to stop the server and restart as suggested. Twice. Still getting the database error.

Attaching the logs as requested.

Not sure what you mean by “tried to stop and restart as suggested, twice.” Were you unable to close the Plex Server application and then start it again?

Well, your database is definitely corrupted.

Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Database optimization: Optimizing database. Starting by capturing all sessions. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 0. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 1. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 2. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 3. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 4. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 5. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 6. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 7. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 8. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 9. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 10. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 11. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 12. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 13. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 14. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 15. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 16. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 17. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 18. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Captured session 19. Jan 08, 2017 15:34:04.853 [0x700004110000] DEBUG - Database optimization: Rebuilding full text search tables. Jan 08, 2017 15:34:05.769 [0x700004110000] WARN - Held transaction for too long (../Library/FullTextSearch.cpp:16): 0.880000 seconds Jan 08, 2017 15:34:06.406 [0x700004110000] WARN - Held transaction for too long (../Library/FullTextSearch.cpp:26): 0.610000 seconds Jan 08, 2017 15:34:06.916 [0x700004110000] ERROR - SQLITE3:0x70000385c0d0, 11, database corruption at line 59437 of [fc49f556e4] Jan 08, 2017 15:34:06.916 [0x700004110000] ERROR - SQLITE3:0x70000385c0d0, 11, database corruption at line 59479 of [fc49f556e4] Jan 08, 2017 15:34:06.916 [0x700004110000] ERROR - SQLITE3:0x70000385c0d0, 11, statement aborts at 4: [] database disk image is malformed Jan 08, 2017 15:34:06.918 [0x700004110000] ERROR - SQLITE3:0x70000385c0d0, 11, statement aborts at 36: [insert into fts4_tag_titles(rowid, tag) select id, tag from tags where tag_type in (1,4,6)] database disk image is malformed Jan 08, 2017 15:34:06.918 [0x700004110000] ERROR - Exception inside transaction (inside=1) (../Library/FullTextSearch.cpp:35): sqlite3_statement_backend::loadOne: database disk image is malformed Jan 08, 2017 15:34:06.926 [0x700004110000] ERROR - Soci Exception handled: sqlite3_statement_backend::loadOne: database disk image is malformed

I’m unsure of how to repair the database. Have to wait for a ninja or other SQLITE knowledgeable person to comment on that.

I meant that I quit the server twice and restarted it twice. No problems doing that.
Thanks for looking at the logs. How were you able to do that?

The logs are just text files. I opened up the Plex Server log and looked for error messages.

If you haven’t disabled automatic database backups, you might be able to successfully restore a previous working database, or you could look into attempting to repair it yourself.

https://support.plex.tv/hc/en-us/articles/201100678-Repair-a-Corrupt-Database
https://support.plex.tv/hc/en-us/articles/202485658-Restore-a-Database-Backed-Up-via-Scheduled-Tasks-

Thanks again.

Went to look for backups of the database. They are there but for some reason the backups stopped running almost a month ago and I don’t know why. That’s farther back than I’d like to go but I guess I’ll do it if I have to. At least I know that’s an option.

I also tried using the database repair from the link that you provided but that didn’t fix the problem.

I wager the backups stopped when the database became corrupted.

Are there any other ways to repair a database or am I going to have to use the month old database and retrace all my viewing history in order to get back to where I am currently?

I’m not at all familiar with the database structure so I can’t help with that.

I appreciate all the help so far. I’m much farther along than I was. I was hoping that maybe there might be someone else who might have something to add.

If you downloaded the SQLITE tools, you could compare a backup to the current one. If there is damage it might be pretty obvious when you compare the two. It’s something to try until a database guru happens along.