7.3

Table Of Contents
5 Restart the identity manager and elastic search services.
service horizon-workspace restart
service elasticsearch restart
RabbitMQ Cannot Resolve Host Names
RabbitMQ uses short host names for vRealize Automation appliances by default, which might prevent
nodes from resolving one another.
Problem
You try to join another vRealize Automation appliance to the cluster, and an error similar to the following
occurs.
Clustering node 'rabbit@sc2-rdops-vm01-dhcp-62-2' with rabbit@company ...
Error: unable to connect to nodes [rabbit@company]: nodedown
DIAGNOSTICS
===========
attempted to contact: [rabbit@company]
rabbit@company:
* unable to connect to epmd (port 4369) on company: nxdomain (non-existing domain)
current node details:
- node name: 'rabbitmq-cli-11@sc2-rdops-vm01-dhcp-62-2'
- home dir: /var/lib/rabbitmq
- cookie hash: 4+kP1tKnxGYaGjrPL2C8bQ==
[2017-09-01 14:58:04] [root] [INFO] RabbitMQ join failed with exit code: 69, see RabbitMQ logs for
details.
Cause
Your network configuration does not allow vRealize Automation appliances to resolve each other by short
host name.
Solution
1 For all vRealize Automation appliances in the deployment, log in as root to a console session.
2 Stop the RabbitMQ service.
service rabbitmq-server stop
3 Open the following file in a text editor.
/etc/rabbitmq/rabbitmq-env.conf
Installing vRealize Automation
VMware, Inc. 163