Stations vanished from LDBWS

[George Goldberg]

An hour or so ago, all Southern stations (at least that's what it looks like to me having tried a few) disappeared from the LDBWS (including the national rail web site, e.g. [1]). Anyone else noticed this, or got any idea what's up? Other stations around the country still seem to be working just fine.

[1] http://ojp.nationalrail.co.uk/service/ldbboard/dep/ECR

George

[Peter Hicks]

Hi George

New Cross Gate is still there, physically too (I can see it from here).

It may be a duff station message that's causing a problem.  Have you checked Peter Mount's site?

Peter

--
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-t...@googlegroups.com.
To post to this group, send email to openrail...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[George Goldberg]

On 20 September 2016 at 13:38, Peter Hicks <peter...@poggs.co.uk> wrote:

New Cross Gate is still there, physically too (I can see it from here).

Interesting. I tried VIC, ECR and GTW and all had the same failure, so I was starting to wonder if Southern had just given up on running trains altogether!

 

It may be a duff station message that's causing a problem.  Have you checked Peter Mount's site?

The fact it's all stations along the same line seems to support that. uktra.in is showing departures for the affected stations, but I'm not sure which feed exactly it's powered by. LDBWS is giving me Error 500 in response to any SOAP request for the affected stations, which is not great really.

Given it affects the NRE web site too, is there anyone I can bother to try and get this fixed? Would be nice if it was working again in time for evening peak, as otherwise I'm going to have a lot of grumpy app users blaming me for it.

---

George

[Peter Hicks]

Apologies for top posting, but if it's affecting the NRE website too, you can be reasonably sure it'll be be fixed sharpish!

[petermount]

Hmmm... New Cross gate is there: https://uktra.in/station/?s=N

Looking at http://departureboards.mobi/ and typing in "new cr" also shows it & that list gets updated every morning from the darwin reference feed.

Also from my new timetable engine (uses the CIF timetable data)

$ curl -q 'http://api.area51.onl/timetable/search?key=************&term=new%20cr'

[{"tiploc":"NWCROSS","crs":"NWX","stanox":88410,"nlc":515000,"nlc_check":"Z","desc":"NEW CROSS","nlcdesc":"NEW CROSS"},{"tiploc":"NEWXGTE","crs":"NXG","stanox":87603,"nlc":534500,"nlc_check":"N","desc":"NEW CROSS GATE","nlcdesc":"NEW CROSS GATE"}]

Peter

[George Goldberg]

On 20 September 2016 at 14:04, petermount <peter...@gmail.com> wrote:

Hmmm... New Cross gate is there: https://uktra.in/station/?s=N

Looking at http://departureboards.mobi/ and typing in "new cr" also shows it & that list gets updated every morning from the darwin reference feed.

Also from my new timetable engine (uses the CIF timetable data)

$ curl -q 'http://api.area51.onl/timetable/search?key=************&term=new%20cr'

[{"tiploc":"NWCROSS","crs":"NWX","stanox":88410,"nlc":515000,"nlc_check":"Z","desc":"NEW CROSS","nlcdesc":"NEW CROSS"},{"tiploc":"NEWXGTE","crs":"NXG","stanox":87603,"nlc":534500,"nlc_check":"N","desc":"NEW CROSS GATE","nlcdesc":"NEW CROSS GATE"}]

Sorry, I didn't explain the problem very clearly. The stations are still in the list/reference data/etc, but when you try to get the departure board from LDBWS for them, you get Error 500, and if you try to look up their departures on the national rail web site, you get a generic "Something went Wrong" page.

The issue appears to be with the web service, as push port data isn't affected in any way that I've noticed.

--

George

[andrew.t...@gmail.com]

All,

The problem is being caused by an association on a particular service. It seems Southern made a (valid but rare) change to an association which is causing the issue. The problem should resolve itself shortly as the relevant service completes its journey.

We have identified a fix to prevent such a situation in the future which will be applied to the service at the next opportunity.

Andrew

[Nigel Mundy]

Maybe that's because NXG also has LOROL services?

--
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 an email to openraildata-talk@googlegroups.com.

[George Goldberg]

On 20 September 2016 at 14:59, <andrew.t...@gmail.com> wrote:

The problem is being caused by an association on a particular service. It seems Southern made a (valid but rare) change to an association which is causing the issue. The problem should resolve itself shortly as the relevant service completes its journey.

We have identified a fix to prevent such a situation in the future which will be applied to the service at the next opportunity.

Thanks very much for the information Andrew. It's good to know the issue has been identified.

--

George

[George Goldberg]

On 20 September 2016 at 14:59, <andrew.t...@gmail.com> wrote:

The problem is being caused by an association on a particular service. It seems Southern made a (valid but rare) change to an association which is causing the issue. The problem should resolve itself shortly as the relevant service completes its journey.

Oh dear, there seems to be another service moving through (from Victoria?) with the same problem. I guess it's going to be a recurring thing until there's an opportunity to apply that fix to the system.

--

George

[andrew.t...@gmail.com]

Yes, I'm afraid so. The intention at the moment (subject to testing and approval) is to apply the fix tomorrow (Thursday 22nd) so hopefully this will be not re-occur after that.

Andrew

[andrew.t...@gmail.com]

The fix was applied this morning. Please advise if you see any re-occurrence of the issue.