Running into errors while installing on docker [AMD64]

Any and all help is appreciated

Could you post the output of the following commands?:

sudo docker compose logs taiga-async-rabbitmq

sudo docker compose logs taiga-events-rabbitmq

there you should see the reason why you got an error in both containers.

3 Likes

I have the same issue.
Here are my logs of the containers:

(Can´t upload both log images but they are the same)

Any ideas on how to fix that?

Still nothing?
I would really want to try Taiga…

Hi @JunTVDE

this error suggests that maybe there is an error in the rabbitmq configuration. We can try different things to find out the problem:

  1. run only taiga-events-rabbitmq or taiga-async-rabbitmq and check if it works
  2. check the credentials between x-environment and taiga-async-rabbitmq
  3. check the credentials between taiga-events and taiga-events-rabbitmq
  4. try with a different version of rabbitmq, like 3.11-management-alpine

Good luck!

I tried to install it again on a fresh installation and I got a DB error this time around. Screenshot attached


Please suggest a solution if you can

Nevermind man. I gave up and switched to a different project management suite. This has been going on for months and the moderators here seem to not have any interest in helping unless we’re paying customers of the SaaS version. Forget it and move on.

Hi @m3tr0n !

Sorry to hear that you couldn’t get it running. I’d like just to let you know that we don’t have paying customers (unless they really really want). The SaaS now is completely free: you can have as many users and private projects as you need. If this suits for you, I’d suggest to give it a try in the Saas version. If, after using Taiga, you still want your own instance, you can always install an on-premise instance and migrate your projects. We’ll help you as best as we can.

Nonetheless, if you want to try again with Taiga on-premise, you should be sharing some logs with the error; otherwise it’s too difficult to anyone to know what’s happening.

Cheers!

Hello Yami. I’d like to update that the services are now working. The invite links are still not sending to new users but I’m assuming that requires an email smtp. I’ll update you on the progress.

I have the exact same issue and would love to know how to resolve this.

As you see, there’s a lot of green, but the rabbits show up red:
dockers

The logs look like this

taiga-docker-taiga-async-rabbitmq-1  | 2023-06-21 08:51:08.056 [error] <0.1057.0> ** Connection attempt from node 'rabbitmqcli-8-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-async-rabbitmq-1  | 2023-06-21 08:51:12.596 [error] <0.1062.0> ** Connection attempt from node 'rabbitmqcli-295-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-async-rabbitmq-1  | 2023-06-21 08:51:17.388 [error] <0.1067.0> ** Connection attempt from node 'rabbitmqcli-872-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-async-rabbitmq-1  | 2023-06-21 08:51:22.034 [error] <0.1071.0> ** Connection attempt from node 'rabbitmqcli-941-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-async-rabbitmq-1  | 2023-06-21 08:51:26.676 [error] <0.1076.0> ** Connection attempt from node 'rabbitmqcli-819-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-async-rabbitmq-1  | 2023-06-21 08:51:31.360 [error] <0.1081.0> ** Connection attempt from node 'rabbitmqcli-189-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-async-rabbitmq-1  | 2023-06-21 08:51:36.030 [error] <0.1085.0> ** Connection attempt from node 'rabbitmqcli-661-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-async-rabbitmq-1  | 2023-06-21 08:51:40.858 [error] <0.1090.0> ** Connection attempt from node 'rabbitmqcli-524-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-async-rabbitmq-1  | 2023-06-21 08:51:45.727 [error] <0.1095.0> ** Connection attempt from node 'rabbitmqcli-271-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-async-rabbitmq-1  | 2023-06-21 08:51:50.253 [error] <0.1099.0> ** Connection attempt from node 'rabbitmqcli-594-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-async-rabbitmq-1  | 2023-06-21 08:51:55.698 [error] <0.1105.0> ** Connection attempt from node 'rabbitmqcli-767-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-async-rabbitmq-1  | 2023-06-21 08:52:00.159 [error] <0.1108.0> ** Connection attempt from node 'rabbitmqcli-769-rabbit@taiga-async-rabbitmq' rejected. Invalid challenge reply. **

and this respectively

