Problems with versions after 1.13.3.5223

Plex Media Server NAS & Devices
1

Hi,

I seem to be having some issues with any version of PMS after 1.13.3.5223. (I have just tried both 1.13.4.5251 and 1.13.5.5291)

Sometimes it will not load at all, sometimes it connects but as indirect, but it is just generally very unreliable and inconsistent in it’s behaviour. I know, always fun when trying to find a problem.

I see log messages that seem to suggest it is losing network connectivity (but i still see that message with v1.13.3.5223 so that may not be relevant).

The specific line is:

Jul 26, 2018 16:38:57.772 [0x7fa1833ff700] DEBUG - MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.

If I ssh to the nas and run ping in a shell that shows no packet loss which (to me at least) indicates no loss of connectivity on the actual nas itself.

I am running the latest DSM (more fool me) and I have always run the 64 Bit version of PMS

If I uninstall the newer versions of PMS and reinstall 1.13.3.5223 then it quickly comes back to life.

I don’t think it would be permissions, the plex user still appears to have permissions on the media folders, and if it was permissions then I would have thought this should affect the 1.13.3.5223 version in the same way.

And yeah I know what’s coming next, can we have some logs…

I am currently using version 1.13.3.5223 and refreshing metadata on a reasonably large Movie library, so once that is done I will look to trying an update again and then collecting some logs (but it may be a little while).

But at the moment my feeling is if it ain’t broke don’t fix it and I might just stick with 1.13.3.5223 for now.

3

Thanks for the reply.

I did try 1.13.5, that was when I first had/noticed the issue, and started rolling back.

I did try rebooting stuff, but that did not seem to make any difference.

fwiw, I am not having any issues with the PMS running on my Mac on the same ethernet network, and that is running 1.13.5

5

Thanks,

I rebooted the nas (again) and changed a synocommunity package to a docker container instead, and it seems to have settled down.

When I managed to get access to the server settings. I set the network interface to the ipaddress of the nas (that is a 4 port bonded connection using LACP)

I am still not sure where the problem is/was but I am leaning towards something new in the latest DSM

Will keep an eye on it and see how it goes.

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.