<div dir="ltr">Hi Matthias,<div><br></div><div>Thank you for your help! �I will send you the logs, screenshot, and report privately in the next couple of hours. �If there are any other pivotal folks who want me to send it to them too, please let me know!</div>
<div><br></div><div>-Chris</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Sep 20, 2013 at 5:23 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Chris,<div class="im"><br>
<br>
On 20/09/13 22:00, Chris wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I can try to get the logs. �Of course, during the upgrade nodes went up<br>
and down... �So there could have been a time when the nodes the queue<br>
was on were both down. �But this continued even after all nodes were<br>
back up and the queue was recreated.<br>
</blockquote>
<br></div>
Right. I want to check the logs for anything unusual.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It is very reproducible now on this specific customer system (we haven't<br>
yet resolved it there since I was hoping for an option that doesn't<br>
include clearing mnesia or resetting the nodes). �So, yes, I can make<br>
the binding fail all I want on that system.<br>
</blockquote>
<br></div>
In which case please post the output of 'rabbitmqctl report' from one of the nodes, and a screenshot of the management UI when you get the NOT_FOUND error.<br>
<br>
Regards,<br>
<br>
Matthias.<br>
</blockquote></div><br></div>