[rabbitmq-discuss] Hard Down

Wed Oct 30 17:56:07 GMT 2013

Yes, we had cleared the disk issue - the issue appears to be with one of our older tools (designed on 3.1.2) for creating vHosts, Exchanges and Queues automagically - something in the tool goes funky when anything new is created on the 3.2 cluster, or rather, created and then deleted.  Anything it created prior to 3.2 is fine.  We're investigating... thanks for your help!

Thanks,
Kale

-----Original Message-----
From: Emile Joubert [mailto:emile at rabbitmq.com] 
Sent: Wednesday, October 30, 2013 7:42 AM
To: Discussions about RabbitMQ
Cc: Ganann, Kale
Subject: Re: [rabbitmq-discuss] Hard Down

Hi Kale,

On 29/10/13 18:35, Ganann, Kale wrote:
>> We just upgraded to 3.2 last Friday, and the system froze up today.
>> My coworker tried a reboot when rabbitmqctl stop just hung.  Node 2 
>> says it's back, but the management interface is still down, and when 
>> he tries to start the other two nodes he gets the following crash 
>> dump...

Unfortunately the crash dump you supplied is of limited use. The first place to look is the broker logfile (including the sasl log). Was anything logged on any of the cluster nodes at the time of the problem?
I assume you have resolved the disk space issue.

-Emile

This communication contains information that is confidential,
proprietary in nature, and may also be attorney-client privileged
and/or work product privileged. It is for the exclusive use of the
intended recipient(s). If you are not the intended recipient(s) or
the person responsible for delivering it to the intended
recipient(s), please note that any form of dissemination,
distribution or copying of this communication is strictly
prohibited and may be unlawful. If you have received this
communication in error, please immediately notify the sender by replying
to this message and delete this email immediately. Thank you for your cooperation. 

Please be advised that neither Altegrity, its affiliates, its employees
or agents accept liability for any errors, omissions or damages
caused by delays of receipt or by any virus infection in this
message or its attachments, or which may otherwise arise as a
result of this e-mail transmission.