[rabbitmq-discuss] rabbit,failure_during_boot

Tue Dec 17 11:36:45 GMT 2013

On 09/12/2013 15:50, Tiziana Stoesselli wrote:

                      [{rabbit_queue_index,parse_pub_record_body,
                           [<<0,0,0,0,0,0,0,0>>]},
                       {rabbit_queue_index,load_journal_entries,1},

The queue index has ended up with a whole load of zeroes appended to it.

We've seen this happen a few times, usually associated with OS crashes or 
power loss or similar.

We changed the queue index file format to be more resilient to this sort of 
corruption in 3.2.0. I'm not sure if there's anything you can do though if 
you've already got a corrupt file with an older version of RabbitMQ apart 
from reset the node and start again.

Cheers, Simon

Hello Simon,

thank you for the response.
Following you can find my attempt

#rabbitmqctl reset
Resetting node 'Name at zenossoc' ...
Error: unable to connect to node 'Name at zenossoc': nodedown

DIAGNOSTICS
===========

nodes in question: ['Name at zenossoc']

hosts, their running nodes and ports:
- zenossoc: [{rabbitmqctl32151,33034}]

current node details:
- node name: rabbitmqctl32151 at zenossoc
- home dir: /var/lib/rabbitmq
- cookie hash: otG5wqMg04+qfhmRCVkglQ==

[root at zenossoc ~]# rabbitmqctl force_reset
Forcefully resetting node 'Name at zenossoc' ...
Error: unable to connect to node 'Name at zenossoc': nodedown

DIAGNOSTICS
===========

nodes in question: ['Name at zenossoc']

hosts, their running nodes and ports:
- zenossoc: [{rabbitmqctl32189,44438}]

current node details:
- node name: rabbitmqctl32189 at zenossoc
- home dir: /var/lib/rabbitmq
- cookie hash: otG5wqMg04+qfhmRCVkglQ==

any idea?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131217/6da9e97f/attachment.html>