Plex App Crashes and starts again but sometimes freezes pms

Hi,

I have been noticing using the plex dash app that the pms app suddenly switches off / crashes and then starts back again. During this time if it failed to start the pms up the pc/server gets stuck and freezes.
I first thought I was maxing my bandwidth but that wasn’t an issue.
Then I thought it was the RAM - still not 100% sure but I dont think this is the issue as it’s max has been 55%.
The processor is overkill and doesn’t go above 25%.

Not sure what the issue is here and no idea how to read log files properly.

Thanks.

Plex Media Server Logs_2020-05-13_06-04-04.zip (5.0 MB)

General comment 1: Turn off verbose logging. It can generate too much information and the log files wrap too quick. See Reporting Issues with Plex Media Server.

General comment 2: When watching media on a PC, use Plex for Mac/Win or Plex Media Player. Both direct play much more content than Plex Web (HEVC, Dolby Digital, etc). You’ll have less transcoding on your system. They can both pass Dolby Digital, dts, etc audio to a sound system as well (which web browsers cannot do).

Specific to your post:

Looks like database corruption. These statements repeat multiple times (Plex Media Server.x.log):

May 13, 2020 05:27:52.437 [13584] ERROR - SQLITE3:0x7c71ea17, 11, database corruption at line 85694 of [bf8c1b2b7a]
May 13, 2020 05:27:52.437 [13584] ERROR - SQLITE3:0x7c71ea17, 11, statement aborts at 165: [select media_items.id as 'media_items_id', media_items.library_section_id as 'media_items_library_section_id', media_items.section_location_id as 'media_items_section_location_id', me
May 13, 2020 05:27:52.438 [13584] ERROR - Butler: Uncaught exception starting generator DeepMediaAnalysis: sqlite3_statement_backend::loadRS: database disk image is malformed
May 13, 2020 06:01:54.351 [4332] ERROR - SQLITE3:0x7c71ea17, 11, database corruption at line 85694 of [bf8c1b2b7a]
May 13, 2020 06:01:54.351 [9600] ERROR - SQLITE3:0x7c71ea17, 11, database corruption at line 85694 of [bf8c1b2b7a]
May 13, 2020 06:01:54.351 [4332] ERROR - SQLITE3:0x7c71ea17, 11, statement aborts at 20: [select media_items.library_section_id, total(media_parts.size) as size, total(media_parts.duration) as duration from media_parts join media_items on media_parts.media_item_id=media_ite
May 13, 2020 06:01:54.351 [9600] ERROR - SQLITE3:0x7c71ea17, 11, statement aborts at 20: [select media_items.library_section_id, total(media_parts.size) as size, total(media_parts.duration) as duration from media_parts join media_items on media_parts.media_item_id=media_ite
May 13, 2020 06:01:54.351 [9600] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: database disk image is malformed
May 13, 2020 06:01:54.351 [4332] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: database disk image is malformed

See Repair a Corrupt Database for additional information.


I did as you said and this error came:

I continued the process and deleted the 2 db-shm and db-wal files and restarted.
Upon start plex did not run. it gave an error saying pms db is corrupt. I also got a notification that the db is corrupt.

What is the easiest solution to fix this issue?

If it won’t repair and you don’t have a backup, you can delete com.plexapp.plugins.library.db. Stop Plex Media Server before deleting the file.

You’ll have to recreate your libraries. You won’t lose any content.

From the support article:
Note : You can also simply delete the com.plexapp.plugins.library.db database file while the Plex Media Server is not running. Restarting the server will then restore your server to a nearly-fresh install state. (i.e. You will lose your existing libraries and need to recreate them , but you won’t be affecting your content itself.)

Ouch… What will actually stay intact after I delete that file apart from all the content?
Will server settings all disappear? What about metadata and the shows I watch etc?

Also, is this guaranteed to fix the crashing issue? The files in that folder don’t have a backup? :pensive:

Sorry, just freaking out as I have around 40TB of content and reorganizing all of that and not knowing my watching history will definitely be a pain in the ***!

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