<div>On Thu, Nov 17, 2011 at 1:47 PM, Simon MacMullen�<span dir="ltr"><<a href="mailto:simon@rabbitmq.com">simon@rabbitmq.com</a>></span>�wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<div class="im">On 16/11/11 13:52, Sampo Savolainen wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
err was empty and log contained only this:<br><br>Stopping and halting node rabbit@blanko ...<br>...done.<br></blockquote><br></div>...and this was definitely after shutdown had *hung*? Because that looks like it had succeeded. Was the timestamp on the log plausible?</blockquote>
</div><div><br></div><div>You were right that this is worth checking out: It seems it's not the rabbitmq service script which fails. I deleted the shutdown logs, and checked the /var/log/rabbitmq directory after shutdown failed. The logs had not been created.</div>
<div><br></div><div>So it seems having rabbitmq running is preventing another service (network-manager perhaps?) from shutting down cleanly.</div><div><br></div><div><br></div><div>�Sampo<br><br></div>