pardahlman / docker-rabbitmq-cluster Goto Github PK

Each node have their own management-plugin, but they are not configured, fortunately, you can configure it.

Hi, I've cloned and docker-compose up and got this error logs

rabbitmq2_1 | RABBITMQ_ERLANG_COOKIE env variable support is deprecated and will be REMOVED in a future version. Use the $HOME/.erlang.cookie file or the --erlang-cookie switch instead.
rabbitmq2_1 | Stopping rabbit application on node rabbit@rabbitmq2 ...
rabbitmq2_1 | Error: unable to perform an operation on node 'rabbit@rabbitmq2'. Please see diagnostics information and suggestions below.
rabbitmq2_1 |
rabbitmq2_1 | Most common reasons for this are:
rabbitmq2_1 |
rabbitmq2_1 | * Target node is unreachable (e.g. due to hostname resolution, TCP connection or firewall issues)
rabbitmq2_1 | * CLI tool fails to authenticate with the server (e.g. due to CLI tool's Erlang cookie not matching that of the server)
rabbitmq2_1 | * Target node is not running
rabbitmq2_1 |
rabbitmq2_1 | In addition to the diagnostics info below:
rabbitmq2_1 |
rabbitmq2_1 | * See the CLI, clustering and networking guides on https://rabbitmq.com/documentation.html to learn more
rabbitmq2_1 | * Consult server logs on node rabbit@rabbitmq2
rabbitmq2_1 | * If target node is configured to use long node names, don't forget to use --longnames with CLI tools
rabbitmq2_1 |
rabbitmq2_1 | DIAGNOSTICS
rabbitmq2_1 | ===========
rabbitmq2_1 |
rabbitmq2_1 | attempted to contact: [rabbit@rabbitmq2]
rabbitmq2_1 |
rabbitmq2_1 | rabbit@rabbitmq2:
rabbitmq2_1 | * connected to epmd (port 4369) on rabbitmq2
rabbitmq2_1 | * epmd reports: node 'rabbit' not running at all
rabbitmq2_1 | no other nodes on rabbitmq2
rabbitmq2_1 | * suggestion: start the node
rabbitmq2_1 |
rabbitmq2_1 | Current node details:
rabbitmq2_1 | * node name: 'rabbitmqcli-45-rabbit@rabbitmq2'
rabbitmq2_1 | * effective user's home directory: /var/lib/rabbitmq
rabbitmq2_1 | * Erlang cookie hash: gnzLDuqKcGxMNKFokfhOew==
rabbitmq2_1 |
rabbitmq3_1 | RABBITMQ_ERLANG_COOKIE env variable support is deprecated and will be REMOVED in a future version. Use the $HOME/.erlang.cookie file or the --erlang-cookie switch instead.
rabbitmq3_1 | Stopping rabbit application on node rabbit@rabbitmq3 ...

and idea why is that?

I get error: standard_init_linux.go:211: exec user process caused "no such file or directory"

`CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

80d25faa4760 haproxy:1.7 "/docker-entrypoint.…" 24 seconds ago Exited (1) 17 seconds ago docker_haproxy_1

4411feb2a4db rabbitmq:3.8-management "/usr/local/bin/clus…" 26 seconds ago Exited (1) 23 seconds ago docker_rabbitmq2_1

9d56fdd8ad9b rabbitmq:3.8-management "/usr/local/bin/clus…" 26 seconds ago Exited (1) 23 seconds ago docker_rabbitmq3_1

01de45c82bbd rabbitmq:3.8-management "docker-entrypoint.s…" 27 seconds ago Up 25 seconds 4369/tcp, 5671-5672/tcp, 15671-15672/tcp, 25672/tcp docker_rabbitmq1_1
`

hello

after editing .env file, I run the commands and I see error logs cause of invalid auth

cleanup docker
docker rm -v $(docker ps -a -f status=exited -q)
docker rmi $(docker images -f "dangling=true" -q)
docker system prune
docker volume prune

then running your repo cluster
docker-compose up -d

I see logs below (docker-compose logs -f)

rabbitmq3_1  | 2019-02-13 10:50:08.730 [info] <0.823.0> accepting AMQP connection <0.823.0> (172.25.0.5:49252 -> 172.25.0.4:5672)
rabbitmq3_1  | 2019-02-13 10:50:08.774 [error] <0.823.0> Error on AMQP connection <0.823.0> (172.25.0.5:49252 -> 172.25.0.4:5672, state: starting):
rabbitmq3_1  | PLAIN login refused: user 'guest' - invalid credentials
rabbitmq1_1  | 2019-02-13 10:50:08.940 [info] <0.1430.0> accepting AMQP connection <0.1430.0> (172.25.0.5:46062 -> 172.25.0.2:5672)
rabbitmq1_1  | 2019-02-13 10:50:08.952 [error] <0.1430.0> Error on AMQP connection <0.1430.0> (172.25.0.5:46062 -> 172.25.0.2:5672, state: starting):
rabbitmq1_1  | PLAIN login refused: user 'guest' - invalid credentials
rabbitmq2_1  | 2019-02-13 10:50:09.818 [info] <0.875.0> accepting AMQP connection <0.875.0> (172.25.0.5:41130 -> 172.25.0.3:5672)
rabbitmq2_1  | 2019-02-13 10:50:09.826 [error] <0.875.0> Error on AMQP connection <0.875.0> (172.25.0.5:41130 -> 172.25.0.3:5672, state: starting):
rabbitmq2_1  | PLAIN login refused: user 'guest' - invalid credentials
rabbitmq1_1  | 2019-02-13 10:50:10.056 [info] <0.1427.0> closing AMQP connection <0.1427.0> (172.25.0.5:46038 -> 172.25.0.2:5672)
rabbitmq2_1  | 2019-02-13 10:50:11.136 [info] <0.872.0> closing AMQP connection <0.872.0> (172.25.0.5:41106 -> 172.25.0.3:5672)
rabbitmq3_1  | 2019-02-13 10:50:11.775 [info] <0.823.0> closing AMQP connection <0.823.0> (172.25.0.5:49252 -> 172.25.0.4:5672)
rabbitmq1_1  | 2019-02-13 10:50:11.953 [info] <0.1430.0> closing AMQP connection <0.1430.0> (172.25.0.5:46062 -> 172.25.0.2:5672)
rabbitmq3_1  | 2019-02-13 10:50:12.415 [info] <0.827.0> accepting AMQP connection <0.827.0> (172.25.0.5:49282 -> 172.25.0.4:5672)
rabbitmq3_1  | 2019-02-13 10:50:12.424 [error] <0.827.0> Error on AMQP connection <0.827.0> (172.25.0.5:49282 -> 172.25.0.4:5672, state: starting):
rabbitmq3_1  | PLAIN login refused: user 'guest' - invalid credentials
infinite...

how can I solve this

Hi there!

I'm taking this repo for a whirl to test out some rabbitmq clustering locally, and I'm hitting a bit of a snag that I can't quite work out.

I cloned the repo, ran docker-compose up, and got the following output:

PS C:\Projects\Work\RabbitClustering\docker-rabbitmq-cluster> docker-compose up
Starting docker-rabbitmq-cluster_rabbitmq1_1 ... done
Starting docker-rabbitmq-cluster_rabbitmq3_1 ... done
Starting docker-rabbitmq-cluster_rabbitmq2_1 ... done
Attaching to docker-rabbitmq-cluster_rabbitmq1_1, docker-rabbitmq-cluster_rabbitmq2_1, docker-rabbitmq-cluster_rabbitmq3_1
rabbitmq2_1  | standard_init_linux.go:190: exec user process caused "no such file or directory"
rabbitmq3_1  | standard_init_linux.go:190: exec user process caused "no such file or directory"
docker-rabbitmq-cluster_rabbitmq2_1 exited with code 1
docker-rabbitmq-cluster_rabbitmq3_1 exited with code 1

So the first node appears to start, but the second and third fail, and hence haproxy along with it. It looks like the official image hasn't changed either. The failure appears to be in locating the rabbit image's entrypoint: /usr/local/bin/docker-entrypoint.sh

Any ideas on what I'm missing? 😕

Thanks!