Cumulus Support

I saw this in 1.8.8 and some of the 1.8.9 betas

every now and then twitter stops, when I first saw it, i had home network issues, so suspected it was due to a failed update attempt. but the web site just carried on

now i have seen twitter updates stop 3 or 4 times in the past 5-6 weeks,
update resume after a cumulus restart

any thoughts,
it is me, my network, my broadband or a problem with a failed twitter update in cumulus causing a jam

Twitter is not that reliable to begin with as a remotely posted service. Many people sending weather data to Twitter have that type of issue using all types of weather software and tools.

If you post duplicates, they will get rejected as well. So if you don't have a time element included in your content, you may see posts dropped as well.

My twitter has been working reliably since setting it up and has 570 odd tweets to it's name.

My twitter only updates once every two hours, I reckon anyone wanting to follow it doesn't want repeated tweets telling them temperature has changed by 0.1'C or that we have had 0.3mm of rain.

My tweets stop for a while sometimes, and I know others have the same problem. I never have to restart Cumulus to get them going again, so I put it down to a problem at Twitter. It's possible that some sort of problem may cause it to get stuck requiring a restart; if you want to run with the debug log turned on it may give a clue when it happens again.

here goes the debug log (twitter bits only)

1224.04313 : 22:52:07 Updating Twitter
1224.04313 : http://twitter.com/statuses/update.xml
1224.06719 : 22:52:09 Twitter Response Code: 200

1260.04313 : 23:52:07 Updating Twitter
1260.04313 : http://twitter.com/statuses/update.xml
1260.06766 : 23:52:09 Twitter Response Code: 200

1296.04313 : http://twitter.com/statuses/update.xml
1296.04313 : 00:52:07 Updating Twitter


1332.04313 : 01:52:07 Updating Twitter
1332.04313 : http://twitter.com/statuses/update.xml
1332.04313 : Twitter update error: HTTP component TwitterHTTP is busy


if i read this right, the twitter update at 00:52:07 did not complete
and ever twitter update attempt afterward fails with "Twitter update error: HTTP component TwitterHTTP is busy"

species5618 wrote:if i read this right, the twitter update at 00:52:07 did not complete
and ever twitter update attempt afterward fails with "Twitter update error: HTTP component TwitterHTTP is busy"

There don't appear to be any timeout settings on the HTTP component. I'll see if I can find out what is supposed to happen. Possibly I am supposed to run my own timer and then abort if it times out.

steve wrote:Possibly I am supposed to run my own timer and then abort if it times out.

Yes, it appears that this is how it is supposed to work. I'll sort something out.