Unbale to create binding between a Exchange and a Queue

[Ojha, Ashish]

Hi Team,

 

We are unable to create a binding between a FANOUT exchange and a Queue using the Management UI ( RabbitMQ Version 3.5.7 )

 

We are trying to bind a queue without any “Routing key” , every time we do, it fails with below error .

 

Error on the Management UI

 

 

Error in the RabbitMQ logs :

 

=ERROR REPORT==== 2-Feb-2016::06:27:16 ===

Channel error on connection <0.8352.10> (<Brok...@host123.1.8352.10>, vhost: '/', user: 'rabbitadm'), channel 1:

{amqp_error,not_found,

            "no binding  between exchange 'NONPROD.PBFUSION.CLIENTCOVERAGE' in vhost '/' and queue 'NONPROD.PBFUSION.CLIENTCOVERAGE.FUSION' in vhost '/'",

            'queue.bind'}

[Michael Klishin]

On 2 February 2016 at 15:21:51, Ojha, Ashish (ashis...@gs.com) wrote:
> =ERROR REPORT==== 2-Feb-2016::06:27:16 ===
>

> Channel error on connection <0.8352.10> (,

> vhost: '/', user: 'rabbitadm'), channel 1:
>
> {amqp_error,not_found,
>
> "no binding between exchange 'NONPROD.PBFUSION.CLIENTCOVERAGE'
> in vhost '/' and queue 'NONPROD.PBFUSION.CLIENTCOVERAGE.FUSION'
> in vhost '/'",
>
> 'queue.bind'}

Are all nodes in this cluster reachable?

Can you send us the output of

rabbitmqctl eval '[ets:tab2list(T) || T <- [rabbit_durable_exchange, 
rabbit_exchange, rabbit_durable_queue, rabbit_queue, 
rabbit_durable_route, rabbit_semi_durable_route, rabbit_route]].' 

(possibly off list) 
--
MK

Staff Software Engineer, Pivotal/RabbitMQ

[Michael Klishin]

A few cases with this specific error do not reveal a specific cause. A couple of people
report that cluster restart makes the issue go away. This looks very much like a distributed
race condition affects internal data store state, at least in some cases :(

[Dev Imagicle]

Hi Michael,

I've the same problem: I want to bind a direct exchange to a queue using a specific routing key. 

As you can see the exchange is already bound to two queues with a different routing key, and I'm able to bound it to the queue AckRemote@VIAREGGIO using any routing key but "TREVISO".

Any suggestion?

Riccardo.