Your message dated Mon, 19 Jan 2026 14:12:24 +0100
with message-id <[email protected]>
and subject line Re: Bug#1125937: rabbitmq-server: Error during startup:
{error,failed_to_initialize_feature_flags_registry}
has caused the Debian Bug report #1125937,
regarding rabbitmq-server: Error during startup:
{error,failed_to_initialize_feature_flags_registry}
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1125937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125937
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rabbitmq-server
Version: 4.0.5-6+deb13u2
Severity: important
During an upgrade from debian 12 to debian 13 dpkg reported a failure
configuring rabbitmq-server.
It turns out that rabbitmq-server doesn't start with this error in the log
BOOT FAILED
===========
Error during startup: {error,failed_to_initialize_feature_flags_registry}
Kernel pid terminated (application_controller)
("{application_start_failure,rabbit,{failed_to_initialize_feature_flags_registry,{rabbit,start,[normal,[]]}}}")
Crash dump is being written to: erl_crash.dump...done
Gracefully halting Erlang VM
Searching for the error I found this
https://www.rabbitmq.com/blog/2022/07/20/required-feature-flags-in-rabbitmq-3.11
which says to downgrade the server to the latest 3.8.x, 3.9.x or 3.10.x, enable
the feature flags an upgrade.
I simply renamed the mnesia directory and created a new, empty, one.
-- System Information:
Debian Release: 13.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.63+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages rabbitmq-server depends on:
ii adduser 3.152
ii erlang-base 1:27.3.4.1+dfsg-1
ii erlang-crypto 1:27.3.4.1+dfsg-1
ii erlang-eldap 1:27.3.4.1+dfsg-1
ii erlang-inets 1:27.3.4.1+dfsg-1
ii erlang-mnesia 1:27.3.4.1+dfsg-1
ii erlang-os-mon 1:27.3.4.1+dfsg-1
ii erlang-parsetools 1:27.3.4.1+dfsg-1
ii erlang-public-key 1:27.3.4.1+dfsg-1
ii erlang-runtime-tools 1:27.3.4.1+dfsg-1
ii erlang-ssl 1:27.3.4.1+dfsg-1
ii erlang-syntax-tools 1:27.3.4.1+dfsg-1
ii erlang-tools 1:27.3.4.1+dfsg-1
ii erlang-xmerl 1:27.3.4.1+dfsg-1
ii openssl 3.5.4-1~deb13u1
ii python3 3.13.5-1
ii socat 1.8.0.3-1
Versions of packages rabbitmq-server recommends:
ii logrotate 3.22.0-1
rabbitmq-server suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On 1/19/26 9:42 AM, Luca Olivetti wrote:
Package: rabbitmq-server
Version: 4.0.5-6+deb13u2
Severity: important
During an upgrade from debian 12 to debian 13 dpkg reported a failure
configuring rabbitmq-server.
It turns out that rabbitmq-server doesn't start with this error in the log
BOOT FAILED
===========
Error during startup: {error,failed_to_initialize_feature_flags_registry}
Kernel pid terminated (application_controller)
("{application_start_failure,rabbit,{failed_to_initialize_feature_flags_registry,{rabbit,start,[normal,[]]}}}")
Crash dump is being written to: erl_crash.dump...done
Gracefully halting Erlang VM
Searching for the error I found this
https://www.rabbitmq.com/blog/2022/07/20/required-feature-flags-in-rabbitmq-3.11
which says to downgrade the server to the latest 3.8.x, 3.9.x or 3.10.x, enable
the feature flags an upgrade.
I simply renamed the mnesia directory and created a new, empty, one.
Hi,
This is a known issue that's been documented in the Trixie release
notes. There's nothing we can do about it, apart from recommending what
you did (ie: emptying the mnesia folder).
Cheers,
Thomas Goirand (zigo)
--- End Message ---
