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

Print a better error if mongo isn't running #997

Closed
crobinson42 opened this issue Oct 5, 2016 · 1 comment
Closed

Print a better error if mongo isn't running #997

crobinson42 opened this issue Oct 5, 2016 · 1 comment

Comments

@crobinson42
Copy link

I did a fresh git clone, npm install (node v4.4) and setup my env vars correctly - I see this loop over and over with no description of what's failing:

admin@jenkins:~/strider$ ./bin/strider 
1887 forked
1887 died 1 null
1900 forked
^C
admin@jenkins:~/strider$ 
@crobinson42
Copy link
Author

Solution

It turns out this is because mongo was not running..

a better error message should be displayed.

@knownasilya knownasilya reopened this Oct 5, 2016
@knownasilya knownasilya changed the title Starting Strider: died 1 null - loop Print a better error if mongo isn't running Feb 20, 2017
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