rabbitmqadmin-start.md

With this sequence of commands, we will enable the rabbitmqadmin web interface for rabbit. All commands should be run as root

PATH=/opt/opscode/embedded/bin:$PATH /opt/opscode/embedded/bin/rabbitmqctl list_queues -p /analytics
    
PATH=/opt/opscode/embedded/bin:$PATH /opt/opscode/embedded/bin/rabbitmqctl list_consumers -p /analytics

PATH=/opt/opscode/embedded/bin:$PATH /opt/opscode/embedded/service/rabbitmq/sbin/rabbitmq-plugins enable rabbitmq_management

• Login to chef server primary backend and install the rabbitmq_management plugin

     PATH=/opt/opscode/embedded/bin:$PATH /opt/opscode/embedded/service/rabbitmq/sbin/rabbitmq-plugins enable rabbitmq_management
  

• Restart rabbitmq

     chef-server-ctl restart rabbitmq
  

• Connect to the newly installed rabbitmq web interface credentials for the webui are guest/guest

For Chef Server 11.3.x

http://FQDN:55672/

For Chef Server 12.x

http://FQDN:15672/

• Configure the interface to allow guest user access to the /analytics vhost. By default the guest user is an administrator, but doesn't have explicit access to the /analytics vhost, so we need to set it.

  • The steps are the same for EC11x and Chef Server 12x, but on Chef Server 12x Rabbitmq interface, there is an Admin link at the top. The user list is inside that link. On EC11x, there is a Users link at the top with the same user list inside the link.

  • Users -> guest bold link -> Select /analytics Virtual Host dropdown, click Set Permission button.

  • Click Queues link at top and select Virtual Host: /analytics dropdown item.

  • You should see alaska and erchef queues in a system that has been in-place upgraded from EC 11x and previously had an Analytics 1.0.x system running against it.

  • Select the alaska queue's bolded link, then you can select individual messages and consume them. Be sure that the checkbox that mentions "requeue" is unchecked.