Cumulus Support

Hello,

Recently i have started experiancing problems with Posting updates to twitter, about a fortnight ago i noticed the updates had stopped so i had a look through the logs and could find no errors relating to this, so i removed the authentication keys from the configuration file and also removed the username and password and disabled twitter, i rebooted Cumulus and entered my twitter details once more, i waited around 5-10 mins and checked the config file and a new set of authentication keys had been populated and updates began.

About a week later updates stopped again, i looked in the error logs nothing.

Why has this suddenly started happening, has twitter put a cap on the amount of updates you can send in a certain time frame or something? I currently post updates once every 30 minutes but right now there are no updates being posted at all as it appears to be broken.

If you could help me out i would be greatful.

Cheers
Rich

Presumably just restarting Cumulus doesn't get it going again? If you turn on the debug log, then additional messages will be logged to the diags file (and there may also be messages in the debug.log file itself) which may help diagnose the problem.

Restarting Cumulus does nothing.

I will turn the debug logs on and see what is what will wait for a few hours afer and post the log here.

Will speak again later today.

richardmhowell wrote:
Why has this suddenly started happening, has twitter put a cap on the amount of updates you can send in a certain time frame or something? I currently post updates once every 30 minutes but right now there are no updates being posted at all as it appears to be broken.

I post every 5 minutes, no problems

Steve,

As promised attached is my debug log file i cant see anything in there but something might stand out to you.

Rich

I need the current diags file, please.

Is that cumulus.ini?

It's the latest file in the diags folder (cumulus.009).

Here we go https://dl.dropbox.com/u/42514355/cumulus.009

Thanks, you should remove that file now, it has your tokens in it; I'd assumed you had restarted Cumulus so the request for tokens wouldn't be in the log.

From a quick scan, it doesn't look like it's doing much after getting the tokens, but I don't know why. It starts the update thread but isn't talking to Twitter (or not getting a response). I'll have a more detailed look later.

steve wrote:Thanks, you should remove that file now, it has your tokens in it; I'd assumed you had restarted Cumulus so the request for tokens wouldn't be in the log.

From a quick scan, it doesn't look like it's doing much after getting the tokens, but I don't know why. It starts the update thread but isn't talking to Twitter (or not getting a response). I'll have a more detailed look later.

That is what i don't get, i noticed that the tokens were there becuase i had searched the forums and done some troublshooting before i came to you so i knew how the system (kinda) worked, what i don't get is why Cumulus is able to request the tokens but then not pass my status updates back to Twitter, it is like it is being blocked somewhere along the line.

It looks like some kind of problem occurred the first time it tried to update Twitter, so before the debug log was on. From then on it 'got stuck'. I put some changes into 1.9.3 to try to cope with this situation, so you could try that: https://cumulus.hosiene.co.uk/viewtopic.php?f=2&t=7341

If you install 1.9.3 and then before you run it edit cumulus.ini, and in the [Station] section add a line

Logging=1

that will turn on the extra logging to the diags file from start up, so we should be able to see what's going on, whether or not 1.9.3 fixes the problem.

Steve,

Quick question, before i install this will it over right my current settings?

Rich

Quick answer: no.

Okay version 1.9.3 1044 is now installed with Logging=1 active in my configuration file.

Do we just need to wait now?

Let me know what you need.

Rich