RabbitMQ Management console not working

rabbitmq

I have started with RabbitMQ. I have a (windows) machine on which I installed two RabbitMQ nodes as a service – I have choose the nodename, port and service name for each of them. The services are running normally (i see that they are listening in a netstat-a).

I have also installed management plugin with "rabbitmq-plugins enable rabbitmq_management" and restarted both services. But the plugin isn't running – I dont see it listening in a netstat and I can't connect to the management console via browser.

Any idea what could be wrong? Is there any log to see what is goind on?

Updated: when I do rabbitmq-plugins list i get:

c:\RabbitMq\sbin>rabbitmq-plugins list
[e] amqp_client                       3.0.1
[ ] cowboy                            0.5.0-rmq3.0.1-git4b93c2d
[ ] eldap                             3.0.1-gite309de4
[e] mochiweb                          2.3.1-rmq3.0.1-gitd541e9a
[ ] rabbitmq_auth_backend_ldap        3.0.1
[ ] rabbitmq_auth_mechanism_ssl       3.0.1
[ ] rabbitmq_consistent_hash_exchange 3.0.1
[ ] rabbitmq_federation               3.0.1
[ ] rabbitmq_federation_management    3.0.1
[ ] rabbitmq_jsonrpc                  3.0.1
[ ] rabbitmq_jsonrpc_channel          3.0.1
[ ] rabbitmq_jsonrpc_channel_examples 3.0.1
[E] rabbitmq_management               3.0.1
[e] rabbitmq_management_agent         3.0.1
[ ] rabbitmq_management_visualiser    3.0.1
[e] rabbitmq_mochiweb                 3.0.1
[ ] rabbitmq_mqtt                     3.0.1
[ ] rabbitmq_old_federation           3.0.1
[ ] rabbitmq_shovel                   3.0.1
[ ] rabbitmq_shovel_management        3.0.1
[ ] rabbitmq_stomp                    3.0.1
[ ] rabbitmq_tracing                  3.0.1
[ ] rabbitmq_web_stomp                3.0.1
[ ] rabbitmq_web_stomp_examples       3.0.1
[ ] rfc4627_jsonrpc                   3.0.1-git7ab174b
[ ] sockjs                            0.3.3-rmq3.0.1-git92d4ba4
[e] webmachine                        1.9.1-rmq3.0.1-git52e62bc

Best Answer

I have also posted this questions on the RabbitMq mailing list. One nice guy from the rabbitmq answred:

Ah, I think I see the problem. Setting RABBITMQ_SERVICENAME for your services sets RABBITMQ_BASE, which then controls the location of where the RabbitMQ service(s) will look for the enabled_plugins file.

But you are not setting this when invoking rabbitmq-plugins.bat, so it's writing the file to a different location. And sadly there's a bug in the rabbitmq-plugins.bat script which prevents it from looking at RABBITMQ_SERVICENAME.

I'll file a bug to get that fixed. But in the mean time you should be able to get the management plugin started by copying the enabled_plugins file from %APPDATA%\RabbitMQ\enabled_plugins to %APPDATA%\TermaniaDevRabbitMQ\enabled_pluagins and %APPDATA%\TermaniaProdRabbitMQ\enabled_plugins.

Since you're using RabbitMQ 3.x you do not need to reinstall the service, just restart it.

Cheers, Simon

That helped me.

Related Solutions

How to make RabbitMQ listen only to localhost

Putting the following in /etc/rabbitmq/rabbitmq-env.conf will make RabbitMQ and epmd listen on only localhost:

export RABBITMQ_NODENAME=rabbit@localhost
export RABBITMQ_NODE_IP_ADDRESS=127.0.0.1
export ERL_EPMD_ADDRESS=127.0.0.1

It takes a bit more work to configure Erlang to only use localhost for the higher numbered port (which is used for clustering nodes as far as I can tell). If you don't care about clustering and just want Rabbit to be run fully locally then you can pass Erlang a kernel option for it to only use the loopback interface.

To do so, create a new file in /etc/rabbitmq/ - I'll call it rabbit.config. In this file we'll put the Erlang option that we need to load on run time.

[{kernel,[{inet_dist_use_interface,{127,0,0,1}}]}].

If you're using the management plugin and also want to limit that to localhost, you'll need to configure its ports separately, making the rabbit.config include this:

[ {rabbitmq_management, [ {listener, [{port, 15672}, {ip, "127.0.0.1"}]} ]}, {kernel, [ {inet_dist_use_interface,{127,0,0,1}} ]} ].

(Note RabbitMQ leaves epmd running when it shuts down, so if you want to block off Erlang's clustering port, you will need to restart epmd separately from Rabbit.)

Next we need to have RabbitMQ load this at startup. Open up /etc/rabbitmq/rabbitmq.conf again and put the following at the top:

export RABBITMQ_CONFIG_FILE="/etc/rabbitmq/rabbit"

This loads that config file when the rabbit server is started and will pass the options to Erlang.

You should now have all Erlang/RabbitMQ processes listening only on localhost! This can be checked with netstat -ntlap

EDIT : In older versions of RabbitMQ, the configuration file is : /etc/rabbitmq/rabbitmq.conf. However, this file has been replaced by the rabbit-env.conf file.

Ssl – Rabbitmq federation with SSL client certificates not working

When you're using SSL for client authentication, there are two separate CA certificates involved.

One is the one that the server presents as the issuer of the server certificate. The client needs to trust this CA in order to verify that the host's SSL certificate.

The other one is the CA that has issued the client certificate. The server needs to trust this in order to verify the client's SSL certificate.

Even if you are using the same actual CA for both certificates, you still need to inform your server that it should use that CA certificate both for its own certificate and to verify that of the client. The former is done with the option cacertfile=/srv/byteq/config/ca.crt - in order to add the latter, you need to add cacerts="/srv/byteq/config/ca.crt.

There's more information at https://www.rabbitmq.com/ssl.html under the heading "Trust the Client's Root CA".

Best Answer

Related Solutions

How to make RabbitMQ listen only to localhost

Ssl – Rabbitmq federation with SSL client certificates not working

Related Topic