TMS dropping Data Direct!!! But no reason to panic.

rkulagow
SD Staff
Posts: 933
Joined: Tue Aug 14, 2007 3:15 pm

Re: TMS dropping Data Direct!!! But no reason to panic.

Post by rkulagow »

You should be able to run with the --force command line parameter.

Re-run the script with --help to see all the options.

pgbennett
Posts: 13
Joined: Sat Sep 27, 2014 2:03 pm

Re: TMS dropping Data Direct!!! But no reason to panic.

Post by pgbennett »

rkulagow wrote:You should be able to run with the --force command line parameter.

Re-run the script with --help to see all the options.
Thank you, the --force worked (and I should have thought of trying --help).

When I ran the mfdb-json.php --force, it failed with the following messages.

2014-10-01 02:11:46:WARNING: JSON does not contain any program elements.
2014-10-01 02:11:46:Send the following to grabber@schedulesdirect.org

array(6) {
["response"]=>
string(18) "SCHEDULE_NOT_FOUND"
["code"]=>
int(7100)
["serverID"]=>
string(10) "20140530.2"
["message"]=>
string(115) "The schedule you requested should be available. Post message to viewforum.php?f=6"
["datetime"]=>
string(20) "2014-10-01T02:11:39Z"
["stationID"]=>
string(5) "53251"
}
2014-10-01 02:11:46:{"response":"SCHEDULE_NOT_FOUND","code":7100,"serverID":"20140530.2","message":"The schedule you requested should be available. Post message to http:\/\/forums.schedulesdirect.org\/viewforum.php?f=6","datetime":"2014-10-01T02:11:39Z","stationID":"53251"}

The stationid 53251 was assigned to channel 590, Local Origination - LOOR590. This was added by the U command on Saturday, so it should know about that station id.

I marked channel 590 as Not Visible, and reran the mfdb-json.php --force and it was successful. It loaded all the data in 6 minutes.

I do not really expect to see any listings for "Local Origination" channels, however I don't want the schedule download to fail because of it.

On the whole the new json downloaded is looking good.

Peter

rkulagow
SD Staff
Posts: 933
Joined: Tue Aug 14, 2007 3:15 pm

Re: TMS dropping Data Direct!!! But no reason to panic.

Post by rkulagow »

2014-10-01 02:11:46:{"response":"SCHEDULE_NOT_FOUND","code":7100,"serverID":"20140530.2","message":"The schedule you requested should be available. Post message to http:\/\/forums.schedulesdirect.org\/viewforum.php?f=6","datetime":"2014-10-01T02:11:39Z","stationID":"53251"}
OK, so this is a bug. What's actually happened is that this particular station has been marked as deleted upstream. I will change the error message to indicate that, and figure out why if it's deleted that it's still being included in the lineup.

If you tune to 590, what do you get?

bdmc
Posts: 1
Joined: Wed Oct 01, 2014 6:36 am

Re: TMS dropping Data Direct!!! But no reason to panic.

Post by bdmc »

Hi,

Got your e-mail message this morning, and tried installing POSTman in Chrome.

Unfortunately, I keep getting 404 errors when I try going to that URL and to the /token URL.

Suggestions?

Am I not reading something important?


Thanks,
Brian

rkulagow
SD Staff
Posts: 933
Joined: Tue Aug 14, 2007 3:15 pm

Re: TMS dropping Data Direct!!! But no reason to panic.

Post by rkulagow »

I've updated the documentation to use the "data2" URL since that's what you can use right now; please check the updated docs and see if that helps.

pgbennett
Posts: 13
Joined: Sat Sep 27, 2014 2:03 pm

Re: TMS dropping Data Direct!!! But no reason to panic.

Post by pgbennett »

rkulagow wrote:
2014-10-01 02:11:46:{"response":"SCHEDULE_NOT_FOUND","code":7100,"serverID":"20140530.2","message":"The schedule you requested should be available. Post message to http:\/\/forums.schedulesdirect.org\/viewforum.php?f=6","datetime":"2014-10-01T02:11:39Z","stationID":"53251"}
OK, so this is a bug. What's actually happened is that this particular station has been marked as deleted upstream. I will change the error message to indicate that, and figure out why if it's deleted that it's still being included in the lineup.

