Crashes on 918+

Server Version#: 1.21.4.4079-1b7748a7b
Player Version#:
Logs.zip (5.0 MB)

Good morning Team,

I have tried to search for problems in the logs but with little to no success from the other posts there. I see a number of errors in the thumbnails which I don’t think is a problem, but also see some issues with some recently added content around codecs.

I have also:

  • Plugged in just a single ethernet cable
  • Set a static IP assignment

Any assistance would be appreciated

I just cleared the log files this morning and got a fresh crash 5 minutes ago :slight_smile:recent logs.zip (71.4 KB)

Thanks. I am not using 2 connections. I was trying to simplify :slight_smile:

Thanks. I guess I’ll hold to see what guidance there is.

:sob: if anyone could help would be great

i have but I am still crashing. I will take another update tonight…

At least i can get this to crash every day :slight_smile:

Fix is coming soon, mainly seem happening when connecting with an android device:

1.22.2.4264-b275c4330 was released yesterday to Plex Pass beta.

In conjunction: Android 8.15 / 8.16 (not sure which version).

Thanks! Loaded. If the android clients aren’t upgraded will i still be subject to crash?

Possible. Less likely but still possible.

Thanks to everyone. I have loaded but still get crashes VERY often. i have tried to look through the troubleshooting steps from others but can’t seem to find anything I haven’t done. I’ve attached the latest which I believe was barely even 12 hours (very little use now with frequent crashes).

Logs.zip (737.9 KB)

Thanks for the logs.

Unfortunately, they don’t give a clue where it’s failing.

It’s time to dig deeper.

Please do the following.

  1. Settings - Server - General - Show Advanced
  2. Turn off “Send Crash Reports to Plex” (disable uploading)
  3. SAVE the change

Now, when it does crash again.

  1. Using FileStation, → Plex shared folder / Library / Application Support / Plex Media Server / Crash Reports.

  2. Make a ZIP file of everything and attach that ZIP file here.

  3. Also attach the Log files ZIP again

  4. Between the two, I will use the debugger and try to retrace the last thing it did.

It the minimum , it will tell me the point of failure but not why.
At best, it will show the point of failure AND the condition which caused the crash (the debugger will show it if it’s there )

Thanks. Just had another crash. I’ll do so now.

Attached. 1.22.2.4264-b275c4330.zip (38.7 KB)

Thank you.

I think I see it.

Do you have a lot of collections or were you manipulating them?

EDIT: I submitted the trouble report to engineering based on what I saw. I hope it is what you’re seeing.

Here’s what I have:

  • All Movies
  • Kids Movies (a folder inside all movies)
  • Anime
  • TV shows (which has HD Homerun writing news)
  • Family Videos (almost never has stuff added to it)

The collections are being updated with Sonar periodically.

I suspect that maybe Sonar was running a fetch, as that can happen at any time. What’s the best way to do this?

Do you have sonarr directly communicating with PMS?

If so, you might want to disable that for now.

What I saw in the debug memory dump (crash file) is when it was trying to update collections.

I was seeing what looked like an external event requesting but wasn’t sure.

If sonarr is making requests / posting about collections then we’ve found what is causing it.

can you confirm?

Thanks @ChuckPa - When you say, “communicating”, it drops files into a folder that’s being monitored by PMS. Other than that, there is no other integration.

Question - could this also be the PVR? It’s an HD Homerun

When I asked “communicating”, I was specifically referring to Sonarr’s ability to run scripts (the Connector feature).

If you are experiencing this problem when new media, which happens to be part of a collection, is deposited by Sonarr into the monitored location, then I’ve found the problem.