thanks sa2000 you have been awesome through this whole thing
@jorgisimo said:
yeah you have to kill everything. Ok so mine died last night. i didnāt get the 503, but it was stuck so its hard to tell if it was the same error. i was able to get the token and the logs, but the proc wouldnāt take the dmp for some reason. I restarted everything and restarted proc to see if next crash i get the full thing.
Same thing for me jorgisimo, I tried to get it to crash by using Web player on Firefox, jumping around to different movies, changing qualities etc. Looks like it finally hung/crashed around 8:23PM. I didnāt get the 503 for a bit longer, for the time immediately after the hang/crash browsers trying to load plex hung at waiting for localhost, or the ip when trying from another machine. Eventually it started doing the 503. Odd thing I was unable to get a full or mini dump w/ Process explorer before it starts the 503 error. I get Error configuring dump resources: The system cannot find the file specified.
I had to wait until the actual 503 error appeared before it (Process Explorer) would allow me to dump the process.
@pettcomputers said:
Odd thing I was unable to get a full or mini dump w/ Process explorer before it starts the 503 error. I get Error configuring dump resources: The system cannot find the file specified.I had to wait until the actual 503 error appeared before it (Process Explorer) would allow me to dump the process.
Just googled that and there has been discussions on this. But there is one here but it is old - so probably not relevant
https://forum.sysinternals.com/forum_posts.asp?TID=29785&PID=140933&title=procexp64-1540-create-dump#140933
Anymore headway on this issue?
@chase.messer@live.com said:
Anymore headway on this issue?
A problem with DASH transcoder threads has been identified and a fix is being worked on
@sa2000 said:
@chase.messer@live.com said:
Anymore headway on this issue?A problem with DASH transcoder threads has been identified and a fix is being worked on
Oh thank you!
I just ran into this same problem
I went into Task Manager and stopped all Plex and Python services and relaunched Plex. Works fine again.
im also running into this problem when i optimize movies.
Read about a guy online that ran into 503 problem. but he diddent reboot, just leed is stand online the night over. the next day i working normal again. maybee a large database takes a lot of time for the pc to go through.
I havent had a crash since i stopped optimizing.
Regards.
A fix for a deadlock problem relating to DASH protocol transcoding will be in the next Plex Pass release (the one after version 1.7.6)
Sounds nizzel.
It kind of sucks having 2 machines do the job.
@sa2000 said:
A fix for a deadlock problem relating to DASH protocol transcoding will be in the next Plex Pass release (the one after version 1.7.6)
That is great news!!
Iām experiencing the same problem I get a 503 error. When I look at the process loads during the crash it usually happening when the server is doing a lot of transcoding so is this DASH protocol transcoding fix likely going to fix my issue? Iāll try and get the dump etc if it doesnāt
@Humac said:
Iām experiencing the same problem I get a 503 error. When I look at the process loads during the crash it usually happening when the server is doing a lot of transcoding so is this DASH protocol transcoding fix likely going to fix my issue? Iāll try and get the dump etc if it doesnāt
The logs covering period before the deadlock starts and up to the time it is deadlocked together with the crash dump would help confirm if it is
I got another 503 deadlock issue. Donāt know if you guys have enough information to resolve the issue or my logs will provide additional info? I saved the logs, I triggered the crash upload, and also saved the output from http://localhost:32400/connections?X-Plex-Token=XXXXX . Running 1.7.6 on Ubuntu 16.04.
@anhtuan99 said:
I got another 503 deadlock issue. Donāt know if you guys have enough information to resolve the issue or my logs will provide additional info? I saved the logs, I triggered the crash upload, and also saved the output from http://localhost:32400/connections?X-Plex-Token=XXXXX . Running 1.7.6 on Ubuntu 16.04.
Need logs to help try and find the crash dump - hopefully it got uploaded ok. It is not a direct route. I cannot find any servers owned to your forum account -
https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files
@sa2000 said:
@Humac said:
Iām experiencing the same problem I get a 503 error. When I look at the process loads during the crash it usually happening when the server is doing a lot of transcoding so is this DASH protocol transcoding fix likely going to fix my issue? Iāll try and get the dump etc if it doesnātThe logs covering period before the deadlock starts and up to the time it is deadlocked together with the crash dump would help confirm if it is
So i got the crash again, here is a link to the connections file, logs and dump
https://1drv.ms/f/s!AP5jOeQ1U0Oncg
Thanks
@Humac said:
@sa2000 said:
@Humac said:
Iām experiencing the same problem I get a 503 error. When I look at the process loads during the crash it usually happening when the server is doing a lot of transcoding so is this DASH protocol transcoding fix likely going to fix my issue? Iāll try and get the dump etc if it doesnātThe logs covering period before the deadlock starts and up to the time it is deadlocked together with the crash dump would help confirm if it is
So i got the crash again, here is a link to the connections file, logs and dump
https://1drv.ms/f/s!AP5jOeQ1U0Oncg
Thanks
Thanks - debug logging was switched off on the server ! Also I could not find the /connections file
Aside from that, the dump shows some DASH transcoding activity and I suggest we wait for the fix for the deadlock for dash transcode threads and see if we still have a problem to investigate after that. The fix for the dash related deadlocks is expected in the next release
@sa2000 said:
@anhtuan99 said:
I got another 503 deadlock issue. Donāt know if you guys have enough information to resolve the issue or my logs will provide additional info? I saved the logs, I triggered the crash upload, and also saved the output from http://localhost:32400/connections?X-Plex-Token=XXXXX . Running 1.7.6 on Ubuntu 16.04.Need logs to help try and find the crash dump - hopefully it got uploaded ok. It is not a direct route. I cannot find any servers owned to your forum account -
https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files
Sorry forgot that Iām running my server under another username: phoenixadmin
And Iāve attached the out from the /connections page.
@anhtuan99 said:
@sa2000 said:
@anhtuan99 said:
I got another 503 deadlock issue. Donāt know if you guys have enough information to resolve the issue or my logs will provide additional info? I saved the logs, I triggered the crash upload, and also saved the output from http://localhost:32400/connections?X-Plex-Token=XXXXX . Running 1.7.6 on Ubuntu 16.04.Need logs to help try and find the crash dump - hopefully it got uploaded ok. It is not a direct route. I cannot find any servers owned to your forum account -
https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files
Sorry forgot that Iām running my server under another username: phoenixadmin
And Iāve attached the out from the /connections page.
Thank you - which of the 3 active servers on that account was it?
Release 1.8.0 of Plex Media Server has just been released for Plex Pass. It has the DASH transcoder deadlock fix
If you are a Plex Pass user, please upgrade and report back if this fixed your deadlocks and error 503. If not then we will need a new investigation with new set of diagnostics to investigate
See Release Notice http://forums.plex.tv/discussion/comment/1488006#Comment_1488006
