Skip to content
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

Closed
xabgesagtx opened this issue May 8, 2016 · 6 comments
Closed

TwitterStreamAgent doesn't generate any events (anymore) #1490

xabgesagtx opened this issue May 8, 2016 · 6 comments

Comments

@xabgesagtx
Copy link

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.

{
  "filters": [
    "raspberrypi",
    "cubieboard",
    "huginn open source"
  ],
  "expected_update_period_in_days": "2",
  "generate": "counts"
}

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 bit

Restarting Agents::TwitterStreamAgent-9-f54cd3d03e1cd38e5269238e87f2b75fab01f648
--> Restarting Agents::TwitterStreamAgent-9-f54cd3d03e1cd38e5269238e87f2b75fab01f648 at 2016-05-08 22:21:35 +0200 <--
Restarting Agents::TwitterStreamAgent-9-f54cd3d03e1cd38e5269238e87f2b75fab01f648
--> Restarting Agents::TwitterStreamAgent-9-f54cd3d03e1cd38e5269238e87f2b75fab01f648 at 2016-05-08 22:21:55 +0200 <--
Restarting Agents::TwitterStreamAgent-9-f54cd3d03e1cd38e5269238e87f2b75fab01f648
Queuing schedule for every_5m
Killing Agents::TwitterStreamAgent-9-f54cd3d03e1cd38e5269238e87f2b75fab01f648
Queuing event propagation
...
Queuing event propagation
Queuing schedule for every_1m
Stopping AgentRunner...

Is there any way how I could get to the bottom of this? Other log levels, specific log files, common mistakes I could check.

@dsander
Copy link
Collaborator

dsander commented May 8, 2016

Hi @xabgesagtx,

it looks like the twitter stream API does have an outage at the moment, that would explain the continuous restarts of the TwitterStreamAgents. Stopping AgentRunner... only is triggered when the background processor received a UNIX signal to stop, did you manually kill it?
You should get your instance back up by running sudo bundle exec rake production:restart in /home/huginn/huginn.

@xabgesagtx
Copy link
Author

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

@xabgesagtx
Copy link
Author

xabgesagtx commented May 9, 2016

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.

@xabgesagtx xabgesagtx reopened this May 9, 2016
@dsander
Copy link
Collaborator

dsander commented May 9, 2016

Oh, you are right we totally missed that. Let's hope the fix is as easy as changing the URL.

dsander added a commit to dsander/huginn that referenced this issue May 9, 2016
The v1 endpoint was discontinued the end of april.

 huginn#1490
dsander added a commit to dsander/huginn that referenced this issue May 9, 2016
The v1 endpoint was discontinued at the end of april.

 huginn#1490
@dsander
Copy link
Collaborator

dsander commented May 9, 2016

@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.

@xabgesagtx
Copy link
Author

Yeah, it works. Thanks for fixing it, @dsander!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants