[rabbitmq-discuss] plugins not loading.

Tue Jan 31 10:59:23 GMT 2012

Hmm, interesting. I know absolutely nothing about the FreeBSD port, it's 
possible it's just broken since plugin activation is a new concept in 2.7.0.

(Is the packager around on this list?)

So it looks like rabbitmq-plugins is finding the plugins and writing the 
file in the correct location. RabbitMQ is then *not* complaining about 
the plugins not being found, it's not even trying to activate them. 
Presumably therefore it's not seeing the enabled plugins file.

So it's possible that the environment variable ENABLED_PLUGINS_FILE is 
getting set to some bogus value by /usr/local/etc/rc.d/rabbitmq. In 
theory that script should not need to set that variable at all, assuming 
it starts rabbit via rabbitmq-server. Which it should, but like I said, 
I don't know about the FreeBSD packaging...

Cheers, Simon

On 31/01/12 03:47, dksayers wrote:
> I am trying to get the administration plugin working with
> rabbitmq-2.7.0 on
> my FreeBSD 8.2-STABLE amd64 machine. I install via the FreeBSD ports
> tree where erlang-lite-r14b04_1,1 is also built and installed as a
> dependancy. I then did the following:
>
> # rabbitmq-plugins enable rabbitmq_management
> The following plugins have been enabled:
>    mochiweb
>    webmachine
>    rabbitmq_mochiweb
>    amqp_client
>    rabbitmq_management_agent
>    rabbitmq_management
>
> Plugin configuration has changed. Restart RabbitMQ for changes to take
> effect.
> # cat /etc/rabbitmq/enabled_plugins
> [rabbitmq_management].
>
> # /usr/local/etc/rc.d/rabbitmq start
> Activating RabbitMQ plugins ...
> 0 plugins activated:
>
> #
>
> When I try to access port 55672 I am told 'Unable to connect'. It
> seems
> that my plugins are not loading but I have no idea why. The log files
> provide no beneficial information. What have I missed.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

-- 
Simon MacMullen
RabbitMQ, VMware