[rabbitmq-discuss] Problem stopping and starting rabbitmq (branch bug21673)

[scott w]

On Mon, Feb 15, 2010 at 12:03 PM, Matthew Sackman <matthew at lshift.net>wrote:

> Hi Scott,
>
> On Mon, Feb 15, 2010 at 10:54:13AM -0800, scott w wrote:
> > We've been using bug21673 and we are having trouble stopping and starting
> a
> > rabbitmq instance. Looking in the logs, we get the output below after
> > running rabbitmq-server stop. Also in the past I have seen "bad rpc node
> > down" and never knew what that meant or how to fix it. Does rabbitmqctrl
> > stop-app and rabbitmq-server stop do the same or fundamentally diffferent
> > things? An explanation of the difference would be helpful.
>
> They should do the same thing. This one is very odd - it looks like tcp
> listeners are being started as the Erlang VM kernel is being shutdown.
> I've never seen this before, but I'd be slightly surprised if it's
> unique to 21673. Can you reproduce this at all on the default branch?
>

Unfortunately no. To be honest, everything works fine on small loads. We are
using that branch for very large loads where the number of tasks don't fit
into memory. So while the problem itself may not be specific to this branch,
I haven't seen this problem in the default branch because the default can't
handle the loads we're generating.


> Also, which version of Erlang are you running? 12B3 is the minimum for
> that branch, and 13B03 is recommended.
>

12B-4 is what we're building from source. What benefits would we get from
upgrading to 13B03?

Btw, are there any special rabbitmq/erlang commands or tools we can run to
verify that rabbimq is healthy beyond running rabbitmqctl and looking at
logs? I find the logs rather cryptic sometimes.

thanks,
Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100215/6e8f9b05/attachment.htm