taiga-docker-taiga-events-rabbitmq-1  | 2023-06-21 08:52:51.008 [error] <0.1159.0> ** Connection attempt from node 'rabbitmqcli-283-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-events-rabbitmq-1  | 2023-06-21 08:52:55.858 [error] <0.1163.0> ** Connection attempt from node 'rabbitmqcli-926-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-events-rabbitmq-1  | 2023-06-21 08:53:00.711 [error] <0.1167.0> ** Connection attempt from node 'rabbitmqcli-716-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-events-rabbitmq-1  | 2023-06-21 08:53:05.498 [error] <0.1172.0> ** Connection attempt from node 'rabbitmqcli-513-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-events-rabbitmq-1  | 2023-06-21 08:53:10.301 [error] <0.1176.0> ** Connection attempt from node 'rabbitmqcli-102-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-events-rabbitmq-1  | 2023-06-21 08:53:15.189 [error] <0.1181.0> ** Connection attempt from node 'rabbitmqcli-290-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-events-rabbitmq-1  | 2023-06-21 08:53:19.983 [error] <0.1186.0> ** Connection attempt from node 'rabbitmqcli-904-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-events-rabbitmq-1  | 2023-06-21 08:53:24.805 [error] <0.1191.0> ** Connection attempt from node 'rabbitmqcli-946-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
taiga-docker-taiga-events-rabbitmq-1  | 2023-06-21 08:53:29.492 [error] <0.1195.0> ** Connection attempt from node 'rabbitmqcli-501-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **

The relevant parts of my .env look like this:

RABBITMQ_USER=taiga
RABBITMQ_PASS=Aiquoh5viagheing

RABBITMQ_VHOST=taiga
RABBITMQ_ERLANG_COOKIE=eim5neishienox7aeShazah0

and the .yml files I did not change at all.

Any help would be greatly appreciated!

No one got any idea?

I asked ChatGPT in my desperation and it kept going back to the rabbitmq config and the erlang-cookie.
When doing docker exec -it <rabbitmq id> env the vhost and pass where not set. After hardcoding them i the docker-compose.yml they showed up correctly. The error persisted though.

I’ve reset my erlang-cookie to the default “secret-erlang-cookie” to match the content of the /var/lib/rabbitmq/.erlang.cookie withing the rabbitmq container, but still no dice.

Here is the complete startup log of one of the rabbitmq containers:

:~/taiga-docker# docker logs 423e06e7491a

warning: /var/lib/rabbitmq/.erlang.cookie contents do not match RABBITMQ_ERLANG_COOKIE

