codalab / codalab/codabench

Can't change rabbit credentials

Open
#1,337 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug
Dominant language
Python
Stars
176
Forks
74
Avg merge
5d 3h
Merged PRs (30d)
21

Description

I recently tried to change all of the default credentials in the .env file on my own instance and had some problems so I am trying again. I started by changing the flower credentials and it worked well.
Now I tried to change the credentials for rabbit and it simply did not change anything and the default credentials still worked.

Every time I change the credentials I do docker-compose down --volumes and then docker compose up -d
These are the current variables. the passwords are 20 characters long.

RABBITMQ_HOST=rabbit
RABBITMQ_DEFAULT_USER=rabbit-username
RABBITMQ_DEFAULT_PASS='...REDACTED...'
RABBITMQ_MANAGEMENT_PORT=15672
RABBITMQ_PORT=5672
WORKER_CONNECTION_TIMEOUT=100000000 # milliseconds

FLOWER_PUBLIC_PORT=5555

FLOWER_BASIC_AUTH='root:...REDACTED...'

Here are the rabbit logs, I will add more if you tell me which you need.

rabbit-1          | 2024-02-16 10:59:07.512346+00:00 [info] <0.2095.0> accepting AMQP connection <0.2095.0> (172.24.0.7:37626 -> 172.24.0.4:5672)
rabbit-1          | 2024-02-16 10:59:07.513567+00:00 [error] <0.2095.0> Error on AMQP connection <0.2095.0> (172.24.0.7:37626 -> 172.24.0.4:5672, state: starting):
rabbit-1          | 2024-02-16 10:59:07.513567+00:00 [error] <0.2095.0> AMQPLAIN login refused: user 'rabbit-username' - invalid credentials
rabbit-1          | 2024-02-16 10:59:07.513711+00:00 [info] <0.2095.0> closing AMQP connection <0.2095.0> (172.24.0.7:37626 -> 172.24.0.4:5672)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the .env variables with the RabbitMQ service definition in the docker-compose configuration, then reproduce the credential change using the reported teardown and startup commands. Done means the intended credentials are accepted, the default credentials are rejected, and the relevant RabbitMQ logs no longer report invalid credentials.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose, rabbitmq
Domain
authentication, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.