program guide not updating

[jandru]

Long time user. Still on v9.1.9.778.
Last week the program guide stopped updating on my sagetv server. As of today there is no guide data.
I have not made any changes on my system for some time, occasional reboots and the system has bee working great.
I am using
I could not find any info for the problem in the logs but I might not be looking in the right place.
I am using EPG linup Dish Albuquerque (SDEPG).

Anybody have suggestions on a course of action to troubleshoot?
I have verified my SD account is in good standing.
Thanks!

[ASegredo]

Has the schedules direct interface gone dark? I tried deleting and adding a channel.
Nothing shown past 7:00PM CDT tonight.

[KeithAbbott]

My program guide has data thru August 28th, so it's not a global problem.

[tvmaster2]

Mine seems to be working…. 16 days of listing

[sic0048]

Mine seems to be working as well. The only thing I can think of is to log into your Schedule Direct account and make sure you are current.

[Malfunction]

My schedule doesn't update unless I restart SageTV or reboot the computer. EPG is OK. This has been going on for some months. I can attempt to force it from the web UI, and it does get logged but doesn't work. I've been using a scheduled task to trigger a reboot on Monday mornings.

[laberet]

Did you resolve this? Having similar issues...

[Malfunction]

It still doesn't update. I get the files and it shows it updated in the log and in system information, but my schedule doesn't update.

[Malfunction]

Does anyone else have their schedule fail to update even though the EPG polls Schedules Direct and updates the files? Mine only updates when I restart SageTV.

[TGsell]

Mine is working fine (Schedules Direct) Zip COde 11545

[Malfunction]

Originally Posted by TGsell

Mine is working fine (Schedules Direct) Zip COde 11545

There is nothing wrong with Schedules Direct. I'm just having issues importing the schedule from the files on the drive.

[Tiki]

I don’t actually look at the guide all that often. But I do keep an eye on my recording schedule, and Sage is having no trouble scheduling and recording my favorites, so the guide data must be ok.

[Malfunction]

Originally Posted by Tiki

I don’t actually look at the guide all that often. But I do keep an eye on my recording schedule, and Sage is having no trouble scheduling and recording my favorites, so the guide data must be ok.

The way mine works is I load SageTV on Monday and the schedule shows 7 days when I check it. On Tuesday, it shows 6 days, On Wednesday it shows 5, etc, counting down to zero if I let it run through Monday.

[TGsell]

Looks like SD-JSON is having issues - an issue report was posted on their site earlier but now it's been taken down even though my EPG isnt updating. This has happened before and they eventually fix it before the guide runs dry...Anyone else experiencing?

[KryptoNyte]

I start to see missing guide data for Oct 16th. That seems normal to me. What else would I be looking for? Specific errors in the logs?

[TGsell]

Yes -- heres today's log and failure - its true of all three WMCs I have running so I am kind of assuming that SAGE also has potential problem. I can just wait it out but thought someone else was experiencing the same (I should have been clear the only known error is on WMC) . Will keep an eye on SAGE. thanks


