Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dependabot updated rabbitmq and it causes an issue #330

Open
umpa385 opened this issue Dec 2, 2024 · 1 comment
Open

dependabot updated rabbitmq and it causes an issue #330

umpa385 opened this issue Dec 2, 2024 · 1 comment

Comments

@umpa385
Copy link

umpa385 commented Dec 2, 2024

2ccc1d2

I think this update needs to be rolled back because when trying to push an update to opencti rabitmq was put into a crash loop

@timbutler
Copy link

timbutler commented Dec 16, 2024

I think I've come across the same issue, however there's a way around it. Here's what I was seeing in the log:

BOOT FAILED
===========
Error during startup: {error,failed_to_initialize_feature_flags_registry}

{exit,terminating,[{application_controller,call,2,[{file,"application_controller.erl"},{line,511}]},{applica2024-12-16 22:32:31.601396+00:00 [notice] <0.45.0> Application rabbit exited with reason: {failed_to_initialize_feature_flags_registry,{rabbit,start,[normal,[]]}}
tion,'-ensure_all_started/3-lc$^0/1-0-',1,[{file,"application.erl"},{line,367}]},{application,ensure_all_started,3,[{file,"application.erl"},{line,367}]},{rabbit,'-start_it/1-fun-0-',1,[{file,"rabbit.erl"},{line,430}]},{timer,tc,2,[{file,"timer.erl"},{line,595}]},{rabbit,start_it,1,[{file,"rabbit.erl"},{line,426}]},{init,start_it,1,[]},{init,start_em,1,[]}]}
Runtime terminating during boot (terminating)

Crash dump is being written to: erl_crash.dump...[os_mon] memory supervisor port (memsup): Erlang has closed
[os_mon] cpu supervisor port (cpu_sup): Erlang has closed
=INFO REPORT==== 16-Dec-2024::22:32:32.365039 ===
    alarm_handler: {set,{system_memory_high_watermark,[]}}
2024-12-16 22:32:34.288787+00:00 [error] <0.216.0> Feature flags: `stream_filtering`: required feature flag not enabled! It must be enabled before upgrading RabbitMQ.
2024-12-16 22:32:34.294082+00:00 [error] <0.216.0> Failed to initialize feature flags registry: {disabled_required_feature_flag,
2024-12-16 22:32:34.294082+00:00 [error] <0.216.0>                                               stream_filtering}
2024-12-16 22:32:34.304582+00:00 [error] <0.216.0> 
2024-12-16 22:32:34.304582+00:00 [error] <0.216.0> BOOT FAILED
2024-12-16 22:32:34.304582+00:00 [error] <0.216.0> ===========
2024-12-16 22:32:34.304582+00:00 [error] <0.216.0> Error during startup: {error,failed_to_initialize_feature_flags_registry}
2024-12-16 22:32:34.304582+00:00 [error] <0.216.0>

Either before you upgrade to the latest version of OpenCTI with RabbitMQ 4 or if you rollback RabbitMQ to 3.13, you then need to enable the stable feature flags first:

docker exec docker_rabbitmq_1 rabbitmqctl enable_feature_flag all

This will enable all of the stable feature flags for RabbitMQ, including stream_filtering. You can confirm by listing all of the enable feature flags:

docker exec docker_rabbitmq_1 rabbitmqctl --formatter pretty_table list_feature_flags

Then, update the docker-compose config to the latest 4.0 for RabbitMQ, pull the latest images and start the docker instances again. This corrected the issue for me and hopefully helps others.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants