After around 7 months of failed upgrade attempts to v1.18.x the changes coming in on Jan 31 have left me lost on where to turn. In another thread this same problem has been happening with users with huge audio collections (just like me) where the Plex database became corrupted. Plex published a document on using SQL Lite Tools to fix. However the article only covers standard Mac, Windows & Linux installs leaving me with no idea how to address this issue since I’m running Plex on a Synology NAS? The same thread mentions that Plex Team has found the issue and will be sending an update soon. The question is though, will this update be released through the Public or Beta channels and will it be released before Jan 31.?
All I can say is that a new version of 1.18 that actually works and fixed all the problems I had is actually about to be released. I am running an Alpha of it now and it was based off the most recent Beta version. So my guess is that the next version of 1.18 will solve it so if I were you, just hang tight on 1.17 until then. You may have a few days when you can’t add new TV shows but be patient.
3 Likes
This fixed my problem described here: Plex server suddenly won't connect, even on host machine
Thanks everyone!
Plex Media Server 1.18.6.2348 is now out as beta
It has the changes for speeding up server database transactions that were causing timeouts and failure of Plex client apps connecting to the server - seen on servers with many libraries.
- (Performance) Speed up connectivity tests and library discovery (#10930)
See release note for other changes
Early days, but appears to have fixed the problem. When I first upgraded to 1.18.6.2348 even though Plex showed as running on my Synology I was unable to connect to the web interface. I tried another device and could at least see Plex supplied 3rd Party content but no access to my local libraries. I figured it may still be updating the database for local content. Sure enough about 30 minutes later my local library became available in Plex as well. Since then I’ve done minor testing but I was able to access every item on Plex, have played both audio & video content, added new content and updated library without problems & can access Admin interface. One funny issue was after the upgrade I found that permissions to access my Plex folder on my NAS using Synology’s File Station had changed and I had no access. Simply changing the permissions for the Admin Group and & for the Admin account to have read/write access to the Plex folder (as it had been prior to the upgrade) brought it back.
Thanks for replying letting us know.
I have upgraded to 1.18.6.2368 beta and still running into unreachable issues multiple times per day (more so during busy hours). I assumed I was having the same issues as OP due to a large library size.
Is there something I should look for specifically when combing the logs? I can send you logs via PM if you wish.
There are further fixes coming along following further investigations with diagnostics from @tramp78 - but these relate to scanning / creating large music libraries.
I need to see server logs of your issue initially.
Im getting the plex is not reachable error as well. Is there a way around the issue?
Hi philmbiz,
not sure if an update is what is causing me being unable to connect to Plex any longer (a few days now) but our entire movie collection is on there so would like to get it up again. Is there an easy and safe way to go to the previous version of Plex (v.1.17)?
If I follow those database repair instructions you have (as best I can) I won’t lose my movie collection as far as you know?
Well I just updated to the latest and now can’t get into the server … However it does hook-up with a server that no longer exists (for 40 days…and sever re-boots later). Needless to say I will not be upgrading again until I have seen nothing but good reviews. Last week was a disaster when I re-installed the server because I was UNAWARE that your servers were down. Now this. How do I get my server to come up and not the old one … Have added much to in the last couple of days that does not show-up in the old server. This is a ubuntu setup and I am more accustomed to windows but if you furnish command line stuff I can deal with it. Thx.
I sent the logs to you via PM - were you able to find any issues?
I can supply more logs or anything else if you require it, thanks!
@sa2000 Do you have an update?
Improvements to some database requests have already been released and the current beta has all fixes to investigated slow transactions that were leading to client apps timing out (Beta 1.18.8.2468-5d395aa9d)
The logs from @MapleEh show some form of deadlock leading to build up of requests and timeouts. I will respond to that in a separate post
So my advice is to use the current beta and if there are problems, note down the time and gather logs and attach here with details. Make sure debug logging was enabled before launching Plex Media Server so logs can show start up sequence as well (where problem happens soon after)
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Logs showed build up of requests and long delays before requests were dealt with. The build up could be due to a deadlock - where one thread may hang and blocking other threads
See this post for what diagnostics would help in investigation of deadlocks
Basically - in addition to logs, we need the connections list and a process dump. If crash reporting is enabled the dmp produced by “kill -SEGV ” for the plexmediaserver pid should get uploaded on subsequent restart, If not, it would be kept in the Crash Reports directory and would be attempted again on next restart
But please run on latest beta
Don’t know if this relates to you or not. I was going literally mad trying to fix my red …no remote access on Plex. It was working fine for quite some time. Comcast installed extra security called xFi I believe early Jan 2020. I found by going on their website under support I was able to disable it. Bam. It worked. I am all green for a couple of weeks now. I have skipped the past two updates figuring they may break remote access. Running fine without xFi turned on. Am I missing anything
We have added a section about XFINITY xFi Advanced Security recently to this article https://support.plex.tv/articles/200931138-troubleshooting-remote-access/
1 Like
Music Library Scan issue - Windows 10
Following any modifications on existing files’ tags already part of the database cause duplicate entries on subsequent scan. Similar behaviours occur when renaming folders. In addition, old entries are not removed from the database.
This Issue has been observed on any 1.18.x release, including 1.18.9
Proceeding with the rollback to 1.17 always fixe the issue following a library scan. All duplicate entries are removed.
Can’t see the relevance of this to “updates cause server unreachable/unavailable” - the title of the topic
If you care to raise a new topic with evidence of the problem:
directory listings, what was added, what the outcome was and debug logs covering the time when the issue arose - I will look into it. I might also need copy of the database (zipped download)
Please post in this thread providing a link to your forum topic for the issue you are describing.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