[10/1/2022 7:58:08 AM] ===============================================================================
[10/1/2022 7:58:08 AM] [ INFO] Beginning epg123 client execution. 2022-10-01 11:58:08Z
[10/1/2022 7:58:08 AM] [ INFO] Import: True , Match: True , NoLogo: False , Force: False , ShowProgress: True , NoGC: True , NoVerify: True , Verbose: False
[10/1/2022 7:58:09 AM] Entering ImportMxfFile() for file "c:\programdata\garyan2\epg123\output\epg123.mxf".
[10/1/2022 7:58:27 AM] [ INFO] Successfully imported .mxf file into Media Center database. Exit code: 0
[10/1/2022 7:58:27 AM] Exiting ImportMxfFile(). SUCCESS.
[10/1/2022 7:58:29 AM] [ INFO] Skipped matching CHARGE to channel 148 due to channel already having an assigned listing.
[10/1/2022 7:58:29 AM] [ INFO] Skipped matching WPIXDT4 to channel 151 due to channel already having an assigned listing.
[10/1/2022 7:58:29 AM] [ INFO] Completed the automatch of lineup stations to tuner channels.
[10/1/2022 7:58:30 AM] [ INFO] Completed lineup refresh.
[10/1/2022 7:58:30 AM] Entering RunWmcIndexTask(PvrScheduleTask)
[10/1/2022 7:58:30 AM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\PvrScheduleTask".
[10/1/2022 7:58:30 AM] [ INFO] Successfully started the PvrScheduleTask task. Exit code: 0
[10/1/2022 7:58:30 AM] Exiting RunWmcIndexTask(PvrScheduleTask). SUCCESS.
[10/1/2022 7:58:30 AM] Entering RunWmcIndexTask(ReindexSearchRoot)
[10/1/2022 7:58:30 AM] [ INFO] SUCCESS: Attempted to run the scheduled task "Microsoft\Windows\Media Center\ReindexSearchRoot".
[10/1/2022 7:58:30 AM] [ INFO] Successfully started the ReindexSearchRoot task. Exit code: 0
[10/1/2022 7:58:30 AM] Exiting RunWmcIndexTask(ReindexSearchRoot). SUCCESS.
[10/1/2022 7:58:31 AM] [ INFO] MXF file was created on 10/1/2022 7:57:56 AM
[10/1/2022 7:58:31 AM] [ERROR] The imported MXF file contained an ERROR in its status field.
[10/1/2022 7:58:31 AM] [ INFO] Completed EPG123 client execution.
[10/1/2022 7:58:31 AM] [ INFO] EPG123 client execution time was 00:00:22.6706456.

[TGsell]

I updated to the latest EPG123 version and the problem seems to be fixed for my WMCs.... for those who didnt update yet my experience might help you.

[robogeek]

I may be seeing the issue now in SageTV with the following error in the SageTV debug log:

Tue 10/4 2:01:40.116 [EPG@22be2e09] SDEPG Exception thrown: Server returned HTTP response code: 403 for URL: https://json.schedulesdirect.org/20141201/schedules/md5
Tue 10/4 2:01:40.117 [EPG@22be2e09] java.io.IOException: Server returned HTTP response code: 403 for URL: https://json.schedulesdirect.org/20141201/schedules/md5
Tue 10/4 2:01:40.117 [EPG@22be2e09] 	at sun.reflect.GeneratedConstructorAccessor506.newInstance(Unknown Source)
Tue 10/4 2:01:40.117 [EPG@22be2e09] 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
Tue 10/4 2:01:40.117 [EPG@22be2e09] 	at java.lang.reflect.Constructor.newInstance(Unknown Source)
Tue 10/4 2:01:40.117 [EPG@22be2e09] 	at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source)
Tue 10/4 2:01:40.117 [EPG@22be2e09] 	at sun.net.www.protocol.http.HttpURLConnection$10.run(Unknown Source)
Tue 10/4 2:01:40.117 [EPG@22be2e09] 	at java.security.AccessController.doPrivileged(Native Method)
Tue 10/4 2:01:40.117 [EPG@22be2e09] 	at sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source)
Tue 10/4 2:01:40.117 [EPG@22be2e09] 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
Tue 10/4 2:01:40.117 [EPG@22be2e09] 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
Tue 10/4 2:01:40.117 [EPG@22be2e09] 	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source)
Tue 10/4 2:01:40.117 [EPG@22be2e09] 	at sage.epg.sd.SDUtils.getStream(SDUtils.java:109)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sage.epg.sd.SDSageSession.post(SDSageSession.java:161)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sage.epg.sd.SDSageSession.post(SDSageSession.java:157)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sage.epg.sd.SDSageSession.post(SDSageSession.java:107)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sage.epg.sd.SDSession.post(SDSession.java:475)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sage.epg.sd.SDSession.postAuth(SDSession.java:453)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sage.epg.sd.SDSession.postAuthJson(SDSession.java:653)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sage.epg.sd.SDSession.getSchedulesMd5(SDSession.java:1159)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sage.epg.sd.SDRipper.extractGuide(SDRipper.java:1576)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sage.EPGDataSource.expand(EPGDataSource.java:709)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sage.EPG.run(EPG.java:773)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at java.lang.Thread.run(Unknown Source)
Tue 10/4 2:01:40.118 [EPG@22be2e09] Caused by: java.io.IOException: Server returned HTTP response code: 403 for URL: https://json.schedulesdirect.org/20141201/schedules/md5
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at java.net.HttpURLConnection.getResponseCode(Unknown Source)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unknown Source)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	at sage.epg.sd.SDUtils.getStream(SDUtils.java:95)
Tue 10/4 2:01:40.118 [EPG@22be2e09] 	... 11 more
Tue 10/4 2:01:40.119 [EPG@22be2e09] EPGDS Local Over the Air Broadcast  - 54914 (sdepg) found a capture device to start data scanning with:Silicondust HDHomeRun Tuner 107734D8-3 Digital TV Tuner

and and then followed up with this error:

Tue 10/4 2:03:40.746 [EPG@22be2e09] ERROR Updating EPG Source Local Over the Air Broadcast  - 54914 (sdepg)
Tue 10/4 2:03:40.747 [EPG@22be2e09] ErrorText:expand called on Local Over the Air Broadcast  - 54914 (sdepg) at Tue 10/4 2:00:39.536 expandedUntil=Tue 10/4 1:56:35.215 scannedUntil=Tue 10/4 2:00:00.000
EPG Expanding Local Over the Air Broadcast  - 54914 (sdepg) at Tue 10/4 2:00:39.537

I'm not sure if this error is just a temporary error on the SD website or if this is related to the new token requirement. From the SD website homepage:

October 1st 2022

SD-JSON images now require tokens
Effective 2022-10-01, the Schedules Direct service will be requiring that the user token be presented for most interaction with our servers. If you are running NextPVR v6 or EPG123 v1.7.1.8 or higher then this will re-enable image downloads.

If you are a developer, please check the updated API documentation. You may also contact grabber@schedulesdirect.org if you would like to have your requests steered to a “debug” server while you are testing the addition of the token to your code.

Two local OTA networks shuffled some subchannels around and add a couple of new subchannels over this past weekend and I can't get new guide data for these new and moved subchannels. Maybe it's due to the SD feed not having the new channel lineup changes integrated yet. I have guide data in SageTV for my other local OTA channels out to 7pm October 20th, so I'll keep an eye the logs and the guide to see what happens.

[emveepee]

I know in addition to the artwork changes we tested with NextPVR SD introduced blocking for multiple uses of user credentials. So you have various SD clients, if the token isn't re-authenticated on failure things won't work.

Previous behaviour was all tokens were valid for 24 hours, and I'm not sure how SageTV deals with this. If you have multiple servers calling SD definitely don't run EPG updates at the same time.

Martin

[TGsell]

The token requirement could explain why updating to EPG123 v1.7.1.8 seems to completely remedy my issue. So far it's good.