RabbitMQ does not start after upgrade to 3.11.1-1 on Debian Buster

7,098 views
Skip to first unread message

William Thomas

unread,
Oct 1, 2022, 11:33:50 AM10/1/22
to rabbitmq-users
After upgrading rabbitmq-server from 3.10.8-1 to 3.11.1-1, RabbitMQ no longer starts.
The error is
Oct  1 10:10:05 rmq001-ed2prd rabbitmq-server[7511]: 2022-10-01 10:10:05.806947-05:00 [error] <0.230.0> Feature flags: `implicit_default_bindings`: required feature flag not enabled! It must be enabled before upgrading RabbitMQ.
Oct  1 10:10:05 rmq001-ed2prd rabbitmq-server[7511]: 2022-10-01 10:10:05.816830-05:00 [error] <0.230.0> Failed to initialize feature flags registry: {disabled_required_feature_flag,
Oct  1 10:10:05 rmq001-ed2prd rabbitmq-server[7511]: 2022-10-01 10:10:05.816830-05:00 [error] <0.230.0>                                               implicit_default_bindings}


From what I could see, I should be able to add that feature flag by setting an environment variable at startup, such as RABBITMQ_FEATURE_FLAGS=implicit_default_bindings

I tried that, and received the exact same error.  

This occurred on multiple machines for me last night, during our normal upgrade window, and I ended up reverting out the upgrade to get them functioning again.

Michal Kuratczyk

unread,
Oct 1, 2022, 3:08:59 PM10/1/22
to rabbitm...@googlegroups.com

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/76b2bea7-4159-444b-ac0a-96852c81d5bcn%40googlegroups.com.


--
Michał
RabbitMQ team

Christopher Hartley

unread,
Oct 14, 2022, 9:54:02 AM10/14/22
to rabbitmq-users
I get the following error attached when upgrading to Rabbit MQ version 23.11.1 and Erlang 25.1.1

The Rabbit MQ Service does not start.
RabbitError.png

Luke Bakken

unread,
Oct 14, 2022, 6:53:02 PM10/14/22
to rabbitmq-users
Hi Christopher,

Please start a new discussion as what you report is not related to the original issue.

Reply all
Reply to author
Forward
0 new messages