Agent Troubleshooting

Node Not Reachable


While the Deployment succeeded, after sometime the Agent was not in the Running state and the deployment shows the VM in red (Unreachable).

Applies to

All Clouds and Apps


  1. Verify the following files for additional details:

    • $AGENT_HOME/log/agent.log

    • $AGENT_HOME/log/nohup.err (Linux)

  2. Reboot the VM or manually start the Agent.

Agent and RabbitMQ communication issue


A deployment failed due to Bootstrap Timeout.

Applies to

All clouds and applications.


To troubleshoot issues caused by a communication between the agent and RabbitMQ, do the following.

  1. Check if the broker host IP and broker host port were correctly specified in 
    user-data in the worker VM.

  2. Confirm that the RabbitMQ service is running:

    1. If you deployed Cloud Remote appliance for this region, from the command line of the Cloud Remote appliance enter:

      docker ps  | grep rabbitmq
    2. If you did not deployed Cloud Remote appliance for this region, ensure kubectl on your computer is configured to communicate with the Kubernetes cluster hosting the CloudCenter Suite and issue this command:

      kubectl get pod  | grep rabbitmq
  3. Ensure there are no firewall rules on the Worker VMs blocking outgoing RabbitMQ connections.

  4. Ensure there are no firewall rules blocking the RabbitMQ service, whether it is running in the CloudCenter Suite cluster or on the Cloud Remote appliance.

  5. Optional. If required, open the RabbitMQ console and confirm you can login by using the following format:

    http://<RabbitMQ server IP>:15672
    #Effective Workload Manager 5.1.1, Port 15672 is disabled by default and can be enabled when required.

    If you are not using Cloud Remote, you can find the RabbitMQ server IP from the Worker AMQP IP Address field in the Region Connectivity section of the Regions / Details tab. If you are using Cloud Remote, use the public IP address assigned to your Cloud Remote appliance when you launched it.

  6. Verify from the agent logs that a Node Bootstrap message was sent.

  7. Login to Kibana and verify from the logs that:

    1. A Node Bootstrap message was received  by the cloudcenter-cco service

    2. The cloudcenter-ccm-backend service received messages from the cloudcenter-cco service

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks