Hi,<div><br></div><div>Since upgraded to 2.5.1 from 2.1.1, one of our rabbit servers refuses to finish startup procedures.. starup_log shows:</div><div><br></div><div><div>AMQP 0-9-1 / 0-9 / 0-8</div><div>Copyright (C) 2007-2011 VMware, Inc.</div>
<div>Licensed under the MPL. See <a href="http://www.rabbitmq.com/">http://www.rabbitmq.com/</a></div><div><br></div><div>node : rabbit@qa</div><div>app descriptor : /usr/lib/rabbitmq/lib/rabbitmq_server-2.5.1/sbin/../ebin/rabbit.app</div>
<div>home dir : /var/lib/rabbitmq</div><div>config file(s) : (none)</div><div>cookie hash : kiHDz4b553meuCVcbBEI4w==</div><div>log : /var/log/rabbitmq/rabbit@qa.log</div><div>sasl log : /var/log/rabbitmq/rabbit@qa-sasl.log</div>
<div>database dir : /var/lib/rabbitmq/mnesia/rabbit@qa</div><div>erlang version : 5.8</div><div><br></div><div>-- rabbit boot start</div><div>starting file handle cache server ...done</div>
<div>starting worker pool ...done</div><div>starting database ...done</div><div>starting codec correctness check ...done</div>
<div>-- external infrastructure ready</div><div>starting plugin registry ...done</div><div>starting auth mechanism cr-demo ...done</div><div>
starting auth mechanism amqplain ...done</div><div>starting auth mechanism plain ...done</div><div>starting statistics event manager ...done</div>
<div>starting logging server ...done</div><div>starting exchange type direct ...done</div><div>starting exchange type fanout ...done</div>
<div>starting exchange type headers ...done</div><div>starting exchange type topic ...done</div><div>-- kernel ready</div><div>starting alarm handler ...done</div>
<div>starting node monitor ...done</div><div>starting cluster delegate ...done</div><div>starting guid generator ...done</div>
<div>starting memory monitor ...done</div><div>-- core initialized</div><div>starting empty DB check ...done</div><div>starting exchange, queue and binding recovery ...</div>
</div><div><br></div><div>At this point it keeps 'doing nothing' forever.. which makes me think it's just re-indexing/recovering queues and messajes, however, the mail log files show the following error:</div>
<div><br></div><div><div>=ERROR REPORT==== 2-Aug-2011::13:27:55 ===</div><div>** Generic server <0.127.0> terminating</div><div>** Last message in was {'$gen_cast',</div><div> {submit_async,</div>
<div> #Fun<rabbit_queue_index.24.55115249>}}</div><div>** When Server state == 2</div><div>** Reason for termination ==</div><div>** {function_clause,</div><div> [{rabbit_queue_index,journal_minus_segment1,</div>
<div> [{no_pub,no_del,ack},</div><div> {{<<144,186,140,223,68,195,225,104,84,142,97,239,10,35,24,96>>,</div><div> {message_properties,undefined,false},</div><div> true},</div>
<div> no_del,no_ack}]},</div><div> {rabbit_queue_index,'-journal_minus_segment/2-fun-0-',4},</div><div> {array,sparse_foldl_3,7},</div><div> {array,sparse_foldl_2,9},</div><div> {rabbit_queue_index,'-recover_journal/1-fun-0-',1},</div>
<div> {dict,map_bucket,2},</div><div> {dict,map_bkt_list,2},</div><div> {dict,map_bkt_list,2}]}</div></div><div><br></div><div>Should I ignore such error??</div><div><br></div><div>Greets</div><div>Pablo</div>
<div><br></div><div>PD: I can zip & send our mnesia files just in case they are needed to debug the issue.</div>