Unable to start new Rabbit node with disabled "RABBITMQ_FEATURE_FLAGS "

552 views
Skip to first unread message

yaniv nayax

unread,
Apr 18, 2023, 5:09:35 AM4/18/23
to rabbitmq-users
Hi All,
I have a test Rabbit cluster with 3 ubuntu18 nodes - Rabbit 3.8.9 Erlang  23.1.4

Trying to upgrade the cluster to Rabbit 3.10.0 Erlang 24.3.3
I have removed the first node from the cluster + uninstalled Erlang & Rabbit + installed the new versions for both.

Trying to start the new node with only the relevant Feature Flags, 
However the node is unable to start when I set it in the /etc/rabbitmq/rabbitmq.conf

The file is empty, I have tried both these options, but the service is unable to start with it:
1. RABBITMQ_FEATURE_FLAGS=quorum_queue,implicit_default_bindings2. {rabbit, [{forced_feature_flags_on_init, [quorum_queue, implicit_default_bindings]}]}Any help appreciated, Tnx Yaniv

Michal Kuratczyk

unread,
Apr 18, 2023, 8:46:48 AM4/18/23
to rabbitm...@googlegroups.com
You didn't provide the error you get.

In the future, remember to always enable all feature flags after a successful upgrade. They are not meant to be configuration flags,
but just temporarily switches to allow upgrading nodes one by one. 

--
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/1c66f555-7362-4924-99bb-7ed930a3c307n%40googlegroups.com.


--
Michał
RabbitMQ team

yaniv nayax

unread,
Apr 18, 2023, 9:02:03 AM4/18/23
to rabbitmq-users
Hi Michal,
Thank you for your reply, this is exactly what I'm trying to do - upgrade the nodes one by one.
however, the first node service is not starting due to the config file giving this error (I already tested and verified that the error is sue to the "RABBITMQ_FEATURE_FLAGS" line in the config):

root@rabbitprodtest01:/etc/rabbitmq# systemctl status rabbitmq-server.service
● rabbitmq-server.service - RabbitMQ broker
   Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; vendor preset: enabled)
   Active: activating (start) since Tue 2023-04-18 13:00:52 UTC; 1s ago
  Process: 4661 ExecStop=/usr/lib/rabbitmq/bin/rabbitmqctl shutdown (code=exited, status=0/SUCCESS)
 Main PID: 4761 (beam.smp)
   Status: "Startup in progress"
    Tasks: 21 (limit: 4654)
   CGroup: /system.slice/rabbitmq-server.service
           ├─4761 /usr/lib/erlang/erts-12.3.1/bin/beam.smp -W w -MBas ageffcbf -MHas ageffcbf -MBlmbcs 512 -MHlmbcs 512 -MMmcs 30 -P 1048576 -t 5000000 -stbt db -zdbbl 128000 -sbwt none -sbwtdcpu none -sbwtdio none -- -root /usr/lib/erla
           └─4787 erl_child_setup 32768

Apr 18 13:00:53 rabbitprodtest01 rabbitmq-server[4761]: 2023-04-18 13:00:53.581046+00:00 [erro] <0.130.0>   - Syntax error in /etc/rabbitmq/rabbitmq.conf after line 80 column 1, parsing incomplete
Apr 18 13:00:53 rabbitprodtest01 rabbitmq-server[4761]: 2023-04-18 13:00:53.581127+00:00 [erro] <0.130.0> Are these files using the Cuttlefish format?
Apr 18 13:00:53 rabbitprodtest01 rabbitmq-server[4761]: BOOT FAILED
Apr 18 13:00:53 rabbitprodtest01 rabbitmq-server[4761]: 2023-04-18 13:00:53.583816+00:00 [erro] <0.130.0>
Apr 18 13:00:53 rabbitprodtest01 rabbitmq-server[4761]: 2023-04-18 13:00:53.583816+00:00 [erro] <0.130.0> BOOT FAILED
Apr 18 13:00:53 rabbitprodtest01 rabbitmq-server[4761]: 2023-04-18 13:00:53.583816+00:00 [erro] <0.130.0> ===========
Apr 18 13:00:53 rabbitprodtest01 rabbitmq-server[4761]: 2023-04-18 13:00:53.583816+00:00 [erro] <0.130.0> Error during startup: {error,failed_to_parse_configuration_file}
Apr 18 13:00:53 rabbitprodtest01 rabbitmq-server[4761]: 2023-04-18 13:00:53.583816+00:00 [erro] <0.130.0>
Apr 18 13:00:53 rabbitprodtest01 rabbitmq-server[4761]: ===========
Apr 18 13:00:53 rabbitprodtest01 rabbitmq-server[4761]: Error during startup: {error,failed_to_parse_configuration_file}





Michal Kuratczyk

unread,
Apr 18, 2023, 9:25:13 AM4/18/23
to rabbitm...@googlegroups.com
Are you trying to set
RABBITMQ_FEATURE_FLAGS=quorum_queue,implicit_default_bindings in
rabbitmq.conf?
If yes, that's not the right place. This is an environment variable.
If not, please show the config file - that's where the problem is.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/4f908494-4584-4994-8d28-468f203d3d8an%40googlegroups.com.



--
Michał

yaniv nayax

unread,
Apr 18, 2023, 12:33:32 PM4/18/23
to rabbitmq-users
Hi Michal,
I was trying to set both strings in the config file:
1.  {rabbit, [{forced_feature_flags_on_init, [quorum_queue, implicit_default_bindings]}]}
2.  RABBITMQ_FEATURE_FLAGS=quorum_queue,implicit_default_bindings

Both were not working - where should I set option #2 if not in the config?
if this works, it would be a solution.

Tnx Yaniv

Michal Kuratczyk

unread,
Apr 18, 2023, 12:45:46 PM4/18/23
to rabbitm...@googlegroups.com
It's an environment variable - you can set it wherever you want as
long as it'll be effective when RabbitMQ starts.
I believe one of the places where you can set it is rabbitmq-env.conf
(https://www.rabbitmq.com/configure.html#customise-environment)

Alternatively, use the advanced config file
(https://www.rabbitmq.com/configure.html#advanced-config-file) with
contents like this:

[{rabbit, [{forced_feature_flags_on_init, [quorum_queue,
implicit_default_bindings]}]}].
> To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/2a9f09ce-97ca-4a9e-a60c-f931af7755f5n%40googlegroups.com.



--
Michał
RabbitMQ team

yaniv nayax

unread,
Apr 19, 2023, 4:57:50 AM4/19/23
to rabbitmq-users
Hi  Michał,
It is now working for me, Thank you so much for your assistance on this!

Yaniv

Reply all
Reply to author
Forward
0 new messages