Starting on this procedure. But to answer your question - this is Synology DS414 - running DSM 6.2.4 (up to date).
just completed the procedure. There were two databases to rename. I did both. I tried to rollback to the database from 7/28 when the DVR was still present. I am the same position. The DVR is gone and my HDHomerun tuner is not being found.
This is what I see -
I have a couple of other databases I could try to use but the tuner was showing correctly on 7/28.
I should of linked these directions: Restore a Database Backed Up via 'Scheduled Tasks' | Plex Support
If you restored a database from before you removed it then the tuner should be present.
I hesitate to send you down the Repair a Corrupted Database | Plex Support or to suggest removing all the db files and starting over as this is getting pretty deep.
I followed the procedure per the linked instructions. This was a bit different than what I did before.
Unfortunately I am still in the same situation. There is no tuner found at least not in UI. The screen shots of what I see are exactly the same as previous message. The log does indicate that tuner was found somewhere along the line so there seems to be disconnect.
this is from the log today after restart and the same thing was in log I sent earlier.
I am trying to make sense of the errors in the log - not easy - Here are the first 5 after just a few minutes. Any help in these?
at 337 Aug 05, 2021 08:36:04.505 [0x2f558d48] ERROR - getaddrinfo(192-168-1-37.abcdefghijklmnopqrstuvwxyz012345.plex.direct) failed: -2
at 386 Aug 05, 2021 08:36:06.319 [0x2e5b2d48] ERROR - Error issuing curl_easy_perform(handle): 28 *This error occurred several times - I won’t repeat.
at 418 Aug 05, 2021 08:36:06.540 [0x2fd07d48] ERROR - SQLITE3:(nil), 1, no such table: schema_migrations in “select version from schema_migrations order by version”
at 421 Aug 05, 2021 08:36:06.602 [0x2fd07d48] ERROR - Thread: Uncaught exception running async task which was spawned by thread 0x2f558d48: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version
at 458 Aug 05, 2021 08:36:06.602 [0x2fd07d48] ERROR - Thread: Uncaught exception running async task which was spawned by thread 0x2f558d48: sqlite3_statement_backend::prepare: no such table: schema_migrations for SQL: select version from schema_migrations order by version
at 506 Aug 05, 2021 08:36:10.258 [0x2e63bd48] ERROR - [EventSourceClient/pubsub] getaddrinfo(192-168-1-37.abcdefghijklmnopqrstuvwxyz012345.plex.direct) failed: -2
at 507 Aug 05, 2021 08:36:10.258 [0x2e63bd48] DEBUG - [EventSourceClient/pubsub] Network: 192-168-1-37.abcdefghijklmnopqrstuvwxyz012345.plex.direct failed to resolve to 192.168.1.37 but instead yielded “”
What do you think next step should be?
I would first roll back to the above serve version, if that doesn’t work then the database repair. The messages indicate that it is trying up upgrade the database schema and hanging.
I didn’t mention it before because it is not really a cause of your problem but you have two ethernet ports defined, you should turn one off.
Network interfaces:
Jul 30, 2021 07:34:26.215 [0x2b652e70] DEBUG - * 1 lo (127.0.0.1) (loopback: 1)
Jul 30, 2021 07:34:26.215 [0x2b652e70] DEBUG - * 2 eth0 (192.168.1.37) (loopback: 0)
Jul 30, 2021 07:34:26.215 [0x2b652e70] DEBUG - * 3 eth1 (192.168.1.38) (loopback: 0)
It seems I will have to uninstall in order to install an older version.
So should I still proceed?
Does this change the steps I should take? perhaps delete some other databases.
What will I lose? not the end of the world but nice to know in advance.
Does this change the version I should try to roll back to?
Thanks.
Yes the uninstall is like asking you are you sure you want to do this.
Using the older version will match the database and should allow it to start up.
Other course of action is to remove the database files and let Plex Server reinitialize. Going this route you may have to reclaim the server.
Did the reinstall to .4805. I am still in same position - can’t find the tuner (at least not show it in the UI). Seems like something is whacked out.
Shutdown Plex and move the DB files somewhere else, start Plex and let it re-initialize and see if you can then add the DVR.
Tiebierius, thank you for the help.
I am glad to report that the Plex server is back on line, with tuner, and guide data updating normally.
I did end up taking the drastic route of deleting the data bases and the app, then reinstalling an older version of the app. This was not actually smooth. I got some error messages along the way that indicated fatal errors but they seemed to be false alarms.
Some things I learned along the way.
- There are instructions for deleting the data bases, and they go beyond the data base folder. I had to delete the Plex Media Server Folder.
- I ended up with a new name for my Plex Media server. Not sure if this was good or bad or neutral. but I had failed to note the name before deleting it. This led to some fiddling at the UI side but not a major issue.
- I lost my recording schedule after all this was complete. Not the end of the world but it is an annoyance. I probably needed to do some cleaning anyway.
- I am left uncertain about when to upgrade the server or steps I should take avoid all the problems I experienced. I’m normally a believer in keeping software up to date. If you or anyone has tips on this last point I’d love to hear them.
Thanks again.
Unfortunate that you had to resort to the most drastic action.
If you have a Android or Iphone enable push notifications on the server (Plex Server restart required) and on the phone app enable database backup and database corruption notifications. If corruption occurs you will catch it much sooner if the backup doesn’t occur every 3 days.
Set your server to only notify you of non-beta releases. Always wait a few days after a release to search the forum for that version to see if people are reporting problems with the upgrade for the OS you are using. Many of the upgrades are modifying the database so that is when most problems are introduced. If a database backup doesn’t occur within 3 days then you know to stop and repair database or restore an older backup.
I have been having the exact same issue as original poster. its been spinning for weeks!!!
I have upgraded the PMS .bin flle multiple times since it started happening (with no changes or improvements).
I dont actually need Guide Data for that Server as I only stream my music on my WDMyCloudEX2 Ultra server. Any TV/VIdeo stuff is done on my other PMS server on my NVIDIAShield, so I even tried to remove the OTA Tuner and delete the “MOVIES” and “TV SHOWS” menu selections hoping that would work since I only want Music on that one server but that didnt help either.
Im worrried its putting a daily resourcea and HDD strain on my NAS Drives or Server if it cant update the Guide.
I have turned OFF the Plex app inside of my NAS UI setting multiple times as well and had the NAS shut down but every time I power it back up Plex shows its still spinning and no changes to get from 0% to anything else
NOTE: MY Music server is my MOST important PMS and I will NOT start over on that one as I have spent MONTHS working on ripping all my THOUSANDS of CDs and setting it all up so thats not an option to start clean
Current System:
PMS Server: WD MyCloudEX2 Ultra
PMS Version : 1.24.3.5033
NAS Firmware v er: 2.41.116 (OS3 type)
NAS Type: RAID 1
Drive Size : 2x - 10 TB Red HDDs (mirrored) by Western Digital
with 9 TB free
OTA Tuner - HD HomeRun Duo
My other PMS Server on my NVIDIA SHield does NOT have this issue and I am able to watch my OTA Tuner and record TV just fine and get updated Guide Data. It is Not constantly spinning so either the issuee is with the WDMYCloudEX2 Ultra .bin file or else on the Plex side.
CPU strain seems to be normal (see images below) but there was one day when my CPU for that PMS Server was over 300%!!! dont know why
Also to note:Hitting the “Cancel Guide Update” X button doesnt seem to do anything to resolve this either.
It just spins for a while and then goes back to trying to refresh the guide
Please advise
NOTE: I am also getting an EMPTY 22 kb Server Logs zip file when I try to download them!
thanks
https://support.plex.tv/articles/202915258-where-is-the-plex-media-server-data-directory-located/
While the newer HDHomeruns are more forgiving you should only have one Plex server configured with the DVR to prevent conflicts over controlling it.
Deleting the EPG database should take care of the 0% stuck refreshing but I would verify that the main com.plexapp.plugins.library.db is being backed up by scheduled tasks every 3 days.
1 Like
Thanks for the reply. I will have to look into this and get back to you. Looks complicated. If I delete the DVR then I will lose all recorded shows no?
If so will need to finish watching those before I do this correct?
How do I make sure only 1 server is set to the DVR (which is what I want, the NVIDIA Shield server, since it CAN transcode video, and DONT want my WD MyCloudEX2 Ultra to be tied to anything video /DVR related, as I only stream my Music FLAC library from that Server) … ?
Thanks
You simply don’t set up a DVR on that server.
When you enter the server settings, take a look at the left side bar.
If you have more than one server in your account, there will be a drop-down selector which you use to select the server to configure.
Make sure your NAS is selected there, then enter the “Live TV & DVR” section (near the bottom) of the side bar.
Make sure there is no tuner present in there.
You can switch servers back and forth and compare the content of the “Live TV & DVR” menu item between the servers.
1 Like
ok thats what I thought just wanted to be sure.
Yeah I think when I originally setup my Plex account I had setup the DVR on the NAS not knowing that it couldnt transcode/do video and then I bought the NVIDIA Shield and the HDHomeRun for the TV/video stuff after and set up the DVR for that but I think the DVR was still on the original NAS server (which is only used for my music).
Wish there was a quick way to just hit a button or go into a setting to STOP guide refresh on a selected server 
Ok its fixed
When I went to the server I noticed it wasnt spinning anymore for the Guide Update.
So something happened without my intervention behind the scenes somehow?
Anyways I went to my Music only server NAS and deleted the tuner and removed the Live TV and DVR from that server.
See attached screen caps showing the new servers and the dashboard with no spinning circle anymore
Hurray!!!
Not sure what happened bur it seemed to be finally fixed by itself after MONTHS of just spinning trying to update the guide from the wrong server
Thanks all
I just noticed one interesting thing that may have caused the spinning refresh guide data issue (not sure).
When I was just reviewing all the settings area I never saw / noticed this but it say the “Approximate refresh guide time will be 2am”
This is of note because I have my music NAS set to SHUTDOWN at 2am and sleep until 8am since Im not using the music streaming server when Im sleeping so trying to get more life our of my NAS drives not being on 24/7
of course this is now moot because I deleted the TV and DVR and antenna tuner from my Music only server but when I did have that on it might have cause the hiccup as it tried to update the guide at 2am and didn’t find the server since it was sleeping??
Just a thought
Now that I only have the TV/video stuff on my NVIDIA Shield this wont be an issue since its always on or sleeping in the background
What do you think?
See screen cap below of the settings area
Hard drives live longer if you spin them down and back up as few times as possible 
The “spin up count” is a major parameter for assessing the health of a hard drive.
Putting a UPS (uninterruptible power source) beside your NAS will have a much greater positive effect on the longevity of your hard drives.
1 Like
