-
-
Notifications
You must be signed in to change notification settings - Fork 229
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
Error: unable to connect to node rabbit: nodedown #13
Comments
Are you using |
rabbitmqctl setup errors are now supressed. Can you try again and see if Zulip is reachable on your host (should be https://127.0.0.1)? |
The certificates are now generated automatically, if they don't exist in the data volume. |
@galexrt Thank you for your reply. Yes, I use the I will try again and reply later. |
+1 I got the same problem
|
@galexrt
|
My logs is the same Added zulip's log.
|
It seems like a database problem. I'm working on a fix for it. |
I fixed the error, as I thought it was a problem with the Please remove and/or repull both images! For me it's working now, please tell me if it's working for you now too. BTW: If you start the container and it doesn't return with a exit code, then everything should be okay. |
@galexrt |
@galexrt Also, I can't login zulip by the |
@njuaplusplus I create a new ticket for your problem with the login. I'll close this ticket now, as it seems to work again. :) |
@njuaplusplus See #17 and #16. |
I have the log like this:
Is Rabbitmq running well? Is there any problem in the contact between Rabbitmq and Zulip ? or is everything fine? |
@toan2948 As written above in this issue, the errors are okay because the Rabbitmq is already correctly setup. The "errors" mean that rabbitmq could not be reconfigured which is as written okay in that case. Please use your created issue for questions and/or issues you experience. This issue is from Oct 21, 2015.. |
Excuse me :). I thought the issues should be in the same topics. |
Hi, I met with some problem. The zulip fail to work.
And it's the logs.
The text was updated successfully, but these errors were encountered: