Hi Simon,<div><br></div><div>Usually i used command "/sbin/service rabbitmq-server stop" to stop the rabbitmq.</div><div><br></div><div>Is it possible the command invoke the "rabbitmqctl stop"?</div><div>
<br></div><div>If yes, then it explain the situation.</div><div><br></div><div>Regards,</div><div>Wong<br><br><div class="gmail_quote">On Wed, Oct 17, 2012 at 5:40 PM, 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 class="im">On 17/10/12 03:04, Wong Kam Hoong wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Simon,<br>
<br><div class="im">
I checked the log and noticed every time when start this particular<br>
RabbitMQ, the log showed some error messages as follow:<br>
<br>
=ERROR REPORT==== 4-Oct-2012::05:46:57 ===<br>
Mnesia(nplay@app2): ** ERROR ** mnesia_event got {inconsistent_database,<br>
starting_partitioned_network, nplay@web1}<br>
<br>
=ERROR REPORT==== 4-Oct-2012::05:46:57 ===<br>
Mnesia(nplay@app2): ** ERROR ** mnesia_event got {inconsistent_database,<br>
starting_partitioned_network, nplay@web2}<br>
<br>
Why the errors logged? Is it related to my cluster setting?<br>
</div></blockquote>
<br>
That log message ("starting_partitioned_<u></u>network") means that Mnesia detected it was partitioned last time it was up, and is recovering from it now (where the recovery is fairly brutal - the node logging that message has thrown away any local changes, and has resynchronised with whichever nodes it found running).<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is production environment, I can guaranteed no one dare to execute<br>
the command "rabbitmqctl stop".<br>
</blockquote>
<br></div>
Well, I can promise that we only log that message "Halting Erlang VM" in response to "rabbitmqctl stop". If you don't believe me you can check - it's emitted in rabbit:stop_and_halt():<br>
<br>
<a href="http://hg.rabbitmq.com/rabbitmq-server/file/rabbitmq_v2_8_x/src/rabbit.erl#l310" target="_blank">http://hg.rabbitmq.com/<u></u>rabbitmq-server/file/rabbitmq_<u></u>v2_8_x/src/rabbit.erl#l310</a><br>
<br>
which is only invoked here:<br>
<br>
<a href="http://hg.rabbitmq.com/rabbitmq-server/file/rabbitmq_v2_8_x/src/rabbit_control.erl#l161" target="_blank">http://hg.rabbitmq.com/<u></u>rabbitmq-server/file/rabbitmq_<u></u>v2_8_x/src/rabbit_control.erl#<u></u>l161</a><br>
<br>
- the handler for "rabbitmqctl stop".<br>
<br>
Cheers, Simon<div class="HOEnZb"><div class="h5"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</div></div></blockquote></div><br></div>