What about those of us that aren’t up and running? Should we re-setup up our DVR (which will be a royal pain – trying to remember TV shows to record and their priority, editing channel lineups, etc.), or is there a fix coming that will restore our DVR and its settings?
Thanks for the new logs
Yes it does show the auto deletion of the DVR - before this hung. Whereas with this version 1.16.4.1469 it completed the deletion at 23:42:46 on 5 August
Aug 05, 2019 23:42:46.655 [5244] DEBUG - HTTP 200 response from GET https://epg.provider.plex.tv/lineups/matches?guid=lineup%3A%2F%2Ftv%2Eplex%2Eproviders%2Eepg%2Eonconnect%2FUSA-MA65213-X%23Verizon%2520Fios%2520Burlington%2520-%2520Digital&X-Plex-Api-Token=xxxxxxxxxxxxxxxxxxxx
Aug 05, 2019 23:42:46.656 [5244] WARN - No matching Cloud EPG lineup; deleting DVR.
Aug 05, 2019 23:42:46.720 [5244] DEBUG - Media Provider: Deregistering provider tv.plex.providers.epg.onconnect:10
Aug 05, 2019 23:42:46.721 [5244] DEBUG - DVR: Unparenting 1 devices.
This should allow you to re-create the DVR manually by going through server settings for Live TV and DVR
The DVR was discovered ok after the deletion
Aug 05, 2019 23:44:16.017 [5244] DEBUG - DVR:Device: Discovering and refreshing devices with identifier tv.plex.grabbers.hdhomerun
Aug 05, 2019 23:44:16.029 [5244] DEBUG - DVR:Grabber: HDHomerun discovered a model HDHR3-CC.
Aug 05, 2019 23:44:16.029 [5244] DEBUG - HTTP requesting GET http://10.0.0.2:80/discover.json
Aug 05, 2019 23:44:16.030 [5244] DEBUG - HTTP 200 response from GET http://10.0.0.2:80/discover.json
Aug 05, 2019 23:44:16.044 [5244] DEBUG - DVR:Grabber: HDHomerun discovered 1 compatible devices.
Aug 05, 2019 23:44:16.044 [5244] DEBUG - HTTP requesting GET http://10.0.0.2:80/discover.json
Aug 05, 2019 23:44:16.055 [5244] DEBUG - HTTP 200 response from GET http://10.0.0.2:80/discover.json
Aug 05, 2019 23:44:16.074 [5244] DEBUG - HTTP requesting GET http://10.0.0.144/discover.json
Aug 05, 2019 23:44:21.079 [19940] DEBUG - DVR:Device: Discovering and refreshing devices with identifier tv.plex.grabbers.hdhomerun
Aug 05, 2019 23:44:21.080 [19940] DEBUG - DVR:Grabber: HDHomerun discovered a model HDHR3-CC.
What did the server settings page for Live TV & DVR show at this time?
How many DVRs do you have?
Is this a second DVR or an old IP address ?
http://10.0.0.144/discover.json
The auto migration attempts to match old schedules to the new EPG - but as there was no lineup match for your setup, the DVR needs to be recreated manually and after that see if any of your old schedules get migrated across
At the moment you need to go through server settings to create the DVR (after the auto deletion). If your DVR does not show up - wait 30 seconds (I have seen cases where old IP addresses for DVRs in the database result in delays) - and then select the DVR and go through setup
Just one DVR on the network. That must be an old IP address, as my DVR is currently at 10.0.0.2.
On 1.16.4, it briefly showed the DVR on the server settings page right after Plex Media Server started up, and then it was completely gone. I exited and restarted the app to see if the DVR would show back up – even briefly – but no joy. Will try recreating manually, I guess.
Could you get me the data that gets returned by these requests
Copy each response into a text file and zip the files and let me have a look
http://192.168.80.4/discover.json
http://192.168.80.4/lineup_status.json
http://192.168.80.4/lineup.json
Once it is auto deleted, it needs to be setup manually. So it would not appear again until you go through the setup. The bug in the previous version was that the auto deletion hung
@RMU - might also need your XMLTV file. Could you zip it and send me by private message - also what country you selected from the drop down. Please include that in the private message
Thanks
I have sent you a private message with the requested information.
Thanks so far!
Thank you
Ok, thanks. Was able to set it up again, and it’s downloading EPG data now. My series recordings/priority lists are still there. Phew! My wife would have killed me otherwise.
Cause of the problem found. The issue arises when using XMLTV if the channel identifier has a space character in it.
Until a fix is written and released, I understand you can get round the problem by editing the xmltv file and removing the space characters from the channel identifiers
Hi,
I am still having a problem - in so far as I have upgraded to 1.16.4.1469 - it has now “discovered” my HDHR - but won’t progress beyond 0% in the "finding best guide data.
It’s odd, because I can see that in the logs, it is finding the guide data and computing the best lineup, but still doesn’t progress to (I assume) download the data and setup the DVR
16379 Aug 06, 2019 10:10:58.069 [0x7fd2ce2b3700] DEBUG - Activity: updated activity d5222e12-efa2-4797-bd2e-0f347d4a6a22 - completed 100.000000% - Computing best lineup
16380 Aug 06, 2019 10:10:58.069 [0x7fd2ce2b3700] DEBUG - EPG: Score for lineup lineup://tv.plex.providers.epg.cloud/5cfe43f0e98f74001d05d7c9#YouView%20Central%20(West)%20IPTV was 130.6
16381 Aug 06, 2019 10:10:58.070 [0x7fd2ce2b3700] DEBUG - Activity: Ended activity d5222e12-efa2-4797-bd2e-0f347d4a6a22.
16382 Aug 06, 2019 10:10:58.076 [0x7fd2ce2b3700] DEBUG - EPG: Best computed lineup was lineup://tv.plex.providers.epg.cloud/5cfe43efe76ff6001e54f53c#Freeview-National%20Lineup%20United%20Kingdom%20OTA%20Broadcast with a total score of 208.6
I attached a full set of logs at post 211 - I’m new(ish) here, so I incorrectly “quoted” you rather than “Replied” - so I guess you may have missed it.
https://forums.plex.tv/t/plextv-server-can-no-longer-see-hdhomerun-tuner/425461/211?u=batterbits
It is possible that async events are not getting through from the server to the Plex Web session that is doing the create DVR. I have seen this before on a system with a reverse proxy and non standard network setup.
Were you setting up the DVR directly from the local network ?
Oh I can see it is being done through a WAN IP address
Aug 06, 2019 09:59:13.419 [0x7fd3071c6700] DEBUG - Using X-Forwarded-For: 165.225.xxx.xxx as remote address
Aug 06, 2019 09:59:13.419 [0x7fd3071c6700] DEBUG - Auth: authenticated user 1 as BatterBits
Aug 06, 2019 09:59:13.420 [0x7fd2cd9e9700] DEBUG - Request: [192.168.1.119:36472 (WAN)] GET /livetv/dvrs (6 live) GZIP Signed-in Token (BatterBits)
Aug 06, 2019 09:59:13.422 [0x7fd3071c6700] DEBUG - Completed: [192.168.1.119:36472] 200 GET /livetv/dvrs (6 live) GZIP 2ms 447 bytes
Has doing setup this way ever worked ? ie through a forwarded WAN IP address to the local network?
We send events to Plex Web every few seconds to show progress and if these do not get through then it would stick at 0%
Thanks for your fast response.
I set up the HDHR on a mac reservation so the IP address doesn’t change - it’s on 192.168.1.61
Up until a while ago (beginning of July perhaps?) it was all working, and recording a few programmes. Then it “couldn’t load DVRs” as per other users in this thread. I tried adding the ip address, but no joy, and then when you released the latest version of the software, I installed that, and it “found” my HDHR, but won’t get the guide data, so doesn’t progress beyond 0%
I have tried this (currently remotely) via my https link into the server, via the app.tv link, via vnc to a local (to home) machine and actually at home, on the local network- using the ip address, all the results are the same.
PMS is running on my Qnap NAS (TS-453A) - I suppose I could set up a linux based server at home and try from there, but it’s a bit of a sledgehammer, if you know what I mean…
The old issues have been resolved and we should go forward now with evidence from version 1.16.4 - previous user reports are no longer relevant as the causes for these have already been identified and fixed
Need to look into firewalls to see if anything blocking async notification events. Best to do the test within the local network - so i do not want to see evidence of setup coming through a WAN connection as was in the provided logs
and wait for few minutes before gathering the logs in case it is just slow and please include a screenshot without cropping so i want to see time and url as well and relate that to the logs
I remoted into my home Linux box - just the same as I did yesterday, but today it worked - it managed to get the guide data, - or rather 23% of it so far. Nothing has changed other than I restarted the Plex Server this morning - I didn’t do that after the new install, because I figured it had to restart itself as part of the upgrade.
It shows up immediately on my remote connection, but just prior to starting it on the local system, I started it again on the remote system, and it still didn’t work.
I usually do all the admin remotely - I can’t think why I wouldn’t have done so when I set it up originally, but maybe I didn’t - it’s a few years ago now.
Anyway - bottom line is - it’s now working again. Many thanks for your help, and for pointing me in the right direction…
I don’t think we had async event notifications then
I’ve been having a problem with the EPG data with my HDHR. I’ve gone back to previous versions, upgraded again and tried deleting my tuner. I seem to be stuck with the EPG constantly trying to update but being stuck at 0%. I’m currently using version 1.16.4.1469. I’m attaching the log file hoping that helps getting this resolved. The tuner shows up but I can’t get the guide data.
Plex Media Server Logs_2019-08-08_10-14-27.zip (1.6 MB)
1 Like
You can wait for sa2000 to review but I believe you have database corruption. Do you have a backup from before August 6th?
Line 450: Aug 07, 2019 12:15:55.397 [10948] ERROR - SQLITE3:0xf5737927, 11, statement aborts at 21: [delete from media_parts where media_item_id=?] database disk image is malformed
Line 451: Aug 07, 2019 12:15:55.397 [10948] ERROR - Exception inside transaction (inside=1) (..\Library\MediaItem.cpp:769): sqlite3_statement_backend::loadOne: database disk image is malformed
Line 452: Aug 07, 2019 12:15:55.397 [10948] ERROR - Thread: Uncaught exception running async task which was spawned by thread 10632: sqlite3_statement_backend::loadOne: database disk image is malformed
Line 1244: Aug 07, 2019 12:16:07.924 [9968] ERROR - SQLITE3:0xf5737927, 11, database corruption at line 85694 of [bf8c1b2b7a]
Line 1245: Aug 07, 2019 12:16:07.924 [9968] ERROR - SQLITE3:0xf5737927, 11, statement aborts at 131: [select media_items.id as 'media_items_id', media_items.library_section_id as 'media_items_library_section_id', media_items.section_location_id as 'media_items_section_location_id', me
Line 1246: Aug 07, 2019 12:16:07.924 [9968] ERROR - Thread: Uncaught exception running async task which was spawned by thread 9736: sqlite3_statement_backend::loadRS: database disk image is malformed
https://support.plex.tv/articles/201100678-repair-a-corrupt-database/
1 Like
