Ever since I downloaded PMS 1.9.5.4339-46276db8d I have had issues with it becoming unresponsive and having to close PMS and restart it. I’ve also restated the computer. I am using Windows Server 2016 and haven’t had an issue until now.
Logs: https://drive.google.com/file/d/0B43jcZHbJGXQYnRldk9TekdaQ2M/view?usp=sharing
Any help is much appreciated.
same… on WD NAS ex4100 same symptoms. IT is software related obviously, not hardware related.
@VodoBaas1 said:
Ever since I downloaded PMS 1.9.5.4339-46276db8d I have had issues with it becoming unresponsive and having to close PMS and restart it. I’ve also restated the computer. I am using Windows Server 2016 and haven’t had an issue until now.Logs: https://drive.google.com/file/d/0B43jcZHbJGXQYnRldk9TekdaQ2M/view?usp=sharing
Any help is much appreciated.
The logs show some database lockout whilst the photos library was being scanned. I have passed the logs to the development team. I will let you know if we need more info / diagnostics.
@VodoBaas1 said:
Ever since I downloaded PMS 1.9.5.4339-46276db8d I have had issues with it becoming unresponsive and having to close PMS and restart it. I’ve also restated the computer. I am using Windows Server 2016 and haven’t had an issue until now.Logs: https://drive.google.com/file/d/0B43jcZHbJGXQYnRldk9TekdaQ2M/view?usp=sharing
Any help is much appreciated.
Could you download a copy of your Plex Media Server database (Settings / Server / Help / Download Database) and send me the zip by Private Message. We have been looking at a lockout that may have been caused by duplicate paths and would like to check that
Same here.
it says “503 Service Unavailable” when i try to access my plex server
same exact issue fyi… also on win 2016 essentials.
@sa2000 - just sent link to zipped db via PM.
@mtsdawson said:
same exact issue fyi… also on win 2016 essentials.@sa2000 - just sent link to zipped db via PM.
I only need the database if when investigating the problem from the logs I see a database issue
First line of investigation is logs with debug logging enabled for time of problem
From the logs analysis a decision is made in whether a process dump plus logs needed or a copy of the database
@mtsdawson said:
same exact issue fyi… also on win 2016 essentials.@sa2000 - just sent link to zipped db via PM.
@sa2000 said:
@mtsdawson said:
same exact issue fyi… also on win 2016 essentials.@sa2000 - just sent link to zipped db via PM.
I only need the database if when investigating the problem from the logs I see a database issue
First line of investigation is logs with debug logging enabled for time of problem
From the logs analysis a decision is made in whether a process dump plus logs needed or a copy of the database
Please enable Debug Logging on the server. You had disabled debug logging
See https://support.plex.tv/hc/en-us/articles/201643703-Reporting-issues-with-Plex-Media-Server
and then restart the server
and on next lockout - note down the time of the lockout and then get the logs and attach with info giving time when the lockout arose
https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files
@smounche said:
Same here.
it says “503 Service Unavailable” when i try to access my plex server
If a deadlock arises, then requests will hang and after a while as the number of queued requests reaches a very high level, requests would get rejected with error 503
It is possible that the issue is that which was reported in this forum topic
http://forums.plex.tv/discussion/291861/server-crashes-after-60-min-of-live-stream
A fix will be released for that soon.
If it is a deadlock, it would only be possible to confirm if it is the same issue if server logs and a process dump is obtained - as can be seen in that forum topic
I have 2 servers running the same PMS version 1.9.5.4339. One is on Win10Prox64 (1703). The other is on Windows Home Server 2011 (aka Server 2008R2). The Server running on Windows Home Server 2011 has this problem, but the one on Win10 does not.
Right now server is barely up… it connects but nothing loads. Waiting for it to go fully offline to capture 503 in the logs, then sending them over.
Yep it’s down again. @sa2000. Just sent you both logs, now with debugging enabled.
@mtsdawson said:
Right now server is barely up… it connects but nothing loads. Waiting for it to go fully offline to capture 503 in the logs, then sending them over.
@mtsdawson said:
Yep it’s down again. @sa2000. Just sent you both logs, now with debugging enabled.
Thanks for the logs - I understand the lockout was between 23:15 and 23:45 on 21 October
You actually had two instances of Plex Media Server.exe running
One as a Service launched at Oct 21, 2017 20:37:57 and that was still running when you for some reason launched Plex Media Server.exe outside the service manually at 22:41
So between 22:41 and the time you had the lockout - you had 2 instances of Plex Media Server.exe running at the same time and of course this would lead to database lockouts and other indeterminate outcomes
Oct 21, 2017 20:37:57.173 [19224] INFO - Plex Media Server v1.9.5.4339-46276db8d - Microsoft PC x64 - build: windows-i386 english - GMT -04:00
Oct 21, 2017 20:37:57.173 [19224] INFO - Windows version: 10.0 (Build 14393), language en-US
Oct 21, 2017 20:37:57.173 [19224] INFO - 8 2494 MHz processor(s): Architecture=0, Level=6, Revision=14857 Processor Identifier=Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
Oct 21, 2017 20:37:57.173 [19224] DEBUG - "C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe" -noninteractive
Oct 21, 2017 20:37:57.532 [18588] INFO - Starting in noninteractive mode
and
Oct 21, 2017 22:41:42.364 [19048] INFO - Plex Media Server v1.9.5.4339-46276db8d - Microsoft PC x64 - build: windows-i386 english - GMT -04:00
Oct 21, 2017 22:41:42.364 [19048] INFO - Windows version: 10.0 (Build 14393), language en-US
Oct 21, 2017 22:41:42.364 [19048] INFO - 8 2494 MHz processor(s): Architecture=0, Level=6, Revision=14857 Processor Identifier=Intel64 Family 6 Model 58 Stepping 9, GenuineIntel
Oct 21, 2017 22:41:42.364 [19048] DEBUG - "C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Server.exe"
and loads of these errors because of the double instances of Plex Media Server.exe running
Oct 21, 2017 22:41:48.645 [8216] WARN - Waited one whole second for a busy database.
Oct 21, 2017 22:41:50.208 [8216] ERROR - Failed to begin transaction (..\Plugins\PluginDatabaseState.cpp:112) (tries=1): Cannot begin transaction. database is locked
Oct 21, 2017 22:41:51.827 [8216] WARN - Waited one whole second for a busy database.
Oct 21, 2017 22:41:52.926 [8216] ERROR - Failed to begin transaction (..\Plugins\PluginDatabaseState.cpp:112) (tries=2): Cannot begin transaction. database is locked
This is a result of trying to get Plex back online. When the original lockout happened, I must’ve tried to restart Plex by stopping the service, waiting, then relaunching the service. This routine works to get Plex back up and running for an hour or two. So it appears the original instance never fully shuts down.
So bottom line, sure, running two instances of Plex can result in a lockout. But the original issue remains.
I’ve rebooted the server so we can ensure only one instance is running. When it fails, and it will, I’ll forward the new logs (PRIOR to restarting the service).
I believe I just figured out the issue. For WinServers to auto-launch Plex at boot, in the past we’ve had to install this third-party tool: PmsService (https://github.com/cjmurph/PmsService/releases). It appears this is no longer needed as Plex now has it’s own service built-in and is able to auto launch at boot. I’ve had this tool installed on my Plex servers for years and it never presented a conflict… but I’m guessing it now does with the latest beta build. Now that the feature is integrated, Plex launches it’s own instance of the service at boot and this tool launches a second, eventually leading to the lockout. I don’t believe the tool was needed for Win10, which would explain why @DamnedOne doesn’t have the issue w/ his Win10 machine.
Bottom line, if you have PMServices (PlexService_1.1.2.msi) installed, uninstall it.
Also, I’ve downgraded to Plex-Media-Server-1.9.4.4325-1bf240a65.exe, so unable to provide further logs. Thanks for previous guidance here.
No
There is no built-in service capability within Plex Media Server
However there was always auto launch on start / login
I am out on mobile now - will answer fully later
@mtsdawson said:
Also, I’ve downgraded to Plex-Media-Server-1.9.4.4325-1bf240a65.exe, so unable to provide further logs. Thanks for previous guidance here.
I do not need any more logs. The logs already provided were conclusive
@mtsdawson said:
I believe I just figured out the issue. For WinServers to auto-launch Plex at boot, in the past we’ve had to install this third-party tool: PmsService (Releases · cjmurph/PmsService · GitHub). It appears this is no longer needed as Plex now has it’s own service built-in and is able to auto launch at boot.
Plex Media Server does not auto launch on boot as a service. It has the option to auto launch as a user process on stratup for the current windows user account. That was always there as an option and it is the default option when you install Plex Media Server or update Plex Media Server. If you boot up the PC without logging in to any windows account then it would not launch. Hence the need for third party product such as the cjmurph PmsService wrapper which allows plex media server to run even when not signed in to a windows user account
When running PMS As a Service you must not make use of the auto update built-in feature for Plex Media Server and you should always do the updates manually and ensuring it does not auto-launch after the update/install. You would use the Plex As Service Service Tray app to start / stop Plex Media Server - ensuring it is stopped before doing any manual updates
So my advice is the opposite to what you are suggesting - unless you do not need the benefits of it running as a service
So if you wish for it to run as a service
Ask Me and is not automaticIf the same windows user account is used for install and running Plex Media Server as a service then the PmsService should itself disable the automatic start of Plex Media Server on start
If you do not wish to run it as a service, then uninstall PmsService wrapper and just use the default mechanisms for updates and auto start on windows user session start
With the regards to the evidence that you provided, there was no evidence of a reboot at 22:41 when Plex Media Server.exe got launched outside the service. But may be you logged out and logged in to the windows user account and that triggered the auto start.
May be it was the way you did the update that bypassed the Plex PmsService mechanism to disable the auto start on login. I always make it the auto start is disabled - but my environment is more complicated in that i have different windows account for install/updates than the one the service runs in
I don’t have the 3rd Party Plex as a Service installed on either of my systems. What I find is that PMS stops responding to requests. The program is still running. If you exit the program from the systray icon, the program does not actually close. You have to go into task manager and kill all the Plex processes that are running, then restart the program again. It will then successfully start and work okay for a while.
@DamnedOne said:
I don’t have the 3rd Party Plex as a Service installed on either of my systems.
There is nothing wrong with having Plex as a Service wrapper app
The issue in the posts above is one specific case of database locks because of multiple instances of Plex Media Server processes running.
@DamnedOne said:
What I find is that PMS stops responding to requests. The program is still running. If you exit the program from the systray icon, the program does not actually close. You have to go into task manager and kill all the Plex processes that are running, then restart the program again. It will then successfully start and work okay for a while.
This could be a deadlock. The appropriate post to you in this thread is the one that shows what initial diagnostics are needed. See these posts
http://forums.plex.tv/discussion/comment/1542016/#Comment_1542016
http://forums.plex.tv/discussion/comment/1542027/#Comment_1542027
Each case needs to be investigated to see what is causing the problem
@sa2000 - Thanks for the detail in your reply. However, now that we’ve isolated the correct procedure for PmsService… I have to say I agree with @DamnedOne. My previous troubleshooting included a few scenarios that actually adhere to your guidance and yet PMS still stopped responding. Truth be said, I think my previous comments re: PmsService are likely getting in the way of troubleshooting the bug with this beta build… but I’ll defer to the experts here.
Again, thanks again for the book-ended guidance re: PmsService - very helpful!
