Connection timed out 110?

[Darren Cook]

I've two machines running phirehose, each with their own twitter
account. They've been going for literally years, with hardly any
maintenance. I noticed both of them stopped today, and both are 100%
failing to connect, e.g. with:

TCP failure 4 of 20 connecting to stream: Connection timed out (110)

It has the increasing time-outs for sleep, and I cannot see that any
error codes are coming from Twitter.

Googling I can see news items about threats to kill off twitter streams
in April 2018, then again in July 2018. But it was working until
yesterday. The docs don't appear to mention anything, and I'm
comfortably below the 400 keyword track limit.

Is anyone else seeing this? I wonder if it is one of those things that
will sort itself if i just leave it for a few more hours...

Darren

[Adam]

We've seen this too - are your servers in AWS London (eu-west-2)? Seems there's a routing issue which started around 13:45UTC and is continuing now (21:50) I've raised a ticket with them...

[Darren Cook]

> We've seen this too - are your servers in AWS London (eu-west-2)? Seems there's
> a routing issue which started around 13:45UTC and is continuing now (21:50) I've
> raised a ticket with them...

Thanks Adam. Both servers were in AWS eu-west! It seems it fixed itself
after midnight GMT.

Good to know rumours of Twitter streaming's demise are not true (yet). :-)

Darren

[Gareth Knight]

Does anyone ** know ** what their plans are, in any shape or form?

---

Too brief? Here's why! http://emailcharter.org

--

---
You received this message because you are subscribed to the Google Groups "Phirehose Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phirehose-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.