That indicates that you didn’t repair the database.
Starting with Plex server versions greater than 1.23.2 you need to follow the linked directions because they embedded sqlite into the Plex executable along with language dependencies. Plex even included a one line repair "C:\Program Files (x86)\Plex\Plex Media Server\Plex SQLite.exe" com.plexapp.plugins.library.db ".output recover.out" ".recover"
Since you have a WD NAS you will have to do a little legwork to find the location of the Plex binaries to translate the above example into something usable.
Thanks for your help so far. I think i tracked down the right file though i’m not super sure as it didn’t appear to do much. I ran the integrity check and got an “ok” back. Then I went through with the one line repair command and received the response below as I took off the .output recover.out part.
This happened again to me as well. Since my last post I updated the Hauppauge WinTV driver using the WinTV software installs. Tip: You don’t need a WinTV activation code to run the install just for drivers. I had my system not record any shows and there was no problem using the tuner occasionally (just to test). I then added shows to record. This went fine for a few days until the DVR once again disappeared. I am now wondering if the problem is my tuner is overheating when recording shows for long periods. I’m going to look into getting heat sinks installed.
Does anyone knowledgeable about the code know if the DVR can become corrupt if the tuner becomes non responsive due to overheating?
You have 2 instances of Plex Media Server .exe running in parallel and both referencing the E:\MediaCenter\Plex Media Server data area
One is running as a service and has debug logging enabled
and the other instant must be running in a different windows user account as it has debug logging disabled and must be referenceing a different user registry area for the settings
Anyway - two instances of Plex Media Server accessing the same sqlite3 databases would lead to issues
How do you update Plex Media Server when you are running as a service ?
Have you seen my post here PMS as a service - #4 by sa2000 about registry change after updates to ensure it does not start in the windows account you use for updating Plex Media Server?
Do you use SYSTEM account for the PMS Service ? I would not advise this - if you are doing this
Thanks @sa2000. I have no idea why the 2nd instance would be running. I’ve had it set up like this for years. Thanks for spotting that though. I may go with your approach and just delete the registry key to be 100% certain that doesn’t happen again.
And for install, I stop the service, install, then restart the service. I don’t click Launch after the install is done.
Ah, that’s the issue. Thanks. I do see the key in the registry now. So that key: ( HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\Plex Media Server) tells it to automatically start when logging in, causing a dual server instance?
No, not under SYSTEM or account I login with. It must have been the first issue where it’s getting pre-selected after a PMS update. Although I’m not logging in with the same account so that’s a bit odd.
It gets set to auto run for the user account doing the install
if the service is using a different account then you must delete the registry setting for the account doing the install
KEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run\Plex Media Server
If it is the same user account for installs and for the service then I thought the @cjmurph Plex Service package handles that and removes the auto launch - are you using his latest package ? PMS as a service
I have looked at your logs and the corruption was due to you running 2 instances of Plex Media Server.exe at the same time - one as PMS As Service and one auto launched on windows session login
See these overlapping times
Auto Launched on Login
May 07, 2021 01:01:07.390 to May 07, 2021 04:59:46.441
May 07, 2021 07:22:02.100 to May 07, 2021 16:59:33.258
May 07, 2021 21:39:53.167 to May 07, 2021 21:50:17.906
Running as PMS As Windows Service
May 07, 2021 02:46:27.614 to May 07, 2021 05:00:14.934
May 07, 2021 05:01:26.508 to May 07, 2021 17:00:15.748
May 07, 2021 17:01:24.606 to May 07, 2021 21:50:32.895
See my responses to @mbarylskihere and the following dialogue - this is relevant to you as well
I’m counting my issues as resolved now. Been running without DVR corruption for over a week. I believe I had two issues.
Tuner becomes too hot if used for long periods for recordings/viewings. I fixed this by installing heatsinks to the chips on my tuner.
I have Plex running as a service when Windows starts and also had Plex checked to start on login. This resulted in two instances running. I fixed this by unchecking the option to start on login. Thanks, @sa2000!
I am summarizing here the results of my investigations into these issues
EPG db corruptions and lockouts caused by running multiple instances of Plex Media Server.exe on Windows (as service/scheduled task as well as auto-launched)
Plex Tuner Service process crashes and tcp port 32600 not released following restart of the Plex Tuner Service - seen from users with Hauppauge WinTV DVRs - this is still with the Plex Media Server development team
Bug in boost affecting ARM based systems leading to failure to setup DVR / refresh EPG - resolved in PMS 1.24.4.5081-e362dc1ee
Problem where DVR is not being detected - this is to be investigated by the development team from diagnostics provided by @bryanbar
If anyone else having the issue reported by @bryanbar - I would like to see server debug logs and Plex Web DVR setup screenshot (noting down time of the screenshot / issue) and download zip of the main Plex Media Server db plus responses to specific http requests responses collected at the time of the problem:
curl -X POST -o dvr-devices_yyyymmdd_hhmm.xml http://local-ip-of-PMS:32400/media/grabbers/devices/discover?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxxxx
curl -o dvrs_yyyymmdd_hhmm.xml http://local-ip-of-PMS:32400/livetv/dvrs?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxxxx
For HD Homerun DVRs - please also get the responses to these
substitute date/time for yyyymmdd_hhmm in the output filename and instead of xxxxxxxxxx put in the server security token - see this support article for how to find the token string, The files will be created in the current directory for the command line session
also the local IP of Plex Media Server and local IP of the networked DVR in above requests as apporpriate
I saw where they said that you had a second instance running. I had been using a task to launch plex at start up. I have deleted that and I will see if that helps
Thanks again.