Cumulus Support

I actually wrote this yesterday and deleted it as I thought it was working ok, but I seem to have a problem with my Twitter updates...

It was set for 4 hours but I changed it yesterday to 60 minutes to see if it would update, it updated once and that was it so not sure whats happening...

Running version 188 b838 my upload is set to
Auto update
Use Active
Use ftp rename

And this has been working fine so not sure why the twitter updates have stopped unless of course it's twitter??
It last updated on the 6th August and since then it has only updated once more....

David in Grantown (daj) had a similar problem, and your post has now reminded me that Twitter has indeed been having problems (a DDOS).

Have you restarted Cumulus recently? I wonder if perhaps the problem at Twitter caused the updates to stop working even after they recovered - mine is working fine, but I restart every day. If a restart doesn't fix it, turn on the debug log - the responses from Twitter are logged in there.

Hi Steve, I wrote the message then did a search and noticed that somebody else had reported it...

Found this on twitter just now which was posted on the 6th August

We are defending against a denial-of-service attack, and will update status again shortly.

Update: the site is back up, but we are continuing to defend against and recover from this attack.

Update (9:46a): As we recover, users will experience some longer load times and slowness. This includes timeouts to API clients. We’re working to get back to 100% as quickly as we can.

Update (4:14p): Site latency has continued to improve, however some web requests continue to fail. This means that some people may be unable to post or follow from the website.

I'll give the restart a go...

Hi Steve, set twitter to update every hour it did the first one from the reboot but that was it, had an error show
ie
08/08/2009 19:19:35 : FTP Connect Timeout
08/08/2009 19:19:35 : FTP Connect Error, Error code = 426

So will reload it again and switch on the error log.

Also spotted this on Twitter blog
Due to defensive measures we’ve taken against the ongoing denial-of-service attack, some Twitter clients are unable to communicate with our API, and many users are unable to tweet via SMS.

We are working as quickly as possible to restore our full service.

tomcatuk wrote:08/08/2009 19:19:35 : FTP Connect Error, Error code = 426

That's an FTP error (it says that the ftp server didn't respond), so not directly related to the Twitter update, but...

Due to defensive measures we’ve taken against the ongoing denial-of-service attack, some Twitter clients are unable to communicate with our API

... that may well be the explanation.

It has been 2 days since my Twitter stopped taking updates from my station , I will just have to play a waiting game for a while

9Lives wrote:It has been 2 days since my Twitter stopped taking updates from my station , I will just have to play a waiting game for a while

I'm getting irregular updates. Seems to work when changing settings in the Cumulus internet options and fails after that ?

KetteringUK wrote:Think my Twitter has been a bit irregular since updating to the latest beta.

http://www.twitter.com/ketteringuk

Debug log is showing only this...

9142.5899 : 13:16:40 EW data line 07 FF FF FF FF FF FF FF FF
9142.5899 : 13:16:40 EW data line 08 FF FF FF FF FF FF FF FF
9143.4588 : 13:16:49 Updating Twitter
9143.4588 : http://twitter.com/statuses/update.xml
9143.4791 : 13:16:49 Twitter Response Code: 0 Response =
9143.5836 : 13:16:50 USB device is plugged in
9143.5836 : 13:16:50 request EW data block, written = 9, addr = 000000

KetteringUK wrote:I'm getting irregular updates. Seems to work when changing settings in the Cumulus internet options and fails after that ?

Yes, it could be that Cumulus doesn't handle Twitter's recent non-responsiveness properly, and restarting Cumulus or changing the settings kicks it off again. Until the next lack of Twitter response...

I'll have a look at the code to see what happens when Twitter doesn't respond.

Just an update Steve, I set Cumulus to update every hour and it has done so for the last 18 hours, so looks like the Twitter problem is over fingers crossed...
So its back to its normal update every 4 hours...

Thanks - I've just checked and they believe they had the problems sorted as of 20:00 UTC last night.

Look's like it's died again... my last post was Saturday 15th at 2.05pm and just before posting this I double checked and it's sent an update...
whoopeee!!

There blog reports:-
Trouble with Oauth and API clients 14 hours ago
Some users are running into trouble using third-party clients that rely on OAuth. We’re aware of this issue and working to resolve it.