WARNING: '/var/lib/rabbitmq/.erlang.cookie' was populated from '$RABBITMQ_ERLANG_COOKIE', which will no longer happen in 3.9 and later! (https://github.com/docker-library/rabbitmq/pull/424)
WARNING: 'docker-entrypoint.sh' generated/modified the RabbitMQ configuration file, which will no longer happen in 3.9 and later! (https://github.com/docker-library/rabbitmq/pull/424)

Generated end result, for reference:
------------------------------------
loopback_users.guest = false

listeners.tcp.default = 5672

default_pass = Aiquoh5viagheing

default_user = taiga

default_vhost = taiga

management.tcp.port = 15672
------------------------------------
Configuring logger redirection
05:49:40.079 [error] ** Connection attempt from node 'rabbitmqcli-674-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:49:45.756 [debug] <0.291.0> Lager installed handler error_logger_lager_h into error_logger
2023-06-26 05:49:45.757 [debug] <0.294.0> Lager installed handler lager_forwarder_backend into error_logger_lager_event
2023-06-26 05:49:45.771 [debug] <0.297.0> Lager installed handler lager_forwarder_backend into rabbit_log_lager_event
2023-06-26 05:49:45.790 [debug] <0.300.0> Lager installed handler lager_forwarder_backend into rabbit_log_channel_lager_event
2023-06-26 05:49:45.802 [debug] <0.303.0> Lager installed handler lager_forwarder_backend into rabbit_log_connection_lager_event
2023-06-26 05:49:45.804 [debug] <0.306.0> Lager installed handler lager_forwarder_backend into rabbit_log_feature_flags_lager_event
2023-06-26 05:49:45.807 [debug] <0.309.0> Lager installed handler lager_forwarder_backend into rabbit_log_federation_lager_event
2023-06-26 05:49:45.808 [debug] <0.312.0> Lager installed handler lager_forwarder_backend into rabbit_log_ldap_lager_event
2023-06-26 05:49:45.816 [debug] <0.315.0> Lager installed handler lager_forwarder_backend into rabbit_log_mirroring_lager_event
2023-06-26 05:49:45.824 [debug] <0.318.0> Lager installed handler lager_forwarder_backend into rabbit_log_prelaunch_lager_event
2023-06-26 05:49:45.829 [debug] <0.321.0> Lager installed handler lager_forwarder_backend into rabbit_log_queue_lager_event
2023-06-26 05:49:45.837 [debug] <0.324.0> Lager installed handler lager_forwarder_backend into rabbit_log_ra_lager_event
2023-06-26 05:49:45.855 [debug] <0.327.0> Lager installed handler lager_forwarder_backend into rabbit_log_shovel_lager_event
2023-06-26 05:49:45.858 [debug] <0.330.0> Lager installed handler lager_forwarder_backend into rabbit_log_upgrade_lager_event
2023-06-26 05:49:46.035 [info] <0.44.0> Application lager started on node 'rabbit@taiga-events-rabbitmq'
2023-06-26 05:49:46.260 [debug] <0.287.0> Lager installed handler lager_backend_throttle into lager_event
2023-06-26 05:49:47.302 [error] <0.334.0> ** Connection attempt from node 'rabbitmqcli-758-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:49:54.255 [error] <0.337.0> ** Connection attempt from node 'rabbitmqcli-76-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:49:58.862 [info] <0.44.0> Application mnesia started on node 'rabbit@taiga-events-rabbitmq'
2023-06-26 05:49:58.865 [info] <0.275.0>
 Starting RabbitMQ 3.8.34 on Erlang 24.3.4.1 [jit]
 Copyright (c) 2007-2022 VMware, Inc. or its affiliates.
 Licensed under the MPL 2.0. Website: https://rabbitmq.com

  ##  ##      RabbitMQ 3.8.34
  ##  ##
  ##########  Copyright (c) 2007-2022 VMware, Inc. or its affiliates.
  ######  ##
  ##########  Licensed under the MPL 2.0. Website: https://rabbitmq.com

  Erlang:      24.3.4.1 [jit]
  TLS Library: OpenSSL - OpenSSL 1.1.1o  3 May 2022

  Doc guides:  https://rabbitmq.com/documentation.html
  Support:     https://rabbitmq.com/contact.html
  Tutorials:   https://rabbitmq.com/getstarted.html
  Monitoring:  https://rabbitmq.com/monitoring.html

  Logs: <stdout>

  Config file(s): /etc/rabbitmq/rabbitmq.conf

  Starting broker...2023-06-26 05:49:58.869 [info] <0.275.0>
 node           : rabbit@taiga-events-rabbitmq
 home dir       : /var/lib/rabbitmq
 config file(s) : /etc/rabbitmq/rabbitmq.conf
 cookie hash    : kD6oFXWiU4mHDTY8rbf/cQ==
 log(s)         : <stdout>
 database dir   : /var/lib/rabbitmq/mnesia/rabbit@taiga-events-rabbitmq
2023-06-26 05:50:01.031 [error] <0.419.0> ** Connection attempt from node 'rabbitmqcli-660-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:50:02.848 [info] <0.275.0> Feature flags: list of feature flags found:
2023-06-26 05:50:02.848 [info] <0.275.0> Feature flags:   [x] drop_unroutable_metric
2023-06-26 05:50:02.848 [info] <0.275.0> Feature flags:   [x] empty_basic_get_metric
2023-06-26 05:50:02.849 [info] <0.275.0> Feature flags:   [x] implicit_default_bindings
2023-06-26 05:50:02.849 [info] <0.275.0> Feature flags:   [x] maintenance_mode_status
2023-06-26 05:50:02.849 [info] <0.275.0> Feature flags:   [x] quorum_queue
2023-06-26 05:50:02.849 [info] <0.275.0> Feature flags:   [x] user_limits
2023-06-26 05:50:02.849 [info] <0.275.0> Feature flags:   [x] virtual_host_metadata
2023-06-26 05:50:02.849 [info] <0.275.0> Feature flags: feature flag states written to disk: yes
2023-06-26 05:50:04.620 [info] <0.275.0> Running boot step pre_boot defined by app rabbit
2023-06-26 05:50:04.620 [info] <0.275.0> Running boot step rabbit_core_metrics defined by app rabbit
2023-06-26 05:50:04.621 [info] <0.275.0> Running boot step rabbit_alarm defined by app rabbit
2023-06-26 05:50:04.632 [info] <0.427.0> Memory high watermark set to 786 MiB (825131008 bytes) of 1967 MiB (2062827520 bytes) total
2023-06-26 05:50:04.670 [info] <0.429.0> Enabling free disk space monitoring
2023-06-26 05:50:04.670 [info] <0.429.0> Disk free limit set to 50MB
2023-06-26 05:50:04.683 [info] <0.275.0> Running boot step code_server_cache defined by app rabbit
2023-06-26 05:50:04.684 [info] <0.275.0> Running boot step file_handle_cache defined by app rabbit
2023-06-26 05:50:04.684 [info] <0.435.0> FHC read buffering:  OFF
2023-06-26 05:50:04.684 [info] <0.435.0> FHC write buffering: ON
2023-06-26 05:50:04.684 [info] <0.434.0> Limiting to approx 1048479 file handles (943629 sockets)
2023-06-26 05:50:04.687 [info] <0.275.0> Running boot step worker_pool defined by app rabbit
2023-06-26 05:50:04.688 [info] <0.380.0> Will use 2 processes for default worker pool
2023-06-26 05:50:04.688 [info] <0.380.0> Starting worker pool 'worker_pool' with 2 processes in it
2023-06-26 05:50:04.688 [info] <0.275.0> Running boot step database defined by app rabbit
2023-06-26 05:50:04.702 [info] <0.275.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2023-06-26 05:50:04.703 [info] <0.275.0> Successfully synced tables from a peer
2023-06-26 05:50:04.703 [info] <0.275.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2023-06-26 05:50:04.704 [info] <0.275.0> Successfully synced tables from a peer
2023-06-26 05:50:04.890 [info] <0.275.0> Waiting for Mnesia tables for 30000 ms, 9 retries left
2023-06-26 05:50:04.891 [info] <0.275.0> Successfully synced tables from a peer
2023-06-26 05:50:04.891 [info] <0.275.0> Peer discovery backend rabbit_peer_discovery_classic_config does not support registration, skipping registration.
2023-06-26 05:50:04.892 [info] <0.275.0> Running boot step database_sync defined by app rabbit
2023-06-26 05:50:04.893 [info] <0.275.0> Running boot step feature_flags defined by app rabbit
2023-06-26 05:50:04.896 [info] <0.275.0> Running boot step codec_correctness_check defined by app rabbit
2023-06-26 05:50:04.896 [info] <0.275.0> Running boot step external_infrastructure defined by app rabbit
2023-06-26 05:50:04.896 [info] <0.275.0> Running boot step rabbit_registry defined by app rabbit
2023-06-26 05:50:04.897 [info] <0.275.0> Running boot step rabbit_auth_mechanism_cr_demo defined by app rabbit
2023-06-26 05:50:04.897 [info] <0.275.0> Running boot step rabbit_queue_location_random defined by app rabbit
2023-06-26 05:50:04.899 [info] <0.275.0> Running boot step rabbit_event defined by app rabbit
2023-06-26 05:50:04.899 [info] <0.275.0> Running boot step rabbit_auth_mechanism_amqplain defined by app rabbit
2023-06-26 05:50:04.901 [info] <0.275.0> Running boot step rabbit_auth_mechanism_plain defined by app rabbit
2023-06-26 05:50:04.902 [info] <0.275.0> Running boot step rabbit_exchange_type_direct defined by app rabbit
2023-06-26 05:50:04.902 [info] <0.275.0> Running boot step rabbit_exchange_type_fanout defined by app rabbit
2023-06-26 05:50:04.903 [info] <0.275.0> Running boot step rabbit_exchange_type_headers defined by app rabbit
2023-06-26 05:50:04.904 [info] <0.275.0> Running boot step rabbit_exchange_type_topic defined by app rabbit
2023-06-26 05:50:04.905 [info] <0.275.0> Running boot step rabbit_mirror_queue_mode_all defined by app rabbit
2023-06-26 05:50:04.905 [info] <0.275.0> Running boot step rabbit_mirror_queue_mode_exactly defined by app rabbit
2023-06-26 05:50:04.906 [info] <0.275.0> Running boot step rabbit_mirror_queue_mode_nodes defined by app rabbit
2023-06-26 05:50:04.906 [info] <0.275.0> Running boot step rabbit_priority_queue defined by app rabbit
2023-06-26 05:50:04.906 [info] <0.275.0> Priority queues enabled, real BQ is rabbit_variable_queue
2023-06-26 05:50:04.906 [info] <0.275.0> Running boot step rabbit_queue_location_client_local defined by app rabbit
2023-06-26 05:50:04.906 [info] <0.275.0> Running boot step rabbit_queue_location_min_masters defined by app rabbit
2023-06-26 05:50:04.906 [info] <0.275.0> Running boot step kernel_ready defined by app rabbit
2023-06-26 05:50:04.906 [info] <0.275.0> Running boot step rabbit_sysmon_minder defined by app rabbit
2023-06-26 05:50:04.909 [info] <0.275.0> Running boot step rabbit_epmd_monitor defined by app rabbit
2023-06-26 05:50:04.915 [info] <0.455.0> epmd monitor knows us, inter-node communication (distribution) port: 25672
2023-06-26 05:50:04.916 [info] <0.275.0> Running boot step guid_generator defined by app rabbit
2023-06-26 05:50:04.921 [info] <0.275.0> Running boot step rabbit_node_monitor defined by app rabbit
2023-06-26 05:50:04.921 [info] <0.459.0> Starting rabbit_node_monitor
2023-06-26 05:50:04.922 [info] <0.275.0> Running boot step delegate_sup defined by app rabbit
2023-06-26 05:50:04.927 [info] <0.275.0> Running boot step rabbit_memory_monitor defined by app rabbit
2023-06-26 05:50:04.930 [info] <0.275.0> Running boot step core_initialized defined by app rabbit
2023-06-26 05:50:04.930 [info] <0.275.0> Running boot step upgrade_queues defined by app rabbit
2023-06-26 05:50:05.050 [info] <0.275.0> Running boot step channel_tracking defined by app rabbit
2023-06-26 05:50:05.051 [info] <0.275.0> Setting up a table for channel tracking on this node: 'tracked_channel_on_node_rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.052 [info] <0.275.0> Setting up a table for channel tracking on this node: 'tracked_channel_table_per_user_on_node_rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.052 [info] <0.275.0> Running boot step rabbit_channel_tracking_handler defined by app rabbit
2023-06-26 05:50:05.052 [info] <0.275.0> Running boot step connection_tracking defined by app rabbit
2023-06-26 05:50:05.053 [info] <0.275.0> Setting up a table for connection tracking on this node: 'tracked_connection_on_node_rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.053 [info] <0.275.0> Setting up a table for per-vhost connection counting on this node: 'tracked_connection_per_vhost_on_node_rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.055 [info] <0.275.0> Setting up a table for per-user connection counting on this node: 'tracked_connection_table_per_user_on_node_rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.056 [info] <0.275.0> Running boot step rabbit_connection_tracking_handler defined by app rabbit
2023-06-26 05:50:05.056 [info] <0.275.0> Running boot step rabbit_exchange_parameters defined by app rabbit
2023-06-26 05:50:05.056 [info] <0.275.0> Running boot step rabbit_mirror_queue_misc defined by app rabbit
2023-06-26 05:50:05.057 [info] <0.275.0> Running boot step rabbit_policies defined by app rabbit
2023-06-26 05:50:05.067 [info] <0.275.0> Running boot step rabbit_policy defined by app rabbit
2023-06-26 05:50:05.067 [info] <0.275.0> Running boot step rabbit_queue_location_validator defined by app rabbit
2023-06-26 05:50:05.067 [info] <0.275.0> Running boot step rabbit_quorum_memory_manager defined by app rabbit
2023-06-26 05:50:05.067 [info] <0.275.0> Running boot step rabbit_vhost_limit defined by app rabbit
2023-06-26 05:50:05.067 [info] <0.275.0> Running boot step rabbit_mgmt_reset_handler defined by app rabbitmq_management
2023-06-26 05:50:05.067 [info] <0.275.0> Running boot step rabbit_mgmt_db_handler defined by app rabbitmq_management_agent
2023-06-26 05:50:05.067 [info] <0.275.0> Management plugin: using rates mode 'basic'
2023-06-26 05:50:05.068 [info] <0.275.0> Running boot step recovery defined by app rabbit
2023-06-26 05:50:05.079 [info] <0.496.0> Making sure data directory '/var/lib/rabbitmq/mnesia/rabbit@taiga-events-rabbitmq/msg_stores/vhosts/DUUPSD51ILPPE6LUATO0IN63B' for vhost 'taiga' exists
2023-06-26 05:50:05.087 [info] <0.496.0> Starting message stores for vhost 'taiga'
2023-06-26 05:50:05.088 [info] <0.500.0> Message store "DUUPSD51ILPPE6LUATO0IN63B/msg_store_transient": using rabbit_msg_store_ets_index to provide index
2023-06-26 05:50:05.095 [info] <0.496.0> Started message store of type transient for vhost 'taiga'
2023-06-26 05:50:05.096 [info] <0.504.0> Message store "DUUPSD51ILPPE6LUATO0IN63B/msg_store_persistent": using rabbit_msg_store_ets_index to provide index
2023-06-26 05:50:05.108 [info] <0.496.0> Started message store of type persistent for vhost 'taiga'
2023-06-26 05:50:05.119 [info] <0.275.0> Running boot step empty_db_check defined by app rabbit
2023-06-26 05:50:05.119 [info] <0.275.0> Will not seed default virtual host and user: have definitions to load...
2023-06-26 05:50:05.119 [info] <0.275.0> Running boot step rabbit_looking_glass defined by app rabbit
2023-06-26 05:50:05.119 [info] <0.275.0> Running boot step rabbit_core_metrics_gc defined by app rabbit
2023-06-26 05:50:05.121 [info] <0.275.0> Running boot step background_gc defined by app rabbit
2023-06-26 05:50:05.125 [info] <0.275.0> Running boot step routing_ready defined by app rabbit
2023-06-26 05:50:05.125 [info] <0.275.0> Running boot step pre_flight defined by app rabbit
2023-06-26 05:50:05.125 [info] <0.275.0> Running boot step notify_cluster defined by app rabbit
2023-06-26 05:50:05.126 [info] <0.275.0> Running boot step networking defined by app rabbit
2023-06-26 05:50:05.126 [info] <0.275.0> Running boot step definition_import_worker_pool defined by app rabbit
2023-06-26 05:50:05.126 [info] <0.380.0> Starting worker pool 'definition_import_pool' with 2 processes in it
2023-06-26 05:50:05.127 [info] <0.275.0> Running boot step cluster_name defined by app rabbit
2023-06-26 05:50:05.127 [info] <0.275.0> Running boot step direct_client defined by app rabbit
2023-06-26 05:50:05.130 [info] <0.275.0> Running boot step rabbit_management_load_definitions defined by app rabbitmq_management
2023-06-26 05:50:05.130 [info] <0.530.0> Resetting node maintenance status
2023-06-26 05:50:05.130 [info] <0.44.0> Application rabbit started on node 'rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.158 [info] <0.44.0> Application rabbitmq_management_agent started on node 'rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.158 [info] <0.44.0> Application cowlib started on node 'rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.159 [info] <0.44.0> Application cowboy started on node 'rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.160 [info] <0.44.0> Application rabbitmq_web_dispatch started on node 'rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.162 [info] <0.44.0> Application amqp_client started on node 'rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.348 [info] <0.589.0> Management plugin: HTTP (non-TLS) listener started on port 15672
2023-06-26 05:50:05.349 [info] <0.618.0> Statistics database started.
2023-06-26 05:50:05.350 [info] <0.617.0> Starting worker pool 'management_worker_pool' with 3 processes in it
2023-06-26 05:50:05.357 [info] <0.44.0> Application rabbitmq_management started on node 'rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.496 [info] <0.44.0> Application prometheus started on node 'rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.522 [info] <0.631.0> Prometheus metrics: HTTP (non-TLS) listener started on port 15692
2023-06-26 05:50:05.522 [info] <0.44.0> Application rabbitmq_prometheus started on node 'rabbit@taiga-events-rabbitmq'
2023-06-26 05:50:05.522 [info] <0.530.0> Ready to start client connection listeners
2023-06-26 05:50:05.531 [info] <0.675.0> started TCP listener on [::]:5672
2023-06-26 05:50:07.684 [error] <0.678.0> ** Connection attempt from node 'rabbitmqcli-475-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:50:07.894 [info] <0.530.0> Server startup complete; 4 plugins started.
 * rabbitmq_prometheus
 * rabbitmq_management
 * rabbitmq_web_dispatch
 * rabbitmq_management_agent
 completed with 4 plugins.
2023-06-26 05:50:07.894 [info] <0.530.0> Resetting node maintenance status
2023-06-26 05:50:12.076 [error] <0.683.0> ** Connection attempt from node 'rabbitmqcli-47-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:50:16.298 [error] <0.687.0> ** Connection attempt from node 'rabbitmqcli-543-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:50:20.946 [error] <0.692.0> ** Connection attempt from node 'rabbitmqcli-266-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:50:25.601 [error] <0.697.0> ** Connection attempt from node 'rabbitmqcli-556-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:50:30.460 [error] <0.702.0> ** Connection attempt from node 'rabbitmqcli-951-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:50:35.205 [error] <0.706.0> ** Connection attempt from node 'rabbitmqcli-1-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:50:40.359 [error] <0.712.0> ** Connection attempt from node 'rabbitmqcli-226-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:50:45.262 [error] <0.717.0> ** Connection attempt from node 'rabbitmqcli-535-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:50:50.097 [error] <0.721.0> ** Connection attempt from node 'rabbitmqcli-891-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:50:54.974 [error] <0.726.0> ** Connection attempt from node 'rabbitmqcli-68-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:50:59.708 [error] <0.731.0> ** Connection attempt from node 'rabbitmqcli-647-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:51:04.527 [error] <0.736.0> ** Connection attempt from node 'rabbitmqcli-552-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:51:09.289 [error] <0.741.0> ** Connection attempt from node 'rabbitmqcli-677-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:51:14.307 [error] <0.747.0> ** Connection attempt from node 'rabbitmqcli-600-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:51:19.092 [error] <0.752.0> ** Connection attempt from node 'rabbitmqcli-991-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:51:24.566 [error] <0.757.0> ** Connection attempt from node 'rabbitmqcli-718-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **
2023-06-26 05:51:29.326 [error] <0.762.0> ** Connection attempt from node 'rabbitmqcli-236-rabbit@taiga-events-rabbitmq' rejected. Invalid challenge reply. **

I’m running out of ideas…

Hi @viamonster

Try to setup rabbit setting with the default values.

RABBITMQ_USER=taiga
RABBITMQ_PASS=taiga
RABBITMQ_VHOST=taiga
RABBITMQ_ERLANG_COOKIE=secret-erlang-cookie

The problem that I think you are having is that you have changed rabbit’s settings (pass and cookie) after having previously initialized it. Therefore, the volume has been created with the initial configuration that appears in the docker-compose.yml.

As it is an internal service, which does not expose any port to the outside of the internal network, my recommendation is that you leave it as it is. There is no security problem.

However, if you want to change it, you must delete the volumes and containers after each change, before starting the system again.

docker compose rm taiga-docker-taiga-async-rabbitmq 
docker volume rm  taiga-docker_taiga-async-rabbitmq-data
docker compose rm taiga-docker-taiga-events-rabbitmq 
docker volume rm  taiga-docker_taiga-events-rabbitmq-data

I hope this can help

Best regards

1 Like

Thank you so much! That did the trick - all containers are now up an running!

After seeing a default-looking password and cookie string in the .env, I was under the impression that I’m supposed to change those. Maybe adding a comment along the lines of “Don’t change these unless you know what you are doing” would be a good idea?

1 Like