Trouble accessing today's schedule?

97 views
Skip to first unread message

Tom Gowland

unread,
Dec 24, 2017, 8:25:31 AM12/24/17
to A gathering place for the Open Rail Data community
Hi all,

Just wondered if anyone else was having problems accessing  https://datafeeds.networkrail.co.uk/ntrod/CifFileAuthenticate?type=CIF_ALL_FULL_DAILY&day=toc-full today?

I am getting the following:

<Error>
    <Code>AccessDenied</Code>
    <Message>Request has expired</Message>
    <Expires>2017-12-24T13:22:56Z</Expires>
    <ServerTime>2017-12-24T13:23:39Z</ServerTime>
    <RequestId>D8D6551B1DB226D9</RequestId>
    <HostId>
      LsEG8TWAxc+jVsDy6QKDl/igYrPtPl8ugNykjdtnB8mnxYQOVLtpFGaIuZAi4dIXflVDh8aCYSQ=
    </HostId>
</Error>

When I log into the datafeeds site my account is still showing as active and I am subscribed to everything...

Thanks,
Tom

Steve Ardagh-Walter

unread,
Dec 24, 2017, 8:37:17 AM12/24/17
to A gathering place for the Open Rail Data community
Hi Tom

Yes, I've had the same.     I suspect nothing may change for the next few days ...

Steve

Tom Gowland

unread,
Dec 24, 2017, 8:39:01 AM12/24/17
to A gathering place for the Open Rail Data community
Hi Steve,

Thanks for letting me know.
I suspect you're probably right!

Tom 

Peter Hicks (Poggs)

unread,
Dec 24, 2017, 8:43:49 AM12/24/17
to Tom Gowland, A gathering place for the Open Rail Data community
Hi Tom

> On 24 Dec 2017, at 13:25, Tom Gowland <tkg...@gmail.com> wrote:
>
> Hi all,
>
> Just wondered if anyone else was having problems accessing https://datafeeds.networkrail.co.uk/ntrod/CifFileAuthenticate?type=CIF_ALL_FULL_DAILY&day=toc-full today?

I’m having the same issue as you.

When you call CifFileAuthenticate, you get a redirect to an Amazon S3 signed URL which is valid for server time + 2 minutes or similar. It looks like clock drift on the server which requests the signed URLs has caused it to make a request with an expiry time that’s now in the past. At a guess, the server time is running two minutes behind reality.

You may have to resign yourself to the fact this might not get picked for several days, given Christmas.

Please - log a ticket though - and anyone else who’s impacted.

Cheers,


Peter


--

OpenTrainTimes Ltd. registered in England and Wales, company no. 09504022.
Registered office: 13a Davenant Road, Upper Holloway, London N19 3NW

Tom Gowland

unread,
Dec 24, 2017, 8:57:54 AM12/24/17
to A gathering place for the Open Rail Data community
Hi Peter,

Thanks a lot for the explanation.
Yes, already resigned myself to that... Just slightly concerned that my account may now be moved to "inactive" since the last time I downloaded a schedule file was 30 days ago from tomorrow and I seem to remember reading that no usage in 30 days would lead to an account being deactivated.
Unfortunately, my system wasn't ready to download daily schedules until today and I had just been using the schedule I downloaded nearly a month back for testing purposes....

Bad timing I guess, but I've explained it all in the ticket I've just submitted so maybe they'll be kind... It is Christmas after all!

Thanks,
Tom

Phil Wieland

unread,
Dec 24, 2017, 10:01:51 AM12/24/17
to A gathering place for the Open Rail Data community
Looks like someone has rebooted something, and I've just downloaded the missing timetable data.

Phil

Peter Mount

unread,
Dec 24, 2017, 10:10:41 AM12/24/17
to Phil Wieland, openraildata-talk
That would explain the alerts I just received as the nr feeds stopped for about 5 minutes

--
You received this message because you are subscribed to the Google Groups "A gathering place for the Open Rail Data community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openraildata-talk+unsubscribe@googlegroups.com.
To post to this group, send email to openraildata-talk@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Tom Gowland

unread,
Dec 24, 2017, 10:29:30 AM12/24/17
to A gathering place for the Open Rail Data community
Excellent! 

Merry Christmas everyone!

WantStuff

unread,
Dec 27, 2017, 5:20:47 AM12/27/17
to A gathering place for the Open Rail Data community
I had the same again today (27th) at 06:15. I assume it was resolved by 06:20 as I didn’t get further alerts - my code retries every 5 mins.

Martin

Brad Gyton

unread,
Dec 27, 2017, 9:29:13 AM12/27/17
to A gathering place for the Open Rail Data community
I've also got the same issue today. A 403 is returned when attempting to download any CIF

Tom Gowland

unread,
Dec 27, 2017, 9:30:53 AM12/27/17
to A gathering place for the Open Rail Data community
Yep, I've got the same issue again today too.


On Sunday, December 24, 2017 at 1:25:31 PM UTC, Tom Gowland wrote:

Brad Gyton

unread,
Dec 27, 2017, 10:44:36 AM12/27/17
to A gathering place for the Open Rail Data community
It seems they have since rebooted NROD and the CIF download is now working again


On Sunday, December 24, 2017 at 1:25:31 PM UTC, Tom Gowland wrote:

Phil Goodman

unread,
Jan 1, 2018, 12:31:34 PM1/1/18
to A gathering place for the Open Rail Data community
Hi all

Happy new year! 

Logging back in after a long break to find we encountered similar issues - and as a result we're missing the CIF Schedule update file for that date (23.12.2017 - reference 'DFROC1A').  

As it's too far back to get from the website, would anyone be able to make this available for me to fill the gap, please?

Many thanks
Phil
Reply all
Reply to author
Forward
0 new messages