Crash updating to any 1.23.2.46xx version on Ubuntu 20.04

May I have everyone’s minidump file ?

(do this by turning off “Report Crashes to Plex” & saving. then make the crash and grab the DMP from the Crash Reports directory)

@ChuckPa not sure what zip file you’re referring to

The downloaded Plex Logs ZIP file which shows what Plex was doing when it crashed.

It’s probably too late now. The log bufffers don’t last long.

Can you share what you found? Maybe something I can keep an eye out for here?

I also didn’t realize I should have just used the Download Logs button, I was just grabbing the changed logs directly from the server. I’m not familiar with all the new troubleshooting options you guys have introduced.

As an aside, I have two HDHomeRun PRIME units for a total of 6 tuners. Although the crash occurred after I had added just one back in, so I don’t believe the number is the issue, but the EPG data that is being stored/delivered. I was seeing errors with database schema in metadata-items and double quoted literals. My gut is still that the update is trying to reconcile DVR related database rows that are not what it’s expecting.

Logs.zip (25.2 KB)
@ChuckPa is this what you need? I grabbed the logs straight from the filesystem. For what it’s worth, I don’t think Plex would have stayed up long enough for me to grab them via the web UI anyway.

@irishpadres

I am sorry but:

  1. You only gave me the “Current” logs . I also need the rollover logs.
  2. This is windows. I can’t help. I don’t know / support Windows.
Jun 07, 2021 19:00:15.055 [18936] INFO - Plex Media Server v1.23.2.4656-85f0adf5b - Microsoft PC x64 - build: windows-x86 windows - GMT -07:00
Jun 07, 2021 19:00:15.055 [18936] INFO - Windows version: 10.0 (Build 19043), language en-US
Jun 07, 2021 19:00:15.055 [18936] INFO - 20 3600 MHz processor(s): Architecture=0, Level=6, Revision=42245 Processor Identifier=Intel64 Family 6 Model 165 Stepping 5, GenuineIntel
Jun 07, 2021 19:00:15.055 [18936] INFO - Compiler is - MSVC 1924

@ChuckPa Seems like this might be platform agnostic. Is there someone else on the Windows side who can help figure this out?

May I at minimum see the “rollover” log which captures the “Crash Uploader” messages so I can see what PMS was doing immediately prior to the crash?

The only thing remotely agnostic I know of at present is a possible EPG updating.

I have this problem and I have a dmp file but I cannot upload it because it is not an allowed extension.

@prizzo

  1. Put the DMP in a ZIP
  2. Please include the Server logs ZIP as well (so I can get the info for the DMP from it)

Zipped up the the Logs dir and Crash Reports dir. It was too big to upload so here’s a link. FYI I nuked my entire install and did a clean install of plexmediaserver_1.23.2.4656-85f0adf5b_amd64.deb and it is still crashing. logs-dump.zip - Google Drive

@prizzo

Thanks, I got the files.

You can now go into the Crash Reports and clear everything out.

It should never be that built up .

I’m working with the build team now to figure out where it’s crashing. (Technology is fighting me today)

The last lines of my log files definitely show it’s crashing in the middle of subscription/EPG updates.

Thank you VERY much. I’ve reported that to engineering (a heads up) until I can give them a definitive location / lines of code to look at

1 Like

That’s interesting, I do only have one current scheduled ongoing DVR recording. NHL Hockey. I wonder if I were to remove that scheduled recording if it would change anything and avoid the crash until I recreate it again? Might try to toss that idea at the wall later and see if it sticks. I’ll report back if I get a moment to try it.

I’ll send over the full logs (and historical) when I report back, maybe there is something else in the older logs to learn what’s causing this before the update can’t manage to navigate it’s way around it.

I had to revert to plexmediaserver_1.23.1.4571-6119e8eed_amd64.deb. This version seems stable and appears to be working correctly.

Both plexmediaserver_1.23.2.4600-f06057b33_amd64.deb and plexmediaserver_1.23.2.4656-85f0adf5b_amd64.deb had similar issues with constant crashes.

I’ve opened a trouble report with engineering and provided the info I have.

Hopefully I can get some assistance digging in and finding where this is going sideways.

2 Likes

I am definitely getting somewhere now with narrowing down what’s happening.

This morning I removed the DVR Setup, after canceling the single recurring recording I have.

I was then able to install 1.23.2.4656, and was then able to add the DVR with both of my tuners back. Took a long time to finish the EPG data as normal and threw some errors, but nothing that seemed critical and the server carried on with life.

After the server finished all the EPG downloads and some waiting thumbnail generation tasks without issue I then played a file on the WebUI, still no issues.

I then went to add back my single recurring recording for NHL Hockey of all Boston Bruins Events, and the server immediately crashed. The Logs and .dmp here are from that specific crash event snapshot. I pulled all the current .log files as well as the .dmp file created at the time of crash.

I then had to revert back to 1.23.1.4571 to get back into the server. Once I was back in, I removed the recurring recording again and then reinstalled 1.23.2.4656. I then proceeded to add a single recording for the single-game airing tonight and it added without incident or crash and the server is still running fine about 30 minutes later.

So it would seem the crash is very directly related to adding (or readding existing ones from the database after DVR is set back up) recurring recordings, which I believe is the very last step once the EPG data is downloaded. Hopefully, the actual incident is captured in the logs and .dmp I uploaded.

Hopefully, other adventurous souls can confirm my findings and this helps the engineers to pinpoint the exact issue. Until then I guess I’m recording the Stanley Cup Playoffs one scheduled recording at a time.

PMSLogs.zip (610.8 KB)

1 Like

@ChuckPa

Any updates? I was hoping my findings would help move things along or at least give a focal point for the engineers to look at.

1 Like

+1 for an update. I’ve had to completely disable the DVR so I’m unable to record any shows until this issue is fixed.