[rabbitmq-discuss] HTTP api not starting

[Wes Mitchell]

Hi, Simon:

It appears from the output that rabbitmq_management plugins are enabled,
with the exception
of rabbitmq_management_visualiser; is that important?

Also the log file doesn't show anything with rabbitmq_management/ or port
55672. The main broker is up and running.

Output of rabbitmq-plugins list:

$ rabbitmq-plugins list
[e] amqp_client                       2.8.4
[ ] eldap                             2.8.4-git
[ ] erlando                           2.8.4
[e] mochiweb                          1.3-rmq2.8.4-git
[ ] rabbitmq_auth_backend_ldap        2.8.4
[ ] rabbitmq_auth_mechanism_ssl       2.8.4
[ ] rabbitmq_consistent_hash_exchange 2.8.4
[ ] rabbitmq_federation               2.8.4
[ ] rabbitmq_federation_management    2.8.4
[ ] rabbitmq_jsonrpc                  2.8.4
[ ] rabbitmq_jsonrpc_channel          2.8.4
[ ] rabbitmq_jsonrpc_channel_examples 2.8.4
[E] rabbitmq_management               2.8.4
[e] rabbitmq_management_agent         2.8.4
[ ] rabbitmq_management_visualiser    2.8.4
[e] rabbitmq_mochiweb                 2.8.4
[ ] rabbitmq_shovel                   2.8.4
[ ] rabbitmq_shovel_management        2.8.4
[ ] rabbitmq_stomp                    2.8.4
[ ] rabbitmq_tracing                  2.8.4
[ ] rfc4627_jsonrpc                   2.8.4-git
[e] webmachine                        1.7.0-rmq2.8.4-hg

On Fri, Nov 9, 2012 at 2:44 AM, Simon MacMullen <simon at rabbitmq.com> wrote:

> Hmm. If the broker can't listen on the socket then it should refuse to
> start.
>
> On the broken machine, does "rabbitmq-plugins list" show all the plugins
> with rabbitmq_management enabled?
>
> Do you see the plugin being activated in /var/log/rabbitmq/startup_log?
>
> Cheers, Simon
>
> On 09/11/12 00:30, wesm wrote:
>
>> I have rmq installed on two servers. On one, a production linux box, the
>> HTTP
>> api and rabbitmqadmin work fine. On the other, a VMware sandbox, the
>> broker
>> is running, but not listening on 55672. These are both "stock"
>> installations, and /etc/rabbitmq contains an enabled-plugins file with the
>> single entry
>> [rabbitmq_management].
>>
>> I only see INFO messages in the log files.
>>
>> Any clues to help debug would be much appreciated. In particular, if
>> there's
>> something in the initialization sequence that could fail here, that would
>> give me things to check.
>>
>>
>>
>> --
>> View this message in context: http://rabbitmq.1065348.n5.**
>> nabble.com/HTTP-api-not-**starting-tp23251.html<http://rabbitmq.1065348.n5.nabble.com/HTTP-api-not-starting-tp23251.html>
>> Sent from the RabbitMQ mailing list archive at Nabble.com.
>> ______________________________**_________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.**rabbitmq.com<rabbitmq-discuss at lists.rabbitmq.com>
>> https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
>>
>>
>
> --
> Simon MacMullen
> RabbitMQ, VMware
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20121109/7f094f65/attachment.htm>