error when trying to add defenitions.json with 'x-delayed-message' to container

[Moran Gibori]

{"init terminating in do_boot",{error,{error,{amqp_error,command_invalid,"unknown exchange type 'x-delayed-message'",none}}}}

Docker container with rabbitmq-delayed-message-exchange plugin enabled

trying to load a defenitions file through 

 docker run -d     -e RABBITMQ_ERLANG_COOKIE="password"     --volume=$(pwd)/rabbitmq.conf:/etc/rabbitmq/rabbitmq.conf    --volume=$(PED)definitions.json:/etc/rabbitmq/definitions.json rabbitmq

[Warren Pang]

what are rabbitmq and erlang versions?

regards.

--
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/3624508a-78e0-4d83-b529-e74008a13ac1o%40googlegroups.com.

[Moran Gibori]

3.8.5 latest from docker hub

To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/CAFi61RvpiMOddy__E6prij1nd2u91UtghxmZJNftD4MhbP%3DcEA%40mail.gmail.com.

[Gerard Boor]

I am running into the same issue with the  rabbitmq_message_deduplication  plugin on Kubernetes. Same error.

init terminating in do_boot ({error,{error,{amqp_error,command_invalid,unknown exchange type 'x-message-deduplication',none}}})

Running the latest rabbitmq-ha helm chart (using the RabbitMQ 3.8.5-alpine image) and setting definitions in values, which creates a definitions file in the right dir in the rabbitmq container, so the process is a bit different than what OP describes, but the result is exactly the same.

It appears that when the definitions are loaded, the plugins involved aren't registered yet, so the exchange type does not yet exist, causing this error. This may be an issue with the order in which things are initialized, or it may be an issue with how the plugin registers its exchange types. If someone from RMQ can confirm which one it is, I can open a ticket on the correct repo.

[Luke Bakken]

Hi Gerard,

Yes this is a known bug that has been fixed in 3.8.6. If you could test your specific scenario using this release candidate and report back, it would help the team immensely.

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.8.6-rc.1

Thanks -

Luke

[Gerard Boor]

Hi Luke,

Thanks for the reply. I can confirm that using image.tag: 3.8.6-rc.1-alpine for the Kubernetes deployment fixes this issue. We are now live with a fully provisioned RabbitMQ with custom exchange types, using the rabbitmq-ha helm chart.

Hope that helps!

Regards,

Gerard