-
Notifications
You must be signed in to change notification settings - Fork 4
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
Hubot doesn't start anymore (I guess after updates) #11
Comments
Could you please try to pin the package to something <2 because version 2 supports only See #10 Please let me know if that solves your issue. |
Thanks for your work so far. I'm having the exact same problem as Sascha and tried to pin I'm running rocketchat and rocketchat-hubot including script using docker-compose. How would I pin the package to 1.3.1 correctly? My syntax:
|
Yes that should be correct, but maybe the hubot-rocketchat container is not correct. In our old setup we used Can you by any chance upgrade to the new hubot? |
I tried all the different combinations in my docker-compose.yml, none worked:
|
|
I think the docker image for "rocketchat/hubot-rocketchat:latest" is outdated. For our setup we use the bot like this: We've cloned https://github.com/RocketChat/hubot-rocketchat-boilerplate and adjusted external-scripts.json and package.json and build the container by ourself.
I don't know if it would be helpful if I build and publish the container for you guys because I am not quite sure if this is a good solution. |
I get pretty far with it, but it ends with a timeout:
|
Okay, by giving hubot some time to start later with:
I finally can start Hubot, but RSS-rolf is not happy:
|
Okay, it seems, that it works, but it lost all feeds from before and it doesn't show up in hubot help. But I guess the main-problem is solved. |
The feeds are probably lost because the redis database lost its data. The broken help will be tracked in #14 |
I want to restart the hubot via docker-compose, but It never goes live. It worked till some weeks ago though. I guess it doesn't work anymore because of your updates. If I can help debug it, let me know. Here is the log file:
The text was updated successfully, but these errors were encountered: