-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TwitterStreamAgent doesn't generate any events (anymore) #1490
Comments
Hi @xabgesagtx, it looks like the twitter stream API does have an outage at the moment, that would explain the continuous restarts of the |
Wow. This is a really long outage. I guess this explains the problem. I only stopped and started huginn with the bundle commands. I was just confused that after starting huginn "Stopping AgentRunnner..." was the last line in the log |
On the other hand, I may have been a little too quick to close the ticket. Retiring the old API could be an explaination as well. The status page seems to be broken too The code of the agent seems to use the API version v1. |
Oh, you are right we totally missed that. Let's hope the fix is as easy as changing the URL. |
The v1 endpoint was discontinued the end of april. huginn#1490
The v1 endpoint was discontinued at the end of april. huginn#1490
@xabgesagtx Thanks for digging into this! I was wondering about the long "downtime" but did not think about API deprecations. The latest master build should work again. |
Yeah, it works. Thanks for fixing it, @dsander! |
I've issues getting the TwitterStreamAgent to work or keep it working. For several days it worked perfectly but now it doesn't generate any events anymore. The check is running but no events are created. I don't understand why and I cannot find any error messages. I tried to reauthenticate with twitter but that didn't change anything.
The huginn application runs in production and I started it with this command.
sudo bundle exec rake production:start
The configuration of the agent.
All other agents are working fine and are creating events as expected.
I've found this in
log/jobs-1/current
, what made me worry a little bitIs there any way how I could get to the bottom of this? Other log levels, specific log files, common mistakes I could check.
The text was updated successfully, but these errors were encountered: