Error during container up when using RabbitMQ 3.8.34-management docker image

[Nishant Kumar]

Hello,

We wish to use version 3.8.34 of RabbitMQ Server in our development environment (Ubuntu = 18.04.6 LTS).

We use docker compose to create RabbitMQ Container.

I am trying to use docker image "3.8.34-management" from docker hub.

But when I try to do "docker compose up rabbitmq" I see the following error:

workstation-rabbitmq-1  | 2024-05-29 12:25:48.581 [info] <0.44.0> Application mnesia exited with reason: stopped
workstation-rabbitmq-1  | 2024-05-29 12:25:48.581 [info] <0.44.0> Application mnesia exited with reason: stopped
workstation-rabbitmq-1  | 2024-05-29 12:25:48.581 [error] <0.273.0>
workstation-rabbitmq-1  | 2024-05-29 12:25:48.581 [error] <0.273.0> BOOT FAILED
workstation-rabbitmq-1  |
workstation-rabbitmq-1  | BOOT FAILED
workstation-rabbitmq-1  | ===========
workstation-rabbitmq-1  | 2024-05-29 12:25:48.581 [error] <0.273.0> ===========
workstation-rabbitmq-1  | 2024-05-29 12:25:48.581 [error] <0.273.0> Error during startup: {error,
workstation-rabbitmq-1  | Error during startup: {error,
workstation-rabbitmq-1  | 2024-05-29 12:25:48.581 [error] <0.273.0>                           {schema_integrity_check_failed,
workstation-rabbitmq-1  |                           {schema_integrity_check_failed,
workstation-rabbitmq-1  | 2024-05-29 12:25:48.581 [error] <0.273.0>                               [{table_missing,rabbit_listener}]}}
workstation-rabbitmq-1  |                               [{table_missing,rabbit_listener}]}}
workstation-rabbitmq-1  | 2024-05-29 12:25:48.581 [error] <0.273.0>
workstation-rabbitmq-1  |
workstation-rabbitmq-1  | 2024-05-29 12:25:49.583 [info] <0.272.0> [{initial_call,{application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}},{pid,<0.272.0>},{registered_name,[]},{error_info,{exit,{{schema_integrity_check_failed,[{table_missing,rabbit_listener}]},{rabbit,start,[normal,[]]}},[{application_master,init,4,[{file,"application_master.erl"},{line,142}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,226}]}]}},{ancestors,[<0.271.0>]},{message_queue_len,1},{messages,[{'EXIT',<0.273.0>,normal}]},{links,[<0.271.0>,<0.44.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,376},{stack_size,29},{reductions,342}], []
workstation-rabbitmq-1  | 2024-05-29 12:25:49.583 [error] <0.272.0> CRASH REPORT Process <0.272.0> with 0 neighbours exited with reason: {{schema_integrity_check_failed,[{table_missing,rabbit_listener}]},{rabbit,start,[normal,[]]}} in application_master:init/4 line 142
workstation-rabbitmq-1  | 2024-05-29 12:25:49.583 [info] <0.44.0> Application rabbit exited with reason: {{schema_integrity_check_failed,[{table_missing,rabbit_listener}]},{rabbit,start,[normal,[]]}}
workstation-rabbitmq-1  | 2024-05-29 12:25:49.583 [info] <0.44.0> Application rabbit exited with reason: {{schema_integrity_check_failed,[{table_missing,rabbit_listener}]},{rabbit,start,[normal,[]]}}
workstation-rabbitmq-1  | {"Kernel pid terminated",application_controller,"{application_start_failure,rabbit,{{schema_integrity_check_failed,[{table_missing,rabbit_listener}]},{rabbit,start,[normal,[]]}}}"}
workstation-rabbitmq-1  | Kernel pid terminated (application_controller) ({application_start_failure,rabbit,{{schema_integrity_check_failed,[{table_missing,rabbit_listener}]},{rabbit,start,[normal,[]]}}})
workstation-rabbitmq-1  |
workstation-rabbitmq-1  | Crash dump is being written to: /var/log/rabbitmq/erl_crash.dump...done

Following is the section for RabbitMQ in docker-compose.yml file (version = 2)

  rabbitmq:
    hostname: rabbitmq
    image: rabbitmq:3.8.34-management
    platform: linux/x86_64
    ports:
      - 5672:5672
      - 15672:15672
    networks:
      - internal

Can anyone please tell why the issue is happening ? 

Do I need to provide any other information ?

Thank you

[Luke Bakken]

Hello,

RabbitMQ 3.8.34 is completely out of support. (https://github.com/rabbitmq/rabbitmq-server/blob/main/COMMUNITY_SUPPORT.md#who-is-eligible-for-community-support)

Having said that, I started 3.8.34-management using "docker run" without issue - see the attached file. There must be an issue in your environment.