Plugin: Schedules Direct EPG (not for v9)

[Slugger]

Actually, upon further review, this looks like my problem. Give me an hour or so, should have a fix.

[Slugger]

Fixes issues with lineup registration/unregistration from the webui. See the details for 0.0.6.1 (a few posts back) for further instructions.

[gdippel]

Updated plugin, registered lineups, setup video sources. No epg data. I have 4 files in the depg plugin directory: sdjson.epg (17,258kb) stations.txt (6kb), web.menu (1kb) and a temp file (46,895kb). I tried refreshing in the plugin config, still no epg data.

[Slugger]

We're getting closer then.

The temp file suggests something crashed while grabbing data from SD. In plugins/sdepg/logs/sdepg.log, are there any exceptions? Any errors? If not, go back to plugin settings, set the "Log Level" setting to debug, try again, zip up all the logs in the logs dir, send them my way.

[gdippel]

I deleted the sdjson.epg file and the temp file and refreshed the epg and now the epg is populating with data.

[Slugger]

Originally Posted by gdippel

I deleted the sdjson.epg file and the temp file and refreshed the epg and now the epg is populating with data.

That's good, but I'd still be interested in knowing if there are any errors and/or exceptions logged in the sdepg.log file from the first attempt.

[gdippel]

I've attached all the logs from the sdepg plugin directory.

[Slugger]

Hmm... interesting:

2014-04-26 15:12:22,510 ERROR [EpgDownloader]: stderr:
Exception in thread "main" java.nio.file.AccessDeniedException: C:\Program Files\SageTV\SageTV\plugins\sdepg\sdjson.epg
	at sun.nio.fs.WindowsException.translateToIOException(Unknown Source)
	at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
	at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
	at sun.nio.fs.WindowsFileSystemProvider.checkReadAccess(Unknown Source)
	at sun.nio.fs.WindowsFileSystemProvider.checkAccess(Unknown Source)
	at com.sun.nio.zipfs.ZipFileSystem.<init>(ZipFileSystem.java:124)
	at com.sun.nio.zipfs.ZipFileSystemProvider.newFileSystem(ZipFileSystemProvider.java:117)
	at java.nio.file.FileSystems.newFileSystem(Unknown Source)
	at java.nio.file.FileSystems.newFileSystem(Unknown Source)
	at org.schedulesdirect.grabber.Grabber.updateZip(Grabber.java:423)
	at org.schedulesdirect.grabber.Grabber.execute(Grabber.java:725)
	at org.schedulesdirect.grabber.Grabber.main(Grabber.java:832)

So for some reason, the grabber appeared to create the .epg file, but then the SageTV process could not access it. My guess is maybe you ran the grabber as a user other than the one SageTV runs as and this is why? Or some thing like that. But in either case, there isn't anything for me to fix since if Sage can't open the epg file, I definitely can't process it.

By deleting both the temp file and the epg file, the next forced update would have had the SageTV process call the grabber, creating the epg file, and then reading it from within Sage, which appears to have worked, as expected. I assume your EPG is filled in now?

[gdippel]

Yes it's filled.

[Slugger]

Excellent. Thanks for being the first to upgrade (besides me)!

Not bad, really. Just those web page issues, which I actually had the fix for awhile ago, but forgot to commit them to the git repository.

All in all I'd say a rather smooth start, though you don't want to know how many tries (i.e. painful Sunday mornings over the last 6 weeks or so) it took me to iron out those upgrade steps in that wiki. That upgrade wiki is only necessary when Schedules Direct overhauls the unique lineup ids it generates for the lineups on their end, which was the case this time around, but hopefully won't happen again anytime soon.

[rnadeau]

Updated the plugin using Wiki instructions. Everything is fine. program guide has data. Thanks for you hard work.

[gdippel]

Originally Posted by Slugger

Excellent. Thanks for being the first to upgrade (besides me)!

Thanks for the update and your other plugins, SJQ and SRE the major reason I'm still using Sage.

[gdippel]

There are several Broadcast Network sub-channels that are not populating with guide data, e.g. 2-2, 5-2, 9-2. They did have data before the epg upgrade. Should I send a email to Schedules Direct or is this a plugin issue?

[Slugger]

I do believe that was the last bug fixed by SD late last week so I'd say open an issue at Schedules Direct. You can confirm it's an SD issue by taking a peak inside the sdjson.epg file (it's just a plain zip file) and looking for schedule files for the station ids that are missing. If they don't exist or they exist and are empty, it's an SD issue. If they exist and have meaningful schedule data inside then it's likely my issue.

[gdippel]

The station IDs are missing in the schedules directory of the epg file so I'll send Schedules Direct a message.

[JerryB]

I downloaded and installed the SDepg update following the instructions you posted for upgrading. I registered my lineups, added my video sources and attached them to the SD lineups, and forced a manual download of the epg. The download of the epg went fine but I'm not seeing any program listings in SageTV. I've attached the log files and hopefully they'll help figure out what the problem is.

[Slugger]

Hmm... well this isn't good:

java.lang.NullPointerException
	at java.io.RandomAccessFile.writeBytes0(Native Method)
	at java.io.RandomAccessFile.writeBytes(Unknown Source)
	at java.io.RandomAccessFile.write(Unknown Source)
	at sage.au.cd(Unknown Source)
	at sage.aw.cd(Unknown Source)
	at sage.av.if(Unknown Source)
	at sage.cd.l(Unknown Source)
	at sage.av.a(Unknown Source)
	at sage.av.a(Unknown Source)
	at sage.av.a(Unknown Source)
	at sage.z$a$0.call(Unknown Source)
	at sagex.epg.schedulesdirect.sagetv.helpers.EPGDBPublicAdvancedImpl.addAiringPublic2(EPGDBPublicAdvancedImpl.groovy:216)
	at sagex.epg.schedulesdirect.sagetv.helpers.IEPGDBPublicAdvanced$addAiringPublic2.call(Unknown Source)
	at sagex.epg.schedulesdirect.EPGImportPluginSchedulesDirect.addAiring(EPGImportPluginSchedulesDirect.groovy:415)
	at sagex.epg.schedulesdirect.EPGImportPluginSchedulesDirect.this$2$addAiring(EPGImportPluginSchedulesDirect.groovy)

The problem appears to be Sage core is failing to write to wiz.bin. Unfortunately, you need Sage support to answer the "why is there an NPE?" I can't do anything other than venture a guess as to the cause when it's Sage core calls throwing the exceptions. The best that I can deduce here is that I'm submitting a new airing to be written to wiz.bin, Sage core accepted the request and tried to write it to wiz.bin, and something failed during the write to wiz.bin.

The best we can hope for is that there's a specific airing in the epg feed that's causing it. I would have to generate a special debug jar for you to try in order to generate the output needed to track it down. Send me an email or if you don't have my address then PM for more details.

[Slugger]

Do you happen to be using any of the airing or program generator features (i.e. do you have any generator groovy scripts installed and executing)? I see a bug in that section of the code that needs to be addressed and if you're using these features then it could maybe explain what you're seeing.

[JerryB]

The program guide appears to be slowly filling with data, at least I have listings for some channels now. What I suggest doing is to give it a day and see if all the channels eventually fill with data and, if not, which ones don't have data. If the problem doesn't resolve itself, then I'll email you and you can send me the special jar to try and track this down.

Edit: I just saw your other message. No, I'm not using any generator scripts.

[Slugger]

Sounds good. Please upgrade to 0.0.6.3 when Sage tells you it's available. If you run generators then this might just fix you up, if you don't then this fix is unrelated, but still need you on the latest version so we're in sync when we start to try and track this down.