[rabbitmq-discuss] Return of 'getting started, broker runs; can't get status'

J Aaron Farr farra at apache.org
Tue Sep 22 09:42:31 BST 2009

On Tue 22 Sep 2009 16:33, "Sylvain Hellegouarch" <sh at defuze.org> wrote:

> Usually the logs offer the reason or a good hint in regards to the
> failure. You may want to look at them.

Hasn't helped me at least:

    $ rabbitmq-server
    RabbitMQ 1.6.0 (AMQP 8-0)
    Copyright (C) 2007-2009 LShift Ltd., Cohesive Financial Technologies LLC., and Rabbit Technologies Ltd.
    Licensed under the MPL.  See http://www.rabbitmq.com/
    node        : rabbit at gandalf
    log         : /var/log/rabbitmq/rabbit.log
    sasl log    : /var/log/rabbitmq/rabbit-sasl.log
    database dir: /var/lib/rabbitmq/mnesia/rabbit
    starting database             ...done
    starting core processes       ...done
    starting recovery             ...done
    starting persister            ...done
    starting guid generator       ...done
    starting builtin applications ...done
    starting TCP listeners        ...done
    broker running


    $ tail -f *.log
    ==> rabbit-sasl.log <==
    ==> rabbit.log <==
    Repaired persister log - 1 recovered, 0 bad
    =INFO REPORT==== 22-Sep-2009::16:38:28 ===
    Rolling persister log to "/var/lib/rabbitmq/mnesia/rabbit/rabbit_persister.LOG.previous"
    =INFO REPORT==== 22-Sep-2009::16:38:28 ===
    started TCP listener on
    =INFO REPORT==== 22-Sep-2009::16:38:38 ===
    Rolling persister log to "/var/lib/rabbitmq/mnesia/rabbit/rabbit_persister.LOG.previous"

and again:

    $ sudo rabbitmqctl status
    Status of node rabbit at gandalf ...

Shows no changes in rabbit.log or rabbit-sasl.log
   J. Aaron Farr

More information about the rabbitmq-discuss mailing list