Read and Review Automation Anywhere Documentation

Automation 360

Close Contents

Contents

Open Contents

Health Check API response if RabbitMQ fails to start

  • Updated: 8/06/2020
    • Automation 360 v.x
    • Install
    • IQ Bot

Health Check API response if RabbitMQ fails to start

Check the status of each IQ Bot service using the Health Check API if RabbitMQ fails to start.

The Health Check response for RabbitMQ startup failure is different in case of FileManager, Project, Validator, VisionBot as described in the following table.

Service name Health Check response Reason for failure

FileManager

http://<hostname>:<9996>/healthcheck

Failure 1:

localhost refused to connect

Failure 2:

localhost refused to connect

Reason for failure 1:

The RabbitMQ node/service went down when the Filemanager service was running.

Reason for failure 2:

The RabbitMQ node/service was already down when the Filemanager service started.

Project

http://<hostname>:<9999>/healthcheck

Failure:

localhost refused to connect

Reason for failure:

The RabbitMQ node/service is down.

Validator

http://<hostname>:<9995>/healthcheck

Failure:

localhost refused to connect

Reason for failure:

The RabbitMQ node/service is down.

VisionBotManager

http://<hostname>:<9998>/healthcheck

Failure:

localhost refused to connect

Reason for failure:

The RabbitMQ node/service is down.

Gateway-2 service

http://<hostname>:8100/healthcheck

Application: gateway-2

Failure 1:

localhost refused to connect

Failure 2:

localhost refused to connect

Reason for failure 1:

Port is blocked and the Gateway-2 service is running.

Reason for failure 2:

The Gateway-2 service is not running.

Send Feedback