RabbitMQ Service stops after upgrading from 3.10.8 to 3.12.3

[deepankarrelativity002]

In one of my instances, after upgrading RabbitMQ to 3.12.3, service(RabbitMQ) stops after 5-10 sec, hence throwing an error while connecting to API. Also, usually RabbitMQ folder gets generated other than installation folder where we can check but for this case it's not getting generated. How to fix this? Compatible Erlang(26.0.2) is being used

[mkuratczyk]

You provided no information whatsoever that would allow anyone to help you. What error? What's in the logs? Did you upgrade directly from 3.10 to 3.12 (that's not supported)? What do you mean by "folder gets generated"?

Did you follow the upgrade guide, including enabling feature flags?

[deepankarrelativity002]

Log file is not getting generated after upgrading it to 3.12.x to check out for the errors

[michaelklishin]

If the log file is not created it may mean that the node terminates very early in its boot process. There should be at least some output in relevant service/OS logs.

Also, are you sure that your node has all the feature flags enabled? This is an upgrade requirement for 3.12, as mentioned in release notes. If that's not the case, nodes will fail to start.

[michaelklishin]

@senimai if this hypothesis is correct, you have two options:

1. Go back to 3.11.23, enable all feature flags and then upgrade to 3.12 again
2. If this is a development installation, stopping the node, wiping node's data directory should make the node happily start again. Then you can enable all feature flags to be more future-proof

[dumbbell]

If the previous version was 3.10.8, you will have to downgrade to 3.10.8, enable all feature flags, then upgrade to 3.11.23 and do the same, before upgrading one last time to 3.12.3.

[deepankarrelativity002]

Followed the steps being given by @michaelklishin

[michaelklishin]

Did they help? :)