[mythtv-users] Schedules Direct DataDirect replacement service testing

[Jay Foster]

On 10/11/2014 7:53 PM, Robert Eden wrote:
> On 10/11/2014 9:39 PM, Bill Meek wrote:
>> On 10/11/2014 09:34 PM, Robert Eden wrote:
>>> On 10/11/2014 8:19 PM, Yeechang Lee wrote:
>>>> Robert Eden <rmeden at gmail.com> says:
>>>>> If you need to edit your hosts file, use this address: 54.85.117.227
>>>>> That's a floating IP currently assigned to the server.
>>>> So is this IP preferable to whatever dd.schedulesdirect.org points to
>>>> at a given moment?
>>>>
>>> No.   dd.schedulesdirect.org is preferred.  I'll point that where it 
>>> needs to go.
>>
>> But if Yeechang means what address is preferred for the /etc/hosts
>> solution, then 54.85.117.227 is correct. At least that's what I
>> updated the Wiki to say.
>>
> Yes, he (and you) are right then.
>
> 1. Use dd.schedulesdirect.org if you can use a hostname.
> 2. Use 54.85.117.227 if you have to hard code an address in /etc/hosts.
>
> Robert
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
I seem to be having problems with the SD listings.  When I run MFDB, I 
see the following:

Resolving webservices.schedulesdirect.tmsdatadirect.com... 54.85.117.227
Connecting to 
webservices.schedulesdirect.tmsdatadirect.com|54.85.117.227|:80... 
connected.
HTTP request sent, awaiting response... 401 Authorization Required
Connecting to 
webservices.schedulesdirect.tmsdatadirect.com|54.85.117.227|:80... 
connected.
HTTP request sent, awaiting response... 402 Account Expired
2014-10-17 10:19:26 ERROR 402: Account Expired.

2014-10-17 10:19:26.981 DataDirect, Error: Failed to save DD cache! 
redownloading data...
--2014-10-17 10:19:26-- 
http://webservices.schedulesdirect.tmsdatadirect.com/schedulesdirect/tvlistings/xtvdService

My account is NOT expired (confirmed on the SD website).  I have not 
seen this happen with the previous service.  Looks like something odd 
going on.

Later in the same MFDB run, I see:

2014-10-17 10:25:37.828 Main temp tables populated.
2014-10-17 10:25:37.829 Did not find any new program data.
2014-10-17 10:25:37.865 Failed to fetch some program info
2014-10-17 10:25:37.865 Adjusting program database end times.
2014-10-17 10:25:38.888     0 replacements made
2014-10-17 10:25:38.888 Marking generic episodes.
2014-10-17 10:25:39.456     Found 14949
2014-10-17 10:25:39.457 Marking repeats.
2014-10-17 10:25:40.432     Found 41959
2014-10-17 10:25:40.432 Unmarking new episode rebroadcast repeats.
2014-10-17 10:25:40.863     Found 0
2014-10-17 10:25:41.538 Marking episode first showings.
2014-10-17 10:25:43.847     Found 10595
2014-10-17 10:25:43.847 Marking episode last showings.
2014-10-17 10:25:46.272     Found 10595
2014-10-17 10:25:46.286

The "Failed to fetch some program info" I think is a result of some of 
the data fetches reporting Account Expired.
Jay