Outage this morning?

[Peter Hicks]

All,

Did anyone else see an outage between between 0758 and 0816 this morning?  I noticed a sharp dip in the number of message I received throughout this period and resultant data loss.

Peter

[Phil Wieland]

Yes indeed.

Message flow stopped 08:01
STOMP connection dropped 08:03 (Dropped by the Network Rail end.)
A few failed attempts to reconnect.
STOMP connection reconnected 08:08
But no messages at all until normal flow resumed at 08:17

There was a small initial spike in message rate above normal levels, but no-where near enough to fill in the sixteen minute gap.

Cheers,

Phil

[petermount]

Yes I did from 08:00-08:15 had nothing come through from NR.

[Peter Hicks]

Hi Phil (and everyone else)

From a subscriber's perspective, what's the impact on your particular application when there's feed instability?  It'll be really good to get some concrete examples of just how important these feeds are - that they're powering actual applications people use.

I'll start off... from an OpenTrainTimes perspective, if I lose TD data (and the messages disappear after 60 seconds), then my real-time maps, which are used by hundreds of people in industry, display incorrect data.  Signal aspects are wrong, berths contain 'stale' data and descriptions are left behind until another train refreshes the data in a berth.

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.

[petermount]

Same here for TD - my maps would also be out of sync until another train runs through a berth, but also the RTPPM display would appear to stall. That one would be an issue if the outage was at the end of the day due to the last values (~0200) get tweeted in the morning & there's a lot of people using those.

[Phil Wieland]

I can't claim hundreds of people, but my real-time maps are in constant use, and as with yours, the berth and signal states quickly become inaccurate.  (If the outage is longer than a few minutes I blank all the berths and signals.)

Also, not (yet) available to the public, I collect schedule data and TRUST movement records, including historical records going back two years.  An outage leaves a gap in this record, as well as making live displays inaccurate.

Cheers,

Phil

[Where-in-Sussex]

Currently running about 55-65 seconds behind reality. Can see duplicate digits due to missed steps right now

On Monday, November 23, 2015 at 9:14:28 AM UTC, Peter Hicks wrote:

[Phil Wieland]

Me too!

[Where-in-Sussex]

It keeps recovering then dropping back again after a few mins. Seeing this TTL of 60 seconds on the (incoming to Rockshore) TD feed again that Peter mentioned the other week?

[Peter Hicks]

I'm seeing that too - messages are coming in to me with a latency of around 60 seconds, which goes down to around 45 seconds but then rises to 60.  I'm also losing messages.

I've logged a support ticket.  Other than that, I'm sorry, my hands are tied.  It's impacting me as badly as everyone else :(

Peter

On Mon, 23 Nov 2015 at 18:18 Where-in-Sussex <swe...@gmail.com> wrote:

It keeps recovering then dropping back again after a few mins. Seeing this TTL of 60 seconds on the (incoming to Rockshore) TD feed again that Peter mentioned the other week?

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