Plex Version 1.2.2.2857 "crashes"

@ElCapitano said:
Mac Mini → OSX Sierra → PMS Version 1.2.0.2838 . . . (DVR Beta)
Just became non-responsive again. .
Attached logfile.

That is an incomplete log file.
It shows server is signed in but Plex Web app accessing through localhost is not signed in or has wrong credentials or different plex.tv account signed in from that for the server?

The log shows a shutdown at 11:30:24.
Can only see one request logged - could be running out of resources / hung threads.

Next time this happens - whilst the Plex Media Server application is still running, put the folowing request in a browser substituting the xxxxxxxxxxxxxxxxxx for your server account token and copy the output to text file and attach together with zip of all the log files (complete log files)

http://localhost:32400/connections?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxxxx
Selecting all the returned displayed text and copying to a text file and saving and attaching that text file.
The token string you need to put in on the request and you can find out the value of your X-Plex-Token string as outlined here
https://support.plex.tv/hc/en-us/articles/204059436-Finding-your-account-token-X-Plex-Token

May be similar to what was seen here http://forums.plex.tv/discussion/240692/1-2-2-crashing-offline-or-on-but-inaccessible-locally-or-remoteley/p1

@ChuckPa said:
That’s a pretty general statement and not been general observation so far but it works just fine with my Samsung (2015 model) as I’m sure it does others.

We need to see if we can tighten down a control case (fixed, known bitrate & format media, etc) and make this so we can repeat it. Once repeatable, the rest will be trivial.

How can we start whittling this down into a sharper point?

Yeah, it is general. But I have at least 3 remote Samsung TVs with constant buffer or kicking off issues since I installed 1.2.2.x, all Remote. Then I happen to use my own Samsung TV (which I rarely use) and notice the same problems on my gb LAN. Once I rolled back ( had 1 user texting me and the other on the phone) they immediately were back up and running like normal. My personal TV was also behaving as normal.

Take my comments for what they are. Just my insights. Take them or leave them.

@foebik said:

@ChuckPa said:
That’s a pretty general statement and not been general observation so far but it works just fine with my Samsung (2015 model) as I’m sure it does others.

We need to see if we can tighten down a control case (fixed, known bitrate & format media, etc) and make this so we can repeat it. Once repeatable, the rest will be trivial.

How can we start whittling this down into a sharper point?

Yeah, it is general. But I have at least 3 remote Samsung TVs with constant buffer or kicking off issues since I installed 1.2.2.x, all Remote. Then I happen to use my own Samsung TV (which I rarely use) and notice the same problems on my gb LAN. Once I rolled back ( had 1 user texting me and the other on the phone) they immediately were back up and running like normal. My personal TV was also behaving as normal.

Take my comments for what they are. Just my insights. Take them or leave them.

I am keeping track of everything. I’m not discounting you. I am requesting for your help in tracking down / sharpening what may be an issue. That’s all.

@foebik said:

@ChuckPa said:
That’s a pretty general statement and not been general observation so far but it works just fine with my Samsung (2015 model) as I’m sure it does others.

We need to see if we can tighten down a control case (fixed, known bitrate & format media, etc) and make this so we can repeat it. Once repeatable, the rest will be trivial.

How can we start whittling this down into a sharper point?

Yeah, it is general. But I have at least 3 remote Samsung TVs with constant buffer or kicking off issues since I installed 1.2.2.x, all Remote. Then I happen to use my own Samsung TV (which I rarely use) and notice the same problems on my gb LAN. Once I rolled back ( had 1 user texting me and the other on the phone) they immediately were back up and running like normal. My personal TV was also behaving as normal.

Take my comments for what they are. Just my insights. Take them or leave them.

There is an issue with Samsungs where when Direct Play is used they bombard the server with requests and the server ends up with hundreds of queued requests for each Samsung TV and could lead to the too many open files issue and running out of resources. There does not seem to be any flow control. Disabling Secure Connections has been seen to make it slightly better.

well mine kinda crashes just noticed and gone back to the none plex pass version without the throttling on,
works all fine internally , but externally phone will play fine, 20 mins later it reports a error that it cannot play, and people using the client report that there is not enough bandwidth , when there is no one on, restart plex all good , have down graded till it gets sorted, can i send you the old logs before they get written over , where are they ?

you should have “Settings - Server - Help” to get the logs (should be in 1.1.4)

If not , under Plex’s Application Support directory in the ‘Logs’ subdirectory

Trying out 1.2.3.2914. Hopefully it’s better!

@jojogrosso said:
Trying out 1.2.3.2914. Hopefully it’s better!

Please let us know. Im currently waiting this time to see if there are any additional reported problems.

@foebik said:

@jojogrosso said:
Trying out 1.2.3.2914. Hopefully it’s better!

Please let us know. Im currently waiting this time to see if there are any additional reported problems.

So far it seems pretty stable. Haven’t had any issues since it was installed. Remote users haven’t been getting errors either. We’ll see how this week goes.

Actually the issue I am having is when using DLNA, for some reason I notice if I pause the file, and the play it again, it tends to play for a a little and then skip right to the next file. If I don’t pause it, it plays flawlessly.

@jojogrosso said:

@foebik said:

@jojogrosso said:
Trying out 1.2.3.2914. Hopefully it’s better!

Please let us know. Im currently waiting this time to see if there are any additional reported problems.

So far it seems pretty stable. Haven’t had any issues since it was installed. Remote users haven’t been getting errors either. We’ll see how this week goes.

Actually the issue I am having is when using DLNA, for some reason I notice if I pause the file, and the play it again, it tends to play for a a little and then skip right to the next file. If I don’t pause it, it plays flawlessly.

Do you have any issues with smart TV clients? I had a lot of issues with the clients for Samsung mostly, but I think other smart TV stuff was also affected. They just didnt seem to play nice with the new feature set for bandwidth that was introduced in the last version.

All, Over at this thread, I’ve been focusing folks about the ‘crashing’ and ‘hang’ issues with PMS 1.2.3

Please feel free to join in . You’ll see the latest we have. I will be focusing further efforts there to avoid duplication.

Plex-Media-Server 1.2.7.2987 has just been released and it has a fix which hopefully will resolve this issue
See Release Notice

Please upgrade to 1.2.7 and let me know if the problem goes away - if not - usual requirement for logs etc

I still have a family member having playback issues on his iPhone 6. The app is fully updated as well as my server.

@dbratt said:
I still have a family member having playback issues on his iPhone 6. The app is fully updated as well as my server.

playback issues is very different from a server locking up and no requests processed from anywhere

Please look at the support pages and raise a forum topic with diagnostic logs from the client app and the server. The support web site - home page here http://support.plex.tv has the information you would need for logs