[rabbitmq-discuss] Unable to create exchange / queue binding
Daniel W. Burke
dburke at addictmud.org
Tue Jun 17 20:15:33 BST 2014
Well, we were keeping somebody from working, so we found an old thread that
recommended shutting down the entire cluster... that did the trick... when
it came back up everything was good again.
I'd still like to know if someone has any suggestions on what to look
for/at if it happens again. We're getting ready to go live in production
hopefully this week with 4 RMQ clusters of 3 nodes each... a 5th cluster to
be added in a few weeks... makes me nervous that we might have to do that
On Tue, Jun 17, 2014 at 2:12 PM, Daniel W. Burke <dburke at addictmud.org>
> Sorry, I forgot to include that we're running version 3.3.2, erlang R16B03
> on CentOS6.5
> On Tue, Jun 17, 2014 at 2:03 PM, Daniel W. Burke <dburke at addictmud.org>
>> When trying to create the binding for a queue, we're hitting a
>> frustrating problem at the moment. (The names have been changed to protect
>> the innocent).
>> NOT_FOUND - no binding BINDING_NAME between exchange 'amq.direct' in
>> vhost 'MYVHOST' and queue 'QUEUENAME' in vhost 'MYVHOST'
>> This should be a binding that already exists, but for this queue it
>> doesn't. When trying to create it from the management UI we get the error
>> (or from the http api)... if we change just one character in the routing
>> key it works... that's not what we want, but it tells me there's something
>> deeper wrong.
>> This is our development cluster, so we can do whatever to it...
>> It's a three node cluster, each node on it's own VM.
>> Any help in resolving this would be great. We're banging our head
>> against our desks on this one.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss