[rabbitmq-discuss] Cannot access rabbitmqadmin.

Anthony Oduor antouboduor at gmail.com
Tue Jan 29 11:20:38 GMT 2013


Thanks for your reply.

Yes, installed via *rabbitmq-server-generic-unix-2.8.4.tar.gz* on my
/home/anthony/rabbitmq/

I am able to access the sbin and run the rabbitmq-* scripts with the same
user. In this case, I am not sure how they could be reading different
values of RABBITMQ_ENABLED_PLUGINS_FILE. This just happened yesterday when
restarted the rabbitmq-server, I haven't encountered this before.


On Tue, Jan 29, 2013 at 1:31 PM, Simon MacMullen <simon at rabbitmq.com> wrote:

> Hmm. Your symptoms are consistent with rabbitmq-plugins and
> rabbitmq-server using a different enabled_plugins file. How did you install
> RabbitMQ? I notice that you are invoking rabbitmq-plugins from the current
> directory as a normal user, so did you perform a manual installation?
>
> If so, make sure that both rabbitmq-plugins and rabbitmq-server see the
> same value for RABBITMQ_ENABLED_PLUGINS_FILE.
>
> Cheers, Simon
>
>
> On 29/01/13 07:39, Anthony Oduor wrote:
>
>> Hello,
>>
>> Encountered this issue too. Everything is running fine, ports 4369 with
>> epmd is up, but cannot access the web management page.
>>
>> $ ./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
>> [E] 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
>>
>> But it still failed to activate the plugins this time.
>>
>> The log ends without activating the plugins, see below:
>>
>> ...
>> -- message delivery logic ready
>> starting error log relay
>>   ...done
>> starting networking
>> ...done
>> starting direct client
>>   ...done
>> starting notify cluster nodes
>> ...done
>>
>> broker running
>> ** Found 0 name clashes in code paths
>>
>> RabbitMQ v2.8.4, Ubuntu 10.04
>>
>> Thanks!
>>
>> On Thu, Jan 24, 2013 at 4:26 PM, Simon MacMullen <simon at rabbitmq.com
>> <mailto:simon at rabbitmq.com>> wrote:
>>
>>     Ah - so you were using "rabbitmqctl stop_app" and "rabbitmqctl
>>     start_app" - yes that would not work since they never halt the
>>     Erlang VM. "service rabbitmq-server restart" would have worked
>>     without a reboot.
>>
>>     I guess we should try to make that clearer.
>>
>>     Cheers, Simon
>>
>>
>>     On 24/01/13 05:56, Alex Damian wrote:
>>
>>         I finally got it working. Restarting and stopping the server with
>>         rabbitmqctl did not work. So I rebooted then restarted directly
>>         with the
>>         rabbitmq-server start command and this time it seemed to load
>>         all the
>>         plugins including Mochiweb and I was able to open the admin
>>         webpage. I'm
>>         not sure why it did not work immediately after the plugins were
>>         enabled...however I'm happy with this solution albeit not ideal
>>         since it
>>         required a reboot.
>>
>>         On Tuesday, January 22, 2013 5:23:24 PM UTC-5, Alex Damian wrote:
>>
>>              Hi
>>
>>              I have followed all the instructions on
>>         http://www.rabbitmq.com/__**management.html<http://www.rabbitmq.com/__management.html>
>>         <http://www.rabbitmq.com/**management.html<http://www.rabbitmq.com/management.html>
>> >
>>              <http://www.rabbitmq.com/__**management.html<http://www.rabbitmq.com/__management.html>
>>
>>         <http://www.rabbitmq.com/**management.html<http://www.rabbitmq.com/management.html>>>
>> and enabled the plugin,
>>              but after than there is no webserver running anywhere on my
>>         machine.
>>              There is no way to connect to Mochiweb at all. I have
>>         restarted the
>>              service and still nothing. I have also tried the
>>              "http:///server-name/:15672/" URL with "localhost",
>>         127.0.0.1 and
>>
>>              also the full server name, all of which are /etc/hosts file.
>> My
>>              vhost is the default "/". Should I add something in my
>>         config file
>>              perhaps? I have also tried a /curl/ command and still
>> nothing.
>>
>>
>>              I am running on Fedora Core 17 with all latest libs
>>         including latest
>>              rabbitMQ sw. I have checked the listening ports on the
>>         server and i
>>              only see the AMQP one.
>>              Also I can run rabbitmq-server and rabbitmqctl without
>>         issues. I
>>              have also been able to create exchanges/queues via rabbit.js
>> on
>>              Node. However not having a proper admin tool is a bit
>>         drawback. I
>>              wonder why it's not possible to supply one like (or enhance)
>>              rabbitmqctl. Seems to do the job just fine.
>>
>>              Any help would be greatly appreciated!
>>
>>
>>
>>         ______________________________**___________________
>>         rabbitmq-discuss mailing list
>>         rabbitmq-discuss at lists.__rabbi**tmq.com <http://rabbitmq.com>
>>         <mailto:rabbitmq-discuss@**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>
>>
>>         <https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**
>> rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
>> >
>>
>>
>>
>>     --
>>     Simon MacMullen
>>     RabbitMQ, VMware
>>     ______________________________**___________________
>>     rabbitmq-discuss mailing list
>>     rabbitmq-discuss at lists.__rabbi**tmq.com <http://rabbitmq.com>
>>     <mailto:rabbitmq-discuss@**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>
>>
>>     <https://lists.rabbitmq.com/**cgi-bin/mailman/listinfo/**
>> rabbitmq-discuss<https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss>
>> >
>>
>>
>>
>>
>> --
>>
>> http://about.me/outhorand/bio
>>
>>
>>
>> ______________________________**_________________
>> 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
>



-- 

http://about.me/outhorand/bio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130129/d5f4f261/attachment.htm>


More information about the rabbitmq-discuss mailing list