Plex Media Server crashing

Plex Media Server Desktops & Laptops
,
1

Server Version#:1.16.5.148
Player Version#: Various players

Tried to find the .dmp files, however they seem to disappear as quick as they appear, Im running Plex on a docker on an unraid server and it appears to be crashing quite often during playback, I get this on the docker logs

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 40-chown-files: executing…
[cont-init.d] 40-chown-files: exited 0.
[cont-init.d] 50-gid-video: executing…
[cont-init.d] 50-gid-video: exited 0.
[cont-init.d] 60-plex-update: executing…
Atempting to upgrade to: 1.16.5.1488-deeb86e7f
2019-08-19 12:12:04 URL:https://downloads.plex.tv/plex-media-server-new/1.16.5.1488-deeb86e7f/debian/plexmediaserver_1.16.5.1488-deeb86e7f_amd64.deb [75114310/75114310] -> “/tmp/plexmediaserver_1.16.5.1488-deeb86e7f_amd64.deb” [1]
(Reading database … 10423 files and directories currently installed.)
Preparing to unpack …/plexmediaserver_1.16.5.1488-deeb86e7f_amd64.deb …
Unpacking plexmediaserver (1.16.5.1488-deeb86e7f) over (1.16.4.1469-6d5612c2f) …
Setting up plexmediaserver (1.16.5.1488-deeb86e7f) …
Processing triggers for libc-bin (2.27-3ubuntu1) …
[cont-init.d] 60-plex-update: exited 0.
[cont-init.d] 99-custom-scripts: executing…
[custom-init] no custom files found exiting…
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting Plex Media Server.
[services.d] done.
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.16.5.1488-deeb86e7f/PLEX MEDIA SERVER/06540832-7edf-6e9a-61bbd756-6c2ade2b.dmp
Starting Plex Media Server.
Dolby, Dolby Digital, Dolby Digital Plus, Dolby TrueHD and the double D symbol are trademarks of Dolby Laboratories.
Connection to 172.104.59.203 closed by remote host.
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.16.5.1488-deeb86e7f/PLEX MEDIA SERVER/4d790e4c-587f-4b12-4e28a105-79fa5eed.dmp
Starting Plex Media Server.
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.16.5.1488-deeb86e7f/PLEX MEDIA SERVER/19417252-27fc-f239-3f01c7dd-133b74b5.dmp
Starting Plex Media Server.
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.16.5.1488-deeb86e7f/PLEX MEDIA SERVER/092744ff-c7de-a98b-2e8007d6-526be3e7.dmp
Starting Plex Media Server.
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.16.5.1488-deeb86e7f/PLEX MEDIA SERVER/38b88ff3-b23e-f25d-5b8b14b6-64f4c85e.dmp
Starting Plex Media Server.
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.16.5.1488-deeb86e7f/PLEX MEDIA SERVER/35c0c304-1752-3057-0a0b736e-66dd08a3.dmp
Starting Plex Media Server.
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.16.5.1488-deeb86e7f/PLEX MEDIA SERVER/32fc9895-c2c5-92bf-38cccc63-289aaa6b.dmp
Starting Plex Media Server.
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.16.5.1488-deeb86e7f/PLEX MEDIA SERVER/4229b432-f15e-dbff-7e57e9b2-3327ef73.dmp
Starting Plex Media Server.
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.16.5.1488-deeb86e7f/PLEX MEDIA SERVER/7e6957f8-6150-345f-2be3e048-33edc8dd.dmp
Starting Plex Media Server.

But when I check for logs on the location specified there is no long written.

I had a scour through the server logs themselves, I’ve noticed around the time of crashing there is this reported
Aug 23, 2019 15:20:10.517 [0x14e550edc700] ERROR - SQLITE3:(nil), 11, database corruption at line 79051 of [bf8c1b2b7a]
Aug 23, 2019 15:20:10.517 [0x14e550edc700] ERROR - SQLITE3:(nil), 11, statement aborts at 35: [select taggings.id, count(*) as taggings_count from tags join taggings on taggings.tag_id=tags.id join taggings as related on taggings.tag_id=related.tag_id join metadata_items o

Anyone able to offer any advice on how to fix or upload proper logs?

1 Like
2

The problem is your database is corrupt and must be resolved first.

Repairing a corrupt database is pretty easily done outside a container but it’s a lot tougher (need SQLITE3 to repair it inside the container -or- you need pull the DB out, repair it, then put it back.

I respectfully submit it’s easier to start over. These type corruptions occur when the system / container is stopped harshly (power-off, etc) PMS needs a few moments to flush all its buffers to the DB. When it can’t, this type problem occurs.

If you have no specific reason for using docker, may I suggest the native package? It will afford you the freedom to make such repairs more easily.

Aug 23, 2019 15:20:10.517 [0x14e550edc700] ERROR - SQLITE3:(nil), 11, database corruption at line 79051 of [bf8c1b2b7a]
Aug 23, 2019 15:20:10.517 [0x14e550edc700] ERROR - SQLITE3:(nil), 11, statement aborts at 35: [select taggings.id, count(*) as taggings_count from tags join taggings on taggings.tag_id=tags.id join taggings as related on taggings.tag_id=related.tag_id join metadata_items o
3

Ok thanks Chuck, I’ll remove the docker image and start over again

I’m using docker because my server is an unraid box, it uses dockers as applications, as far as i know I cant run a native plex app on unraid

4

Ah. That explains it. You have my condolences. I failed to see the unraid tag.

I presume there’s a UPS on that?

5

There is indeed a UPS

6

Played around a bit more, Managed to pull the database out, attempted to repair and it failed, making the database 0kb in size, noticed there was a backup sitting there from 23 days ago (thought it was suppose to backup every 3 days?), replaced it with the backup and its all back to normal

7

Have you seen this thread?

8

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