If you tune to 590, what do you get?
Channel 590 is XFINITY Latino as per the Comcast lineup ( http://www.comcast.com/customers/clu/ch ... hx?clu=768# ). I cannot check it right now, I am at work, but I will check later. It must have been removed upstream in your server between Saturday and yesterday.
According to the 9old, existing) schedules direct page ( https://www.schedulesdirect.org/lineups ... A20453%3AX ) 590 is Local Origination and has xmltvid 53251.
This is one example of where schedules direct is incorrect in the line up. I do not care about this one, since I do not watch XFINITY Latino.
However the bigger problem is the schedule download should not terminate because of this issue. I would much rather have missing listings for one channel than have no listings because the download failed.

Peter

rkulagow
SD Staff
Posts: 933
Joined: Tue Aug 14, 2007 3:15 pm

Re: TMS dropping Data Direct!!! But no reason to panic.

Post by rkulagow »

OK, so there are two issues.

One is that the lineup is incorrect, and that should be handled through the normal process of opening a ticket at the Schedules Direct webpage. If you have additional examples of places where the lineup is incorrect, please include that in the ticket so that we can get an updated lineup from Comcast.

The second is the code terminating when it finds errors. At the moment, this is by design, because these are precisely the sorts of issues we want to catch during the beta phase. I believe I've fixed this particular bug now, so if you run the client again you should get a schedule.

pgbennett
Posts: 13
Joined: Sat Sep 27, 2014 2:03 pm

Re: TMS dropping Data Direct!!! But no reason to panic.

Post by pgbennett »

rkulagow wrote: I believe I've fixed this particular bug now, so if you run the client again you should get a schedule.
There seems to be a problem with the version checking. It will not run, even with --force-

peter@ubuntu1204x64:~/proj/sd/mfdb-json$ git pull
Already up-to-date.
peter@ubuntu1204x64:~/proj/sd/mfdb-json$ ./mfdb-json.php

Using beta server.
2014-10-02 15:57:17:Checking to see if we're running the latest client.
2014-10-02 15:57:18:***Version mismatch.***
2014-10-02 15:57:18:Server version: 0.13
2014-10-02 15:57:18:Our version: 0.14
2014-10-02 15:57:18:Exiting. Do you need to run 'git pull' to refresh?
2014-10-02 15:57:18:Restart script with --force to ignore mismatch.
peter@ubuntu1204x64:~/proj/sd/mfdb-json$
peter@ubuntu1204x64:~/proj/sd/mfdb-json$ ./mfdb-json.php --force

Using beta server.
2014-10-02 15:59:57:Checking to see if we're running the latest client.
2014-10-02 15:59:57:***Version mismatch.***
2014-10-02 15:59:57:Server version: 0.13
2014-10-02 15:59:57:Our version: 0.14
2014-10-02 15:59:57:Exiting. Do you need to run 'git pull' to refresh?
2014-10-02 15:59:57:Restart script with --force to ignore mismatch.
peter@ubuntu1204x64:~/proj/sd/mfdb-json$

rkulagow
SD Staff
Posts: 933
Joined: Tue Aug 14, 2007 3:15 pm

Re: TMS dropping Data Direct!!! But no reason to panic.

Post by rkulagow »

It's actually --x to "force". It's my super-sekrit undocumented command line argument which will go away when all bugs have been quashed.

:)

pgbennett
Posts: 13
Joined: Sat Sep 27, 2014 2:03 pm

Re: TMS dropping Data Direct!!! But no reason to panic.

Post by pgbennett »

rkulagow wrote:It's actually --x to "force". It's my super-sekrit undocumented command line argument which will go away when all bugs have been quashed.

:)
I tried with --x and got another error as follows.

array(6) {
["response"]=>
string(18) "SCHEDULE_NOT_FOUND"
["code"]=>
int(7100)
["serverID"]=>
string(10) "20140530.2"
["message"]=>
string(115) "The schedule you requested should be available. Post message to viewforum.php?f=6"
["datetime"]=>
string(20) "2014-10-02T16:35:28Z"
["stationID"]=>
string(5) "11006"
}
2014-10-02 16:35:42:{"response":"SCHEDULE_NOT_FOUND","code":7100,"serverID":"20140530.2","message":"The schedule you requested should be available. Post message to http:\/\/forums.schedulesdirect.org\/viewforum.php?f=6","datetime":"2014-10-02T16:35:28Z","stationID":"11006"}

11006 is Nickleodeon, channel 48. That should have worked.

Peter

Post Reply