Taiga RabbitMQ containers keep crashing

Troubleshooting Self hosted Taiga
1

My container taiga-docker-taiga-async-rabbitmq-1 keeps crashing with no explanation.

Configuring logger redirection
Killed
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 = taiga

default_user = taiga

default_vhost = taiga
------------------------------------
Killed
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 = taiga

default_user = taiga

default_vhost = taiga
------------------------------------
Killed

I do notice that there’s a high CPU usage when restarting the container

image
image1167×67 19.1 KB

The other RabbitMQ container (taiga-docker-taiga-events-rabbitmq-1) also fails.

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 = taiga

default_user = taiga

default_vhost = taiga
------------------------------------
Configuring logger redirection
Killed

I’ve tried the steps from this thread and these commands, specifically:

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’ve made sure that I’m pulling the latest images as of November 25, 2023. Any solutions or can anyone point me as to why my RabbitMQ containers keep failing?

Also, I’m using the default script for launching Taiga. And I’m using the default erlang cookie RABBITMQ_ERLANG_COOKIE=secret-erlang-cookie.

2

Also worth noting: the image I’m using for RabbitMQ is
rabbitmq:3.8-management-alpine

3

Solution:

Changing the image to:
rabbitmq:3.11-management-alpine

from
rabbitmq:3.8-management-alpine

Fixed everything. Someone should change that dependency in the docker-compose file.

1 Like
4

Hi @Dartegnian

Sometimes, if configuration changes are made after the rábitmq container volumes have been created, there can be problems because they are no longer compatible with the new changes. In these cases, it is recommended to delete the volumes and relaunch them after making the changes.

We updated the docker images a few days ago and with version 3.8 they continued to work without any problem.

However, it is very interesting to know that Taiga also works with rabbitmq “out of the box”. So we will take this into consideration for future versions of our taiga-docker repository.

Thank you very much for your contribution.

Best regards.

1 Like