New Plex Pass/Beta Release crashes immediately

Hi, the new Plex Pass release 1.19.5 crashes immediately upon startup for me. At first I assumed something happened when it was updated automatically. I manually reinstalled it and same thing, dumps as soon as I open it. So maybe corrupted DB, in which case I restored from an earlier version but to no avail, same outcome.

That said, rolling back to 1.19.4 seems to work without issue.

It doesn’t look like there’s a flood of people on MacOS running into the same issue so I would assume it’s not a bug, but not sure what could be occurring on my end to cause the crash.

Any guidance or suggestions would be appreciated. I can attach more of the log files if needed. Thanks
PMS log file

Well… that’s a log file from your 1.19.4 install (rollback).
Are you sure the Plex Media Server is working without issue after you rolled back to 1.19.4? The log is full of network errors (failing to connect to your gateway, failing to connect to plex.tv – looks like you’re either using different subnets or you might be stuck in a CGNAT setup (ISP assigns private IP address to their customer).

Then again… that should block you from accessing your server remotely and maybe from streaming some online sources – probably not related to your app crashing in the first place.

1 Like

Thanks for jumping in.

The errors with the weird subnet is plex constantly recognizing Xteve (IPTV emulator that looks like an HDHomerun) that’s running in a docker. Even though it’s not setup with Plex, it’s constantly pinging it. I dont know of a way to stop it other than turning it off (and I use it).

Unless you see something else that I’m not privy to? But that’s what being referred to over and over.

I just realized I’m not sure how to produce 1.19.5 logs since it wont run. If I start it, it comes down inside a few seconds.

Usually each restart produces a new log and Plex’ rolling log approach always keeps 6 of them in the logs folder. So even if the startup failed you should have logs from it.

hey thanks. I’ve attached them here. I wasnt sure if I should inlcude all of them or notPlex Media Server.log (22.8 KB) Plex Media Server.1.log (5.0 KB) Plex Media Server.2.log (4.3 KB) Plex Media Server.3.log (10.6 KB) Plex Media Server.4.log (3.4 KB) Plex Media Server.5.log (3.1 KB)

Can you please…

  • enable “Debug logging” in your server settings (Not Verbose logging!)
    Settings > [Server Name] > General > Enable Plex Media Server debug logging
  • update to 1.19.5 and try running the server
  • after it failed, upload “Plex Media Server.log”
    • alternatively downgrade to 1.19.4 and download the entire log zip file from there (in which case it’ll be easiest just to upload the entire zip file)
      Settings > [Server Name] > Manage > Troubleshooting > Download Logs
1 Like

Sure thing, will do that now. thanks a lot

OK I upgraded to 1.19.5 and it crashes immediately as discussed. I opened it 2x and it crashed 2x and then I pulled the logs. The zip is attached herePlex Media Server Logs_2020-07-08_09-43-23.zip (1.7 MB)

Are you sure it’s crashing right away or will 1.19.5 crash when you attempt to start playing some media?
According to the logs you created that new log package from within Plex Web running on your PMS 1.19.5 :wink:

The previous logs don’t show much detail for the actual crash. It seems your server is picking up on a previously not completed scan, adding/updating a number of seasons of “The Simpsons”. At some point before the crash Plex gets an event message it cannot deal with. I suppose that message is what’s causing the crash.

Adding to the feedback you had, the crashes appear to be related to dialogue with shared server “Tony’s Server” which has a domain name as the access route

Is it a remote server ?

Could you get the xml from this request and copy into a text file and zip it and send it privately using Private Message

https://plex.tv/api/resources.xml?includeHttps=1&includeRelay=1&auth_token=xxxxxxxxxxxxxxxxxxxx

You would need to replace the xxxxxxxxxxxxx with the server token - there is an article here for how to find a valid token

2 Likes

It’s primarily crashing immediately upon startup. When I just reinstalled it to pull the logs, I opened it, it crashed. I opened it again. It didn’t crash immediately and I trued to play something then it crashed. But that was the first time I’d gotten past the first few seconds of it opened. Every other time it’s been immediately.

That’s interesting. That’s a friends remote server yes.
Re: XML, Absolutely, I’ll put that together now. Thanks a lot.

ok so I removed “Tony’s server” and installed 1.19.5. It’s not crashing immediately but I get “playback error” message for anything I try to play.

@sa2000
@tom80H

I resintalled 1.19.4 and now it’s also going the same exact thing. It opens but can’t play any media.

Very weird. I attached the logs from this latest session in case it offers any other insight.

Update- I deleted Plex and restored the database with an older backup than I had restored earlier. Reinstalled 1.19.5 and so far so good. No crashing, everything is playing (knock on wood). Maybe it was a corrupted DB and I didn’t go back far enough the first time I replaced it? What threw me off was the fact that 1.19.4 was working fine (until it wasn’t) but not the most recent release.

If all it was, was a corrupted DB I apologize for spinning your wheels with something I could’ve corrected myself. Very appreciative for the attention you both gave to it.

@sa2000 if you see anything from the XML I sent you I would still very much like to hear your thoughts. Otherwise much thanks to you both.

Looks ok - only non standard aspect is the use of domain name for the shared server. You could get that share back again and let me know if the crashes come back

OK ill get it back and let you know if the issue returns.
I turned off the tuner emulator to get a look at the logs without that issue filling the page.
I noticed I’m getting a ton of these:
SLOW QUERY: It took 14170.000000 ms to retrieve 1 items.

Isn’t that a possible indication of a corrupted database? Im wondering if I really dodged this issue.

could be because database needs optimizing / could be that you have large libraries

To run an optimize (note that when optimize runs, plex apps accessing the server may get time outs)

  • Settings / Server / Troubleshooting / Optimize Database

Any update on getting access to that shared server again?

I think you nailed it- he invited me back on and as soon as I accept the invite, it crashes. Reopening it now recreates the problem I originally posted about, I can’t keep plex on for more than a couple seconds since I added his server back on.

I’ve attached the logs here. Thanks a lot for the help here. [Plex Media Server.log|attachment]

Thanks for the confirmation. I am guessing it is to do with the shared server having a domain name for access rather than just an IP Address and port.

I have referred the crash to our Plex Media Server development team

Very appreciated! There is no way I would’ve ever figured this out on my own. What’s weird is I’ve been connected to his server for a year and this just started. Either way, this is definitely the issue.
I’ll mark this as solved.

Curious, isn’t his custom URL used the same way as I use in “Custom server access URL” setting here?

plex server domain

It looks like a 1.19.5 regression