Let me add some additional information, and re-summarize what I'm seeing.<br><br>In our startup script for RabbitMQ we do the following;<br><br>rabbitmq-server -detached<br>rabbitmqctl status<br><Extract the PID from rabbitmqctl status, write to our PIDFILE><br>
rabbitmqctl wait PIDFILE<br><br>On shutdown, we do:<br><br>rabbitmqctl stop PIDFILE<br>rm PIDFILE<br><br>In normal circumstances, this works just fine hundreds of times in a row. However as mentioned earlier in the thread, sometimes when restarting the node that had a stats database, the "rabbitmqctl wait" hangs.<br>
<br>Thanks,<br><br>Mat<br><br><br><div class="gmail_quote">On Wed, Feb 22, 2012 at 3:05 PM, Matt Pietrek <span dir="ltr"><<a href="mailto:mpietrek@skytap.com">mpietrek@skytap.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I was able to just now repro this again. Because of some layers of scripting, it turns out it's not hanging up when running rabbitmq-server. Rather, it's hanging up when running "rabbitmqctl wait <pidfile>"<br>
<br>The output from rabbitmqctl when run on any node is:<br><br>Waiting for rabbit@play ...�� << Where 'play' is the node that's restarting>><br>pid is 21925 ...�������������������� << Where the PID value is different depending on which node it's run>><br>
<br><br>The last few lines of the event log for the 'play' node:<br><br><br>=INFO REPORT==== 22-Feb-2012::14:52:08 ===<br>Stopping Rabbit<br><br>=INFO REPORT==== 22-Feb-2012::14:52:08 ===<br>��� application: rabbitmq_management<br>
��� exited: stopped<br>��� type: permanent<br><br>=INFO REPORT==== 22-Feb-2012::14:52:08 ===<br>��� application: rabbitmq_management_agent<br>��� exited: stopped<br>��� type: permanent<br><br>=INFO REPORT==== 22-Feb-2012::14:52:08 ===<br>
stopped TCP Listener on <a href="http://0.0.0.0:5672" target="_blank">0.0.0.0:5672</a><br><br>=INFO REPORT==== 22-Feb-2012::14:52:08 ===<br>��� application: rabbit<br>��� exited: stopped<br>��� type: permanent<br><br>=INFO REPORT==== 22-Feb-2012::14:52:08 ===<br>
��� application: os_mon<br>��� exited: stopped<br>��� type: permanent<br><br>=INFO REPORT==== 22-Feb-2012::14:52:08 ===<br>��� application: mnesia<br>��� exited: stopped<br>��� type: permanent<br><br>=INFO REPORT==== 22-Feb-2012::14:52:08 ===<br>
Halting Erlang VM<br><br>=INFO REPORT==== 22-Feb-2012::14:52:13 ===<br>Limiting to approx 924 file handles (829 sockets)<div class="HOEnZb"><div class="h5"><br><br><br><br><div class="gmail_quote">On Wed, Feb 22, 2012 at 10:40 AM, Matt Pietrek <span dir="ltr"><<a href="mailto:mpietrek@skytap.com" target="_blank">mpietrek@skytap.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Unfortunately, I don't see anything in the logs. I'll try again. Is there anything I can do on my end to gather more information?<span><font color="#888888"><br>
<br>Matt</font></span><div><div><br><br><div class="gmail_quote">On Wed, Feb 22, 2012 at 3:45 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On 21/02/12 18:49, Matt Pietrek wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If I try this action on the node with the stats database, rabbitmqctl<br>
waits forever and I have to ctrl-c out. �If I then try "rabbitmqctl<br>
stop", it errors out, saying that the node is down.<br>
</blockquote>
<br></div>
Hmm. Needless to say, this does not happen when I try it :(<br>
<br>
Does anything show up in the logs on that node at this point?<br>
<br>
Cheers, Simon<span><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</font></span></blockquote></div><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>