<div dir="ltr">While experimenting, I just found that deleting the virtual host and recreating it fixed the problem.<div><br></div><div>It's still not ideal in a production scenario :( but I suppose its more manageable than bringing down the whole cluster... </div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 24, 2014 at 12:12 PM, Daniel W. Burke <span dir="ltr"><<a href="mailto:dburke@addictmud.org" target="_blank">dburke@addictmud.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I just realized my last two messages went to Simon directly instead of to the mailing list... my mistake...<div>
<div class="h5"><br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Daniel W. Burke</b> <span dir="ltr"><<a href="mailto:dburke@addictmud.org" target="_blank">dburke@addictmud.org</a>></span><br>
Date: Tue, Jun 24, 2014 at 12:10 PM<br>Subject: Re: [rabbitmq-discuss] Unable to create exchange / queue binding<br>To: Simon MacMullen <<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>><br>
<br><br><div dir="ltr">
We have this happening again in our dev environment. This is alarming, as we're going to go live with rabbitmq in production in two days (with four clusters of three nodes each), and so far the only way we know to get past it is to down the entire cluster.<div>
<br></div><div>Nothing is showing up in the logs for the error, so I don't have any additional information to provide. We'll leave it as-is for as long as possible in the hopes that someone can provide some commands to help troubleshoot, since its not currently preventing anyone from working.</div>
<div><br></div><div>Help!</div><div><br></div><div>Thanks,</div><div>Dan.</div><div><br></div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 18, 2014 at 6:13 AM, Daniel W. Burke <span dir="ltr"><<a href="mailto:dburke@addictmud.org" target="_blank">dburke@addictmud.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">That does not seem like the case to me. All three nodes in the cluster had been up a few days, and queues are mirrored to all nodes in the cluster.</p>
<p dir="ltr">Another potential item of note is that the nodes were restarted last to upgrade from 3.3.1 to 3.3.2. They were restarted one at a time instead of bringing the whole cluster down.</p>
<p dir="ltr">Also, logging seemed to have been stopped until the entire cluster was brought down to fix this error, but I see there's a related fix to that in 3.3.3 now.</p>
<p dir="ltr">Dan.<br>
</p><div><div>
<div class="gmail_quote">On Jun 18, 2014 4:54 AM, "Simon MacMullen" <<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 17/06/2014 19:03, Daniel W. Burke wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
NOT_FOUND - no binding BINDING_NAME between exchange 'amq.direct' in<br>
vhost 'MYVHOST' and queue 'QUEUENAME' in vhost 'MYVHOST'<br>
<br>
This should be a binding that already exists, but for this queue it<br>
doesn't. When trying to create it from the management UI we get the<br>
error (or from the http api)... if we change just one character in the<br>
routing key it works... that's not what we want, but it tells me there's<br>
something deeper wrong.<br>
</blockquote>
<br>
This message means that you are trying to create an already known binding to a queue whih is currently down (i.e. unmirrored and on a down node, or mirrored but only to a ste of nodes all of which are down).<br>
<br>
Does that sound like what's happening?<br>
<br>
Cheers, Simon<br>
</blockquote></div>
</div></div></blockquote></div><br></div>
</div></div></div><br></div></div></div>
</blockquote></div><br></div>