Summary
When the rabbitmq-server is not started on ECX, all VMWare policies will fail, and the policy reports will be empty.
Symptoms
- When attempting to browse ECX policy logs of instances, no logging information is shown
- VMWare Copy and use policies fail without giving any information in the logs ( logs are empty)
- During startup of the ECX, the following error is seen:
(Connect not connect: [Errno 111] Connection refused)
Resolution
The rabbitmq server writes all login ECX; if the rabbitmq server process is not running on the ECX Appliance, no logs will be written; in addition, VMware copies and use policies use rabbitmq for all communication to VADP process and if the rabbitmq server is not running the policies will fail.
Under some circumstances, the rabbitmq service will be set not to start on reboot. To address this, the following commands need to be run:
- chkconfig rabbitmq-server on
- run "chkconfig rabbitmq-server" or chkconfig -list to verify the rabbitmq-server is set to start automatically.
- reboot the appliance to get the setting active or run:
- "/etc/init.d/rabbitmq-server start" and "/etc/init.d/virgo stop" and "/etc/init.d/virgo start"