ZZZ-28.2E-DEFAULT - schedules unaccessible

Issues relating to lineups should be posted here.

ZZZ-28.2E-DEFAULT - schedules unaccessible

Postby karamike » Thu Jan 17, 2019 3:04 pm

Hi,

I have raised the following topic at various places (perhaps not the right ones?) for weeks but had no reaction so far. I think that I can now demonstrate that the error is not at my end.

The problem is that I can not request a schedule (or the MD5 thereof) from a station that should be part of my configured lineup ZZZ-28.2E-DEFAULT. I get error #7030 ("You have requested a schedule which is not in any of your configured lineups.")

However within the same request I successfully retrieve the schedule (or the MD5 thereof) of a station from another configured satellite lineup (ZZZ-19.2E-DEFAULT).

For this reason I assume that there is a problem with the underlying data of lineup ZZZ-28.2E-DEFAULT.

I've attached a debug output for the following sequence

    - request a token
    - request the user status - to show that ZZZ-19.2E-DEFAULT and ZZZ-28.2E-DEFAULT are configured lineups
    - request the station list of lineups ZZZ-19.2E-DEFAULT and ZZZ-28.2E-DEFAULT - to show that the stationIDs 67146 (Arte - 19.2E) and 69387 (BBC One HD - 28.2E) are part of their respective lineup (see line 3990 and 14475).
    - request the MD5s of the schedules of station 67146 and 69387 in a single request

As you can see in the shortend debug output below:
    - for 67146 (19.2E) I get the correct response
    - for 69387 (28.2E) I get an error message

There are three other noteworthy facts:
    - The station listing of lineup ZZZ-28.2E-DEFAULT is malformed. Line 15871 of the attached log shows a "[]" where a "{ .... }" should be. This does not occur in the other lineups.
    - The lineup itself is nearly 4 years old. Especially for a satellite lineup this seems an extremly long time.
    - The 'lastModified' date of the error message is 1970-1-1 00:00:00 (Unix time 0) and it has a faked MD5 ("Cafe Deed Beef") which makes me believe that his is some kind of an "catch all exceptions" answer.

Here is the shortend reply for the MD5 request:

Code: Select all
url: https://json.schedulesdirect.org/20141201/schedules/md5
verb: post
headers: {'User-Agent': 'sdjsonclient.py/0.2', 'token': 'dc32054622241c7e4bf0b7eacc386e66'}
data: [{'stationID': '67146'}, {'stationID': '69387'}]
status code: 200
headers: {'Date': 'Thu, 17 Jan 2019 21:55:46 GMT', 'Content-Type': 'application/json;charset=UTF-8', 'Transfer-Encoding': 'chunked', 'Connection': 'keep-alive', 'Server': 'nginx/1.10.3 (Ubuntu)', 'Vary': 'Accept-Encoding', 'Schedulesdirect-Serverid': '20141201.web.X', 'X-Frame-Options': 'SAMEORIGIN', 'X-Content-Type-Options': 'nosniff', 'X-XSS-Protection': '1; mode=block', 'Content-Encoding': 'gzip'}
json:
{
    "67146": {
        "2019-01-17": {
            "code": 0,
            "message": "OK",
            "lastModified": "2019-01-17T21:18:39Z",
            "md5": "26nDbyIuFfKVMaa1M0Ltqg"
        },
        "2019-01-18": {
            "code": 0,
            "message": "OK",
            "lastModified": "2019-01-17T21:18:39Z",
            "md5": "ylduOEN8G1G621y1dy57yA"
        },
        ...
    },
    "69387": {
        "2019-01-17": {
            "stationID": "69387",
            "serverID": "20141201.web.X",
            "code": 7030,
            "message": "You have requested a schedule which is not in any of your configured lineups.",
            "lastModified": "1970-01-01T00:00:00Z",
            "md5": "CAFEDEADBEEFCAFEDEADBE",
            "date": "2019-01-17"
        },
        "2019-01-18": {
            "stationID": "69387",
            "serverID": "20141201.web.X",
            "code": 7030,
            "message": "You have requested a schedule which is not in any of your configured lineups.",
            "lastModified": "1970-01-01T00:00:00Z",
            "md5": "CAFEDEADBEEFCAFEDEADBE",
            "date": "2019-01-18"
        },
        ...
    }
}


What did I miss? Any ideas how to fix this?

Michael
Attachments
schedule_prob.txt
(572.14 KiB) Downloaded 13 times
karamike
 
Posts: 4
Joined: Wed Jan 02, 2019 1:15 pm

Return to Lineup Issues

Who is online

Users browsing this forum: No registered users and 1 guest