RabbitMQ service stops working after you upgrade.
RabbitMQ is not responding correctly in the upgraded cluster environment.
The RabbitMQ nodes must be stopped in the reverse order that they were started. This preserves the order of the master node. To determine the start order, view the /db/rabbitmq/data/*/nodes_running_at_shutdown files on each server. Shut down the node that lists all the nodes first. For example, if you have three nodes that were started, node1, then node2, then node3, the nodes_running_at_shutdown file on node 3 lists node1,node2,node3. Node 2 lists node1,node2. Node 1 list node1. You shut down 3, then 2, then 1.
- Stop RabbitMQ nodes on each VMware Identity Manager appliance in the cluster.
Type rabbitmqctl stop.
Do this for each RabbiMQ node in the cluster before going on.
- Start the RabbitMQ node on the last node stopped.
Type rabbitmq-server -detached.
- Verify that the node started.
Type rabbitmqctl status.
- Follow steps 2 and 3 to start the other RabbitMQ nodes in the cluster in the correct order.
- Verify that RabbitMQ is detached from the cluster.
Type rabbitmqctl cluster_status.
- Restart the VMware Identity Manager service.
Type service horizon-workspace restart.