no automatic epg update

[ww4397]

Yeah, I cant quite see how he is tying WAU into this one either.

I'm not necessarily tying it in. I'm making observations. And, it appears that things seemed to change after I turned WUA off.

I'll wait until tomorrow and see what the next automatic EPG update, with WUA turned off, brings...

[ww4397]

I'll wait until tomorrow and see what the next automatic EPG update, with WUA turned off, brings...

Well it brought no joy. I'm right back where I started -- the machine wakes up for ~9-10 minutes and then goes back into standby without updating the EPG.

Log snip-it:

2/4/2007 5:00:01 AM.546 VERBOSE [12] Will run EPG update soon...
2/4/2007 5:00:31 AM.562 VERBOSE [12] Keeping machine awake for pending EPG update...
2/4/2007 5:00:31 AM.578 VERBOSE [12] Initiating EPG update...
2/4/2007 5:00:31 AM.578 VERBOSE [12] exporting backup of recordings data...
2/4/2007 5:00:31 AM.578 VERBOSE [12] RecordingFactory.loadSchedule()
2/4/2007 5:00:31 AM.593 VERBOSE [12] getValue cached value: /settings/AutoRemoveMissingRecordings : true
2/4/2007 5:00:32 AM.375 VERBOSE [12] updating EPG...
2/4/2007 5:00:32 AM.375 INFO [12] Auto-Updating EPG
2/4/2007 5:00:32 AM.390 VERBOSE [12] getValue cached value: /settings/Zap2itListingDays : 15
2/4/2007 5:00:32 AM.390 VERBOSE [12] getValue cached value: /settings/CompleteEPGReload : true
2/4/2007 5:00:32 AM.390 VERBOSE [12] Zap2it full EPG update required.
2/4/2007 5:00:32 AM.390 VERBOSE [12] Processing zap2it channels using SAX parser
2/4/2007 5:00:32 AM.390 VERBOSE [12] Requesting listings for the period: 2007-02-04T00:00:00Z to 2007-02-19T23:59:59Z
2/4/2007 7:32:03 AM.703 VERBOSE [12] Error updating EPG Source (PVR150): System.Net.WebException: The operation has timed out.
at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
at System.Net.WebClient.UploadData(Uri address, String method, Byte[] data)
at System.Net.WebClient.UploadData(String address, String method, Byte[] data)
at GBPVR.Backend.Common.Zap2itEpgReader.x7174d5399cba81ee(IEpgUpdateProgressCallback x421ce789b9741187, DateTime xdc88f59e43b65f7f, DateTime x33db96d2cea26583)
at GBPVR.Backend.Common.Zap2itEpgReader.LoadChannels(IEpgUpdateProgressCallback callback)
at GBPVR.RecordingService.xa9e17cce0eee6a7a.x52e8ddd0b9bc8c68()

[sub]

Any how long is it taking to pull your listings in from zap2it and processing them?

[_gl]

I also have the same problem (I've been meaning to post about this for a while). It started a couple or so versions ago:

a) I use XMLTV GUI via the Windows Task Scheduler to grab listings every day (that works fine), and GB is set to auto-import the generated XML file at 7pm. But every week my pending recordings run out and I have to update manually from config, so clearly GB isn't importing them.

b) btw, updating the XML file manually seems to take forever, but there is usually virtually no CPU time or disk trashing going on. Is it possible the 'playing nice' download throttling/pausing is accidentally being applied to the local file import?

c) my machine often wakes up at really bizarre moments. Could be various things, but before I had the EPG problems, it was more predictable.

d) GB now crashes when I try to initiate an EPG update from the System menu. This only started happening about two versions ago, before that it was fine.

I've attached my logs, just after I caused the crash in d).

BTW, the EPG issues are my only remaining problem with GB now that the pause still frames are fixed. Just aswell, you're running out of build numbers Sub - 1.0 here we come.

[sub]

I also have the same problem (I've been meaning to post about this for a while). It started a couple or so versions ago:

a) I use XMLTV GUI via the Windows Task Scheduler to grab listings every day (that works fine), and GB is set to auto-import the generated XML file at 7pm. But every week my pending recordings run out and I have to update manually from config, so clearly GB isn't importing them.

b) btw, updating the XML file manually seems to take forever, but there is usually virtually no CPU time or disk trashing going on. Is it possible the 'playing nice' download throttling/pausing is accidentally being applied to the local file import?

c) my machine often wakes up at really bizarre moments. Could be various things, but before I had the EPG problems, it was more predictable.

d) GB now crashes when I try to initiate an EPG update from the System menu. This only started happening about two versions ago, before that it was fine.

I've attached my logs, just after I caused the crash in d).

I can see an error occuring in your logs that would account (a) and probably (d) above.

