[rabbitmq-discuss] The rabbitmq-server stop command hangs

Tim Watson watson.timothy at gmail.com
Thu Nov 22 06:25:18 GMT 2012


Thanks for the update Liz. We are looking into this, but 3.0 took precedence for a little while.

On 21 Nov 2012, at 21:59, Elizabeth Liao <eliao at seegrid.com> wrote:

> I took another look at this so I have a couple of things to add:
>  * Trying RabbitMQ 3.0.0 did not resolve any issues
>  * When rabbit hangs, there appears to be lots of channels (400-500) open.  However, it's unclear whether that's cause or effect.
> 

500 channels is no big deal for the server, but if the supervision tree is stuck shutting down its quite likely the network is involved so I'll keep this in mind.

Could you send another inspect trace using 3.0 by any chance?

Cheers
Tim

> Liz
> ________________________________________
> From: rabbitmq-discuss-bounces at lists.rabbitmq.com [rabbitmq-discuss-bounces at lists.rabbitmq.com] on behalf of Elizabeth Liao [eliao at seegrid.com]
> Sent: Thursday, November 15, 2012 7:32 PM
> To: Discussions about RabbitMQ
> Subject: Re: [rabbitmq-discuss] The rabbitmq-server stop command hangs
> 
> Hi Tim,
> 
> I ended up running the script with these commands:
> # su rabbitmq
> $ escript suptree_inspect.beam rabbit at TEST2 rabbit_sup | tee output-rabbit.log
> 
> The output is attached.
> 
> Thanks!
> 
> Liz
> ________________________________________
> From: rabbitmq-discuss-bounces at lists.rabbitmq.com [rabbitmq-discuss-bounces at lists.rabbitmq.com] on behalf of Tim Watson [tim at rabbitmq.com]
> Sent: Tuesday, November 13, 2012 7:32 AM
> To: Matthias Radestock
> Cc: Discussions about RabbitMQ
> Subject: Re: [rabbitmq-discuss] The rabbitmq-server stop command hangs
> 
> Thanks Matthias!
> 
> On 13 Nov 2012, at 11:40, Matthias Radestock wrote:
> 
>> On 13/11/12 11:34, Tim Watson wrote:
>>> Are you using the same account to launch both executables?
>> 
>> Almost certainly not, given...
>> 
>>>> # rabbitmqctl status Status of node test2 at test2 ...
>> 
>> and
>> 
>>>> #  escript suptree_inspect.beam test2 at test2 rabbit_sup | tee output.log
>> 
>> rabbitmqctl likely is the system-wide version which switches to the rabbitmq user. So the escript will need to be run like this:
>> 
>> sudo rabbitmq escript suptree_inspect.beam test2 at test2 rabbit_sup | tee output.log
>> 
>> Regards,
>> 
>> Matthias.
> 
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> Email Confidentiality Notice
> 
> The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law. This message is intended for the sole use of the individual or entity to whom it's addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer.
> Email Confidentiality Notice
> 
> The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law. This message is intended for the sole use of the individual or entity to whom it's addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss


More information about the rabbitmq-discuss mailing list