Crash Reports directory empty, need visibility into Categories crash

Plex Media Server
,
1

Server Version#: 1.41.5.9522

My server, running as a Docker container, crashes every time I select Categories under the Movies library I have setup. To make matters worse, I see this in the Docker logs:

****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.41.5.9522-a96edc606/PLEX MEDIA SERVER/3e571ea9-f2f4-4cdc-00bf2692-a585e7d9.dmp

But when I go to the Crash Reports directory there is no crash log. It shows the directory as being updated but nothing’s inside, even when I use ls -a. I tried changing the permissions of the Crash Reports directory and the relevant subdirectories to no avail.

Any help welcome here.

2

Go to Settings → Server_Name → General and uncheck “send crash reports to Plex.”

IIRC when checked, PMS sends, then deletes, the crash report. If unchecked, it leaves the crash report in the directory.

I’ve never looked at one of the crash reports. No idea if it will help.


You might find Plex Media Server.log and rollovers helpful.

You will need debug (not verbose) level server logs enabled in Settings → Server_Name → General + Show Advanced.

When Plex starts, it rolls the log files. When you start Plex, it creates a new Plex Media Server.log. The previous Plex Media Server.log is now Plex Media Server.1.log (and so on, with the previous .5.log getting rolled off the end).

This means what Plex was doing when it crashed is at the bottom of Plex Media Server.1.log.

Note: Plex also rolls the log files when they reach a size limit.

Note: Plex writes DEBUG - BPQ: [Idle] -> [Starting] at the top of the Plex Media Server.log file when it starts. That is an easy way to find the time/date when Plex was launched.

Note: The log files are written by and for the devs. They can be cryptic and sometimes do not seem to make sense. Just keep that in mind when reading them.

1 Like
3

To add here,

In the Crash Reports directory, the ‘dmp’ file is PMS proprietary.
It’s entirely in binary and requires additional tools to decode.

2 Likes
4

This worked! I now have a readable .log file to puruse.

And as I do I see these a lot:

ERROR - [Req#6f02] Unknown metadata type: folder
ERROR - [Req#6f11] Unknown metadata type: folder
ERROR - [Req#6f72] Unknown metadata type: directory
ERROR - [Req#6f6f] Unknown metadata type: directory

And in the Plex Media Server.1.log file you mentioned, I see them there too. The last thing in that log file before the crash is this:

Completed: [IP address/port] 404 GET /photo/:/transcode?width=360&height=203&minSize=1&upscale=1&url=%2Fphoto%2F%3A%2Ftranscode%3FblendColor%3D704A23%26width%3D2560%26height%3D1440%26url%3D%252Flibrary%252Fmetadata%252F6778%252Fart%252F1726812708%26X-Plex-Token%3Dxxxxxxxxxxxxxxxxxxxx (18 live) #6f77 TLS GZIP 9ms 379 bytes (pipelined: 1)

Kinda feels like it’s looking for art, not finding it, and then crashing?

I’ve tried optimizing and repairing the database - neither seemed to help

Category Images Causing Plex Server Crash?
5

You can ignore them. The log files sometimes contain entries that are due to Plex making changes in the software, but not necessarily changing what is logged.

It is almost impossible to diagnose problems from one log entry.

If you attach the entire zip file, or at least the Plex Media Server.log to .5.log files, then people can take a look at what is happening.

1 Like
6

Is there anything I should remove from the logs before I post them here, for security reasons?

7

In the Plex Media Server.log and .1.log to .5.log files:

  • The e-mail associated with your Plex account.
  • The public IP address of your server.

Both should be listed, but not necessarily in every file. You can search/replace with a text editor to remove the info.

I’m not sure about the other log files.

Just attach the Plex Media Server.log to .5.log files. Can worry about the others if needed.

1 Like
8

Thanks for the help so far. Here are the logs.

EDIT: Removed

9

Just checked this again and it seems to work now? Weird but not questioning it. Thanks to everyone for their help. Will close this out.

10

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