02/02/2007 19:06:43.301 VERBOSE [8] Initiating EPG update...
02/02/2007 19:06:43.301 VERBOSE [8] exporting backup of recordings data...
02/02/2007 19:06:43.301 VERBOSE [8] RecordingFactory.loadSchedule()
02/02/2007 19:06:43.301 VERBOSE [8] getValue cached value: /settings/AutoRemoveMissingRecordings : true
02/02/2007 19:06:43.614 ERROR [8] Object reference not set to an instance of an object.
02/02/2007 19:06:43.723 ERROR [8] at GBPVR.Backend.Common.x396614b3dae3b1da.x961866b492315542()
at GBPVR.RecordingService.xa9e17cce0eee6a7a.xcba1f05fb5a46d5f()

Its not clear exactly why, but I do know the error is occuring when it tries to generate the recording backup file (recordings-dump.xml) before it actually starts the EPG update.

You'll probably find an error occurs, or at least the process doesnt work, when you click the 'export recordings' button in the config app. These two things are both calling the same function, which seems to be the one failing.

Its probably something odd one of the recordings refers a channel that no longer exists, or a program that no longer exists, or something similar. (ie, a corrupt recording record in the database)

I've made a small change to the next release to ensure this error wont stop the rest of the EPG update from occurring.

[ww4397]

Any how long is it taking to pull your listings in from zap2it and processing them?

About 15 minutes to do it all including running zapimport after EPG update.

I found this in my logs today. Any ideas about what is in bold? Could that have something to do with the problem?

2/6/2007 6:00:47 AM.703 VERBOSE [12] Requesting listings for the period: 2007-02-06T00:00:00Z to 2007-02-21T23:59:59Z
2/6/2007 6:00:47 AM.984 VERBOSE [12] Error updating EPG Source (m150): System.Net.WebException: The remote name could not be resolved: 'datadirect.webservices.zap2it.com'
at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
at System.Net.WebClient.UploadData(Uri address, String method, Byte[] data)
at System.Net.WebClient.UploadData(String address, String method, Byte[] data)
at GBPVR.Backend.Common.Zap2itEpgReader.x7174d5399cba81ee(IEpgUpdateProgressCallback x421ce789b9741187, DateTime xdc88f59e43b65f7f, DateTime x33db96d2cea26583)
at GBPVR.Backend.Common.Zap2itEpgReader.LoadChannels(IEpgUpdateProgressCallback callback)
at GBPVR.RecordingService.xa9e17cce0eee6a7a.x52e8ddd0b9bc8c68()

[_gl]

I can see an error occuring in your logs that would account (a) and probably (d) above.

<snip>

Its probably something odd one of the recordings refers a channel that no longer exists, or a program that no longer exists, or something similar. (ie, a corrupt recording record in the database)

Ah, that's very possible, I have edited the db to remove phantom channels that simply wouldn't remove from the config app (and thus were cluttering up my program guide). I've had to rebuild the db a couple of times in the past specifically due to channel problems. It would be good if GB could force-remove a channel from the db, even if all the internal references aren't quite as expected.

I've made a small change to the next release to ensure this error wont stop the rest of the EPG update from occurring.

Great, I'll report back when that comes out.

[sub]

Ah, that's very possible, I have edited the db to remove phantom channels that simply wouldn't remove from the config app (and thus were cluttering up my program guide). I've had to rebuild the db a couple of times in the past specifically due to channel problems. It would be good if GB could force-remove a channel from the db, even if all the internal references aren't quite as expected.

Yeah, I'm guessing you cocked it up when you did this.

You could always fix it by checking at all recordings in your database refer to channels and programs that exists.

[sub]

I found this in my logs today. Any ideas about what is in bold? Could that have something to do with the problem?

2/6/2007 6:00:47 AM.703 VERBOSE [12] Requesting listings for the period: 2007-02-06T00:00:00Z to 2007-02-21T23:59:59Z
2/6/2007 6:00:47 AM.984 VERBOSE [12] Error updating EPG Source (m150): System.Net.WebException: The remote name could not be resolved: 'datadirect.webservices.zap2it.com'
at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
at System.Net.WebClient.UploadData(Uri address, String method, Byte[] data)
at System.Net.WebClient.UploadData(String address, String method, Byte[] data)
at GBPVR.Backend.Common.Zap2itEpgReader.x7174d5399cba81ee(IEpgUpdateProgressCallback x421ce789b9741187, DateTime xdc88f59e43b65f7f, DateTime x33db96d2cea26583)
at GBPVR.Backend.Common.Zap2itEpgReader.LoadChannels(IEpgUpdateProgressCallback callback)
at GBPVR.RecordingService.xa9e17cce0eee6a7a.x52e8ddd0b9bc8c68()

In this case it failed because it was unable to resolve the name 'datadirect.webservices.zap2it.com' into an IP address. This would typically occur if your ISPs DNS server was down at the time, or some firewall is disallowing GB-PVR's Recording Service from accessing the DNS.