Document recipes for fixing rabbitmq issue #465

Closed
rawray7 opened this Issue Feb 10, 2016 · 4 comments

Projects

None yet

3 participants

@rawray7
rawray7 commented Feb 10, 2016

i had a really hard time fixing the rabbitmq issue after i had misset /etc/hosts . just wanted to summarize my findings before i forget so that the next person doesn't have to beat their head against the wall so many times. this happened to me on a fresh digital ocean droplet when trying to follow the install instructions, so i hope it will help clarify for new zulip users:

i'm assuming you already installed zulip successfully, but now getting 400 or 500 errors and things like "Client was disconnected at a connection stage indicating a probable authentication ..." in /var/log/zulip/errors.log

  1. make sure you have "127.0.0.1 hostname" in /etc/hosts
  2. make sure you have ALLOWED_HOSTS = ['localhost','your.website.com'] in /etc/zulip/settings.py
  3. this assumes that 'supervisorctl restart all' is not solving the problem (at this stage)
  4. reinstall rabbit with:
    'apt-get purge rabbitmq-server',then 'apt-get install rabbitmq-server'
  5. fix the rabbit<=>zulip connection with:
    '/root/zulip/scripts/setup/configure-rabbitmq'
  6. now do 'supervisorctl restart all'

zulip team - please correct me if i'm wrong on any of these steps.

@rawray7 rawray7 closed this Feb 10, 2016
@timabbott timabbott reopened this Mar 20, 2016
@timabbott timabbott changed the title from fixing rabbitmq issue to Document recipes for fixing rabbitmq issue Mar 20, 2016
@timabbott timabbott added the priority label Mar 20, 2016
@timabbott
Member

We need to improve the troubleshooting docs for RabbitMQ, combining the data in this issue with the data from #194 (comment) and replacing my initial work in #377, which is definitely lacking in specificity.

@timabbott timabbott added this to the 2016 roadmap milestone Apr 29, 2016
@brainwane
Contributor

Relevant conversation on the developers' Zulip realm: https://zulip.tabbott.net/#narrow/stream/general/subject/rabbitmq/near/14201

@timabbott
Member

I'm pretty close to merging changes that cause Zulip to hardcode the rabbitmq nodename for new installations, which would mostly resolve this issue permanently.

@timabbott timabbott modified the milestone: Zulip roadmap, Old roadmap Nov 18, 2016
@timabbott timabbott added a commit that referenced this issue Nov 27, 2016
@andersk @timabbott andersk + timabbott install: Fix RabbitMQ node name if RabbitMQ is not installed.
This indirectly causes the RabbitMQ node name for new Zulip
installations to default to zulip@localhost, which would eliminate the
persistent problems we have had

Fixes #194, #465, #1375, #1751.

Signed-off-by: Anders Kaseorg <andersk@mit.edu>
78d6c3d
@timabbott
Member

Addressed by #2376.

@timabbott timabbott closed this Nov 27, 2016
@brockwhittaker brockwhittaker added a commit to brockwhittaker/zulip that referenced this issue Nov 30, 2016
@andersk @brockwhittaker andersk + brockwhittaker install: Fix RabbitMQ node name if RabbitMQ is not installed.
This indirectly causes the RabbitMQ node name for new Zulip
installations to default to zulip@localhost, which would eliminate the
persistent problems we have had

Fixes #194, #465, #1375, #1751.

Signed-off-by: Anders Kaseorg <andersk@mit.edu>
10d305e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment