Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rabbitmq:latest does not start up #117

Open
sajith opened this issue Sep 18, 2024 · 2 comments · May be fixed by #118
Open

rabbitmq:latest does not start up #117

sajith opened this issue Sep 18, 2024 · 2 comments · May be fixed by #118
Assignees
Labels
bug Something isn't working

Comments

@sajith
Copy link
Member

sajith commented Sep 18, 2024

Following instructions from https://sdx-docs.readthedocs.io/en/latest/sdx_deploy_single_server.html, I did a docker compose up this morning and it failed, seemingly because of a problem with rabbitmq:latest docker image. It would be a good idea to use a release tag instead of latest.

Here's a section of docker logs rabbitmq:

BOOT FAILED
===========
Exception during startup:

error:{badmatch,{error,{{shutdown,{failed_to_start_child,auth,{"Error when reading /var/lib/rabbitmq/.erlang.cookie: eacces",[{auth,init_no_setcookie,0,[{file,"auth.erl"},{line,313}]},{auth,init,1,[{file,"auth.erl"},{line,165}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,980}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,935}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,241}]}]}}},{child,undefined,net_sup_dynamic,{erl_distribution,start_link,[#{name => rabbit_prelaunch_20@localhost,supervisor => net_sup_dynamic,net_tickintensity => 4,net_ticktime => 60,name_domain => shortnames,clean_halt => false}]},permanent,false,1000,supervisor,[erl_distribution]}}}}

    rabbit_prelaunch_dist:duplicate_node_check/1, line 80
    rabbit_prelaunch_dist:setup/1, line 23
    rabbit_prelaunch:do_run/0, line 115
    rabbit_prelaunch:run_prelaunch_first_phase/0, line 32
    supervisor:do_start_child_i/3, line 420
    supervisor:do_start_child/2, line 406
    supervisor:-start_children/2-fun-0-/3, line 390
    supervisor:children_map/4, line 1258

2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>     supervisor: {local,rabbit_prelaunch_sup}
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>     errorContext: start_error
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>     reason: {badmatch,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                 {error,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                     {{shutdown,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                          {failed_to_start_child,auth,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                              {"Error when reading /var/lib/rabbitmq/.erlang.cookie: eacces",
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                               [{auth,init_no_setcookie,0,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                                    [{file,"auth.erl"},{line,313}]},
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                                {auth,init,1,[{file,"auth.erl"},{line,165}]},
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                                {gen_server,init_it,2,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                                    [{file,"gen_server.erl"},{line,980}]},
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                                {gen_server,init_it,6,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                                    [{file,"gen_server.erl"},{line,935}]},
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                                {proc_lib,init_p_do_apply,3,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                                    [{file,"proc_lib.erl"},{line,241}]}]}}},
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                      {child,undefined,net_sup_dynamic,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                          {erl_distribution,start_link,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                              [#{name => rabbit_prelaunch_20@localhost,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                                 supervisor => net_sup_dynamic,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                                 net_tickintensity => 4,net_ticktime => 60,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                                 name_domain => shortnames,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                                 clean_halt => false}]},
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                          permanent,false,1000,supervisor,
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                          [erl_distribution]}}}}
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>     offender: [{pid,undefined},
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                {id,prelaunch},
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                {mfargs,{rabbit_prelaunch,run_prelaunch_first_phase,[]}},
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                {restart_type,transient},
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                {significant,false},
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                {shutdown,5000},
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0>                {child_type,worker}]
2024-09-18 11:51:28.701102+00:00 [error] <0.156.0> 
Runtime terminating during boot (terminating)

Crash dump is being written to: erl_crash.dump...[os_mon] cpu supervisor port (cpu_sup): Erlang has closed
[os_mon] memory supervisor port (memsup): Erlang has closed
@sajith sajith added the bug Something isn't working label Sep 18, 2024
@sajith sajith linked a pull request Sep 18, 2024 that will close this issue
@italovalcy
Copy link
Contributor

Hi Sajith, I'm testing here with rabbitmq:latest (digest dc6c413c58a5, created 10h ago) and it is working fine for me. Just tested here, making sure to pull the very latest version of each one of the images, and the whole process worked very smoothly.

Personally, I would prefer to stay with rabbitmq:latest unless a major problem happens and we reconsider this. Which does not seems to be the case.

@sajith
Copy link
Member Author

sajith commented Sep 18, 2024

I did a docker pull again, and that pulled the one with digest sha256:d74c576bf9cee66ec28c96299f8cca896945489ee1546fb892edc2116b32e2dc. That seems to run.

I still think that we should prefer a known working version, in the interest of reproducibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants