Closed ChesterMino closed 6 days ago
@ChesterMino how is this relevant as an issue in the documentation website?
Take a look at the 3.13.3
release notes.
Duplicate of #11324 (judging from the little information we have), although https://github.com/rabbitmq/rabbitmq-server/pull/11318 (which stems from Erlang 26's stricter TLS setting validation) can also be relevant: Shovels may fail to start because of that setting, which simply triggers #11324 in environments where it previously was never present.
Hei, sry for opening in wrong topic. Thx for references.
Describe the bug
Dear Team,
After upgrading from 3.8.2 to 3.13.2 we started to experience issues, when some of the dynamic shovels cannot be deleted. The issue was reproduced several times during last few weeks.
Reproduction steps
Shovel with the name ‘my-shovel’ was not found on virtual host '/'
rabbitmqctl clear_parameter shovel “my-shovel”
, following msg is returned:Clearing runtime parameter “my-shovel" for component "shovel" on vhost "/" ... Error:{:noproc, {:gen_server, :call, [:rabbit_shovel_dyn_worker_sup_sup, :which_children, :infinity]}}
Expected behavior
Keeping consistency of defined shovel(s)
Additional context
We are running 5 nodes cluster of 3.13.2 (binaries) with erlang 26.2.5
Thanks!
Dominik