Server Version#:1.13.6.5339 & 1.13.5.5332
I have a synology NAS DS416j. Been using plex for a long time. The last working version is 1.13.4.5271.
After a perform an upgrade to version 1.13.6.5339 or 1.13.5.5332 server is not able to start anymore and url
http://X.X.X.X:32400/web/index.html
times out
Whats different with the last two versions. How can I resolve it?
Thanks trumpy81 for the log dive. Interestingly I do have the IP setup as static. For most of my boxes in network I setup static. So definitely the nas during should have the proper value assigned.
From glancing at the logs my self I get the impression that there may not be enough logging especially around the area where the problem occurs. Not sure if there is some dependency either local store (db migration from version to version) or network related that may be triggering an error. Then when the server starts it may not find everything in place and fails to start.
I have noticed two ways the problem manifests. After a few reboot trials:
a) sometimes the URL http://Your-NAS-IP:32400/web is completely unresponsive and times out
b) it starts up but there is no server available. I get a drop down with the plex server that is dimmed out and has a error sign on the side.
wow !! this worked. Went through some ups and downs and had to repeat the process (I think because I started it from version 1.13.4.5271 and server claiming was not there.
Went to latest version did that again and had one more glitch. It asked to claim the server but then after a few seconds it skipped because i didnt claim in time and redirected to setup. During setup it did not reuse my library folders so I reset and started over again. This time it reused my folders, asked to claim and got me to the home screen with all working.
Thanks trympy81 !! something seems to have changed with server registration version over version. Now I have a few inactive servers in my account with same name but I can go back and delete them. Wanna make sure that it will be stable in the next days and the config sticks so I dont have to rebuild library.
Awesome !
Oh man this is killing me. Whatever was introduced after 1.13.5.5332 is kicking my ars at this point. I have ended up doing this process a “few” times by now. After resetting the preferences it lights up momentarily and I can see my library. After a few minutes though the server becomes once again unresponsive and I have to do this all over again.
I have to revert back to version 1.13.4.5271 hopefully not forever at this point.
May I have the logs, manually collected via file station using
Logs
Compress to Logs.zipI think I was able to reproduce this a bunch of times.
Let me point out the steps I went through.
I noticed my library had a bunch of movies duplicated. I am assuming this happened during a migration process since it was not existing before. The duplicate entries were not corresponding to a valid video file. Clicking to play them would trigger the bug in fact.
After selecting and clicking the shadow duplicate movie entries, the server would become unresponsive. At this point no normal operation would revive the server. I went ahead and manually stopped and started it without resolution. No matter what I did the server would not respond again and the page http://Your-NAS-IP:32400/web would result in showing my server unavailable.
I can only assume that some crash would leave the preference and pid file in an unpredictable state? Since deleting them would give me another life.
Let me also point out that in my multiple retries I noticed a weird situation. When I was navigating back to Plex/Library/Application Support/Plex Media Server sometimes the pid file was there, while other times not. Could not explain that.
Delete once again the preference and pid file (when latter was available) I would get another chance to revive the server and claim it. Then it would respond again. Until I once again play something (one of the invalid duplicate library entries) that would once again put it in the unresponsive state.
I went ahead and deleted the duplicate invalid library entries. After that I was able to play a few moves without noticing the unresponsive state behavior again.
Not sure if all this makes sense or rings a bell. I will keep an open eye in the event I notice another reproducible way to get it in the undefined state. Will also collect some logs as well tomorrow. Set the server in verbose mode?
Please do not set the server to Verbose mode.
It is only useful in the most finite of cases. It generates 50x more output than is needed (literally). As a result, it will hold 1-2 minutes of elapsed time making it pointless for general, first pass debugging.
As for the duplicates,
You should see the invalid files now disappearing
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
