Anyone who needs PMS 1.13.4 for Synology, please post here and I will repost the link.
1.13.8 had a fix for an issue affecting remote access - that issue was still there in 1.13.7
Also the changes for network interface selection that came into 1.13.5 introduced new bugs and led to issues if used and ipv6 is enabled - This has now been superseded with a new preferred network interface setting 1.13.9 - it is still has teething issues and a restart is needed after setting it.
If the issue you observed in 1.13.7 is still there in 1.13.9 then would like logs of the problem so it can be investigated and resolved.
would it be possible to get diagnostics for that on 1.13.9 so it can be looked into ? and would be also beneficial to get logs for similar test on 1.13.4
It may be necessary to get logs from both the client app and the server
Thank you for sending me the logs. Very useful.
Looks transient lockouts when PMS is communicating with the router - results in timeouts at the client end
Same issue as unearthed with evidence from @audelair diagnosed as deadlock Cannot find Plex Server after upgrade (last working version 1.13.4.5271) - #14 by sa2000
It is a transient deadlock for 2 minutes but that is much more than the client apps timeouts of 15-30 seconds and also the deadlock repeats itself later
The issue has already been referred to the development team
If you can provide the deadlocks evidence as provided by @audelair that would help.
The more evidence we have and I do mean evidence as opposed to saying it does not work, the higher up the list of priorities an issue gets and the faster resolution
Diagnostics for Deadlocks on NAS/Linux (Transient Deadlock - circa 2 minutes)
- Ensure debug logging remains enabled. (Settings / Server / General / Show Advanced)
- Ensure crash reporting is enabled. (Settings / Server / General / Show Advanced)
When you get the lockout and client apps failing with an error , do the following
in a browser get this request to this server
http://10.0.0.2:32400/connections?X-Plex-Token=xxxxxxxxxxxxxxxxx
Substitute the server token for the xxxxxxxxxxxxxxxxxxx
See this article for how to find the token
https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
(This assumes your server remains on IP address 10.0.0.2)
Copy the response to a text file and note down the time the request was made and send the text file to me by private message referencing this forum topic and giving the time it was done
Then get a process dump through the command line in Linux
kill -SEGV <pid>
where <pid> is the PID number for the plexmediaserver process
The crash report should get uploaded when you restart the server
Wait for few minutes and then get the logs zip and attach here. The crash uploader logs would give the information I need to locate the dump. The other logs would be needed for the investigation of the deadlock
1 Like
I am going to stay on 1.13.4 until mid-November, when I have time to play with this again. Iāll update to 1.13.9 (or current) and that time and report back.
Still an issue in 1.13.9.5456-ecd600442
Also wanted to report back that with the windows and Linux versions of the server enabling external access does not cause this issue.
so only NAS?
The issue is still with the development team to look at
Correct only Synology NAS. While I only ran the windows and Linux server versions a few days I did not encounter the issue.
I am still running 3 versions of the server (Synology, Windows, Linux) to be certain of this.
I have seen a couple of cases running Linux but most users were NAS
Hey Guys
Just hit this issue on my Synology NAS after updating to 1.13.9.5456. Uninstalled and went back to 1.13.8.5395 and same issue. I didnāt have this before. Anyway to fix it till new version comes out? 1.13.8 was working fine for me before.
Anyone has older version I can install ? or any other way to fix it?
I probably do as 1.13.8 and 1.13.9 didnāt work for me
PMS 1.13.4.5271 X86_64 Synology.
https://drive.google.com/open?id=1bHDRz0IBDDSRs3jEv6Kchwl5GUZq7pfN
1 Like
Did you establish if this gets round the problem:
- Setup Port Forward in the router and ensure IP of PMS DHCP Reservered
- Select Manually Specify Port and enter the public port in the port forward
- Disable uPnP in the router
Hoping that would make the router return immediately to the server with an error instead of server being locked out whilst waiting for
a response
I know, I have always been configured with these settings. Even tried a different router.
Still the lockout occurs only on Synology versions past 1.13.4. While it is transient I can eventually replicate it every time on those versions (with external access enabled)
So looking at wireshark captures I can clearly see different TLS versions being used between versions when trying to connect out to a relay server. *while looking at the Synology versions
In plex server 1.13.4 every connection is using TLSv1.2.
In plex server 1.13.9 all local connection are TLSv1.2 but external connections dropped down to TLSv1. I can clearly see my client browser connecting to plex relay in this case (172.104.211.98, pubsub13.pop.ewr.plex.bz) After a few exchanges I was kicked to a second relay server (96.126.104.168, relay07.pop.ewr.plex.bz) and then never received another response.
This is totally unrelated to the issue that was seen in the original investigated evidence. The problem that was identified was lockouts whilst communicating with the router and when the router takes more than 15 seconds to respond, we get the clients timing out. This cause of this has been identified and a fix will be released.
What you are describing now sounds like a potentially different issue, which I would be happy to look into if it is causing an issue - but i would need to see evidence of the impact and the diagnostics and of course logs
I was using wireshark to try and capture when the lockout was occurring. I just happened to notice the TLS version differences (which may not be a big deal). I figured that it was related which is why I pointed it out. The point at which I didnāt get a response back from the relay just so happened to be the point where my client lost connection to the server so you could see where I might make that connection.
Sounds like itās a non issue then. I will just wait for the fix to roll out.
I would like to offer a development build to a few users to try and confirm the fix, please let me know the package you need - you can give me the platform and also indication as to which of the downloads files on https://plex.tv/downloads you would use
I am using the Synology build, 1.13.9.5456-ecd600442 (64bit) version.
Private Message sent with download link
