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

Can't get HuBot started. #551

Closed
ghost opened this Issue Jul 26, 2013 · 8 comments

Comments

Projects
None yet
6 participants
@ghost

ghost commented Jul 26, 2013

I have it installed correctly, just not sure what to do now...this is what happens when I do bin/hubot

Hubot> [Fri Jul 26 2013 18:06:08 GMT-0500 (CDT)] WARNING The HUBOT_AUTH_ADMIN environment variable is set not going to load roles.coffee, you should delete it
[Fri Jul 26 2013 18:06:08 GMT-0500 (CDT)] ERROR [Error: Redis connection to localhost:6379 failed - connect ECONNREFUSED]
[Fri Jul 26 2013 18:06:08 GMT-0500 (CDT)] ERROR [Error: Redis connection to localhost:6379 failed - connect ECONNREFUSED]
[Fri Jul 26 2013 18:06:09 GMT-0500 (CDT)] ERROR [Error: Redis connection to localhost:6379 failed - connect ECONNREFUSED]
[Fri Jul 26 2013 18:06:10 GMT-0500 (CDT)] ERROR [Error: Redis connection to localhost:6379 failed - connect ECONNREFUSED]
[Fri Jul 26 2013 18:06:11 GMT-0500 (CDT)] ERROR [Error: Redis connection to localhost:6379 failed - connect ECONNREFUSED]
[Fri Jul 26 2013 18:06:13 GMT-0500 (CDT)] ERROR [Error: Redis connection to localhost:6379 failed - connect ECONNREFUSED]
[Fri Jul 26 2013 18:06:17 GMT-0500 (CDT)] ERROR [Error: Redis connection to localhost:6379 failed - connect ECONNREFUSED]

EDIT: Removing redis-brain.coffee from hubot-scripts.json fixed the redis connection error.

@tombell

This comment has been minimized.

Contributor

tombell commented Jul 26, 2013

Locally you will need a Redis server running if you're using redis-brain.coffee.

@spajus

This comment has been minimized.

Contributor

spajus commented Jul 27, 2013

How about having brainless Hubot by default? Extra requirements makes it harder to start using it, and you can always add a brain later when you need it.

@technicalpickles

This comment has been minimized.

Contributor

technicalpickles commented Jul 27, 2013

Potentially. There's a hard balance between easier to use out of the box
and more usable out of the box. A robot with a brain is a lot more useful.

Maybe can default to the file brain. Or add better error handling to redis
brain.

@tombell, how did your testing of an interactive generator go? Would be
useful for things like this.

On Friday, July 26, 2013, Tomas Varaneckas wrote:

How about having a no-brainer Hubot as a default? Extra requirements makes
it harder to start using it, and you can always add a brain later when you
need it.


Reply to this email directly or view it on GitHubhttps://github.com//issues/551#issuecomment-21657852
.

  • Josh

@ghost ghost closed this Jul 27, 2013

@noahlz

This comment has been minimized.

noahlz commented Oct 15, 2013

Worthwhile to add a comment about this to the README, no?

@sundaymtn

This comment has been minimized.

sundaymtn commented Dec 19, 2013

Getting Started with Hubot needs to mention the redis-server install before the following:
"You now have your own functional hubot! There's a bin/hubot command for convenience, to handle installing npm dependencies, loading scripts, and then launching your hubot."

@noahlz

This comment has been minimized.

noahlz commented Dec 20, 2013

So the "installing npm dependencies" implies "such as Redis?" Got it.

@technicalpickles

This comment has been minimized.

Contributor

technicalpickles commented Dec 20, 2013

Related:

If anyone that has run into this can take a few moments to suggest specific improvements that would have covered their problems, that would be super useful 👍

@edsu

This comment has been minimized.

edsu commented Oct 2, 2014

I ran into this too. My suggestion:

a) redis should be listed as a dependency
b) hubot shouldn't have redis-brain enabled by default
c) you ignore this comment and go back to whatever you were doing

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment