Hubot/slack adapter times out? #282
Labels
bug
M-T: A confirmed bug report. Issues are confirmed when the reproduction steps are documented
Comments
|
I couldn't find other discussion about this earlier, now I have. :/ Here's the solution that I'm trying, which is replacing slack.coffee with this updated file: https://github.com/eriklindebratt/hubot-slack/blob/master/src/slack.coffee |
|
This is the reply that got me this info: hubotio/hubot#1013 (comment) |
|
About a day of using the updated slack.coffee files and I have had no problems. |
DEGoodmanWilson
added
bug
|
This should be fixed in #309 |
robertvilla
added a commit
to edina/edina-hubot
that referenced
this issue
Aug 5, 2016
Updated the hubot-slack module to the latest version. This will hopefully avoid the problem with hubot disconnecting from slack. Related to the following problems: * hubotio/hubot#1013 (comment) * slackapi/hubot-slack#282
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After about a day's worth of connected uptime, the hubot seems to crash. Sort of.
It ran flawlessly for days on end with the Slack adapter when I was running Ubuntu 14.04 on an older machine. Now on a newer machine running Linux Mint 17.3 Rosa, after about 12 to 24 hours it seems to stop working.
I'm using the same upstart script, but my node/hubot/adapter installations are all fresh ones.
I still get a green light for the bot in Slack, but he doesn't respond to commands, even ones that his own server
curls to him.Thoughts? The logs didn't seem to include anything useful. Is this a hubot problem or an adapter problem?
I got a similar problem with a cloud VM and the twitter adapter, but my only solution was to write a script to restart the server with
cron.The text was updated successfully, but these errors were encountered: