rabbitmq pod in crashloopback status

[sachinmane1983]

Describe the bug

my rabbitmq pod in crashloopback status. in log its showing below error
2023-09-26 16:16:13.485962+00:00 [notice] <0.44.0> Application rabbitmq_prelaunch exited with reason: {{shutdown,{failed_to_start_child,prelaunch,failed_to_prepare_configuration}},{rabbit_prelaunch_app,start,[normal,[]]}}
Kernel pid terminated (application_controller) ({application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,failed_to_prepare_configuration}},{rabbit_prelaunch_app,start,[normal,[]]}}})

Reproduction steps

pod is down with crashloopback status
2023-09-26 16:16:13.485962+00:00 [notice] <0.44.0> Application rabbitmq_prelaunch exited with reason: {{shutdown,{failed_to_start_child,prelaunch,failed_to_prepare_configuration}},{rabbit_prelaunch_app,start,[normal,[]]}}
Kernel pid terminated (application_controller) ({application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,failed_to_prepare_configuration}},{rabbit_prelaunch_app,start,[normal,[]]}}})
...

Expected behavior

2023-09-26 16:16:13.485962+00:00 [notice] <0.44.0> Application rabbitmq_prelaunch exited with reason: {{shutdown,{failed_to_start_child,prelaunch,failed_to_prepare_configuration}},{rabbit_prelaunch_app,start,[normal,[]]}}
Kernel pid terminated (application_controller) ({application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,failed_to_prepare_configuration}},{rabbit_prelaunch_app,start,[normal,[]]}}})

Additional context

2023-09-26 16:16:13.485962+00:00 [notice] <0.44.0> Application rabbitmq_prelaunch exited with reason: {{shutdown,{failed_to_start_child,prelaunch,failed_to_prepare_configuration}},{rabbit_prelaunch_app,start,[normal,[]]}}
Kernel pid terminated (application_controller) ({application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,failed_to_prepare_configuration}},{rabbit_prelaunch_app,start,[normal,[]]}}})

[michaelklishin]

@sachinmane1983 I'm afraid this does not provide any information that may lead to an informed answer. We do not guess in this community.

failed_to_prepare_configuration suggests the node fails very early, at the step where it reads/parses/merges configuration files.

We cannot suggest anything else since we don't know anything about how this cluster was provisioned (no definition YAML), neither what configuration file is used (e.g. advanced.config be syntactically incorrect and there is no validation for that, unlike rabbitmq.conf). Consider sharing as many details as possible, that would help others help you.

[michaelklishin]

Before the node throws said exception, it should log all errors discovered during rabbitmq.conf and advanced.config reading/parsing/reconciliation. Consider inspecting and (if there are any) sharing the logs from that node.