RabbitMq server fails to start - BOOT FAILED

[uditkumawat]

Sometimes rabbitMq server fails to start.Below are the logs, please help me in resolving this issue.

2021-11-23 04:37:54.238 [info] <0.44.0> Application mnesia exited with reason: stopped
2021-11-23 04:37:54.238 [info] <0.44.0> Application mnesia exited with reason: stopped
2021-11-23 04:37:54.238 [error] <0.271.0>
2021-11-23 04:37:54.238 [error] <0.271.0> BOOT FAILED
2021-11-23 04:37:54.239 [error] <0.271.0> ===========
2021-11-23 04:37:54.239 [error] <0.271.0> Exception during startup:
2021-11-23 04:37:54.239 [error] <0.271.0>
2021-11-23 04:37:54.239 [error] <0.271.0> rabbit_boot_steps:run_boot_steps/1 line 20
2021-11-23 04:37:54.239 [error] <0.271.0> rabbit_boot_steps:'-run_boot_steps/1-lc$^0/1-0-'/1 line 19
2021-11-23 04:37:54.239 [error] <0.271.0> rabbit_boot_steps:run_step/2 line 46
2021-11-23 04:37:54.239 [error] <0.271.0> rabbit_boot_steps:'-run_step/2-lc$^0/1-0-'/2 line 41
2021-11-23 04:37:54.239 [error] <0.271.0> rabbit:insert_default_data/0 line 1018
2021-11-23 04:37:54.240 [error] <0.271.0> rabbit_auth_backend_internal:add_user_sans_validation/3 line 211
2021-11-23 04:37:54.240 [error] <0.271.0> rabbit_password:hash/2 line 25
2021-11-23 04:37:54.240 [error] <0.271.0> crypto:notsup_to_error/1 line 2635
2021-11-23 04:37:54.240 [error] <0.271.0> error:notsup
2021-11-23 04:37:54.240 [error] <0.271.0>

[michaelklishin]

Thank you for your time.

Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. This assumes that we have a certain amount of information to work with.

Getting all the details necessary to reproduce an issue, make a conclusion or even form a hypothesis about what's happening can take a fair amount of time. Our team is multiple orders of magnitude smaller than the RabbitMQ community. Please help others help you by providing a way to reproduce the behavior you're
observing and sharing as much relevant information as possible on the list:

• Server, client library and plugin (if applicable) versions used
• Server logs
• A code example or terminal transcript that can be used to reproduce
• Full exception stack traces (not a single line message)
• rabbitmqctl status (and, if possible, rabbitmqctl environment output)
• Other relevant things about the environment and workload, e.g. OS/systemd logs, a traffic capture, deployment tool logs, etc

Feel free to edit out hostnames and other potentially sensitive information.

When/if we have a complete enough understanding of what's going on, a recommendation will be provided or a new issues with more context will be filed.

Thank you.

[michaelklishin]

2021-11-23 04:37:54.240 [error] <0.271.0> rabbit_password:hash/2 line 25
2021-11-23 04:37:54.240 [error] <0.271.0> crypto:notsup_to_error/1 line 2635
2021-11-23 04:37:54.240 [error] <0.271.0> error:notsup

very likely means that the crypto module in this installation is missing, so RabbitMQ cannot insert default user data because it cannot hash the password. See Erlang/OTP Requirements.

[uditkumawat]

@michaelklishin I am already having rabbitmq server as 3.8.9 and erlang version 23.1. I never installed crypto module seperately. Suddenly this error has started coming in AWS gov cloud. For other commercial accounts of AWS, rabbitmq server is running fine.

[lukebakken]

I am already having rabbitmq server as 3.8.9 and erlang version 23.1. I never installed crypto module seperately. Suddenly this error has started coming in AWS gov cloud

If this error has "suddenly" appeared but you did not change the RabbitMQ or Erlang version, then the operating system has changed due to an update. Can you check your logs for that? Are you absolutely certain nothing changed with your Erlang installation?

Here is the code that fails with error:notsup: https://github.com/rabbitmq/rabbitmq-server/blob/master/deps/rabbit/src/rabbit_password.erl#L25

By default, RabbitMQ uses SHA-256 to hash passwords. It's difficult to imagine a scenario where that isn't supported.