Agent troubleshooting

Agent install requirements

Typically, when a VM Instance is still in the provisioning phase long after the VM is up, the Instance is unable to reach the platform. Depending on the Agent install mode, it could also mean the platform cannot reach the Instance. You must consider network and configuration requirements to install the Agent successfully when provisioning an Instance.

The most common reason an Agent install fails is the provisioned Instance cannot reach the platform Appliance via the https://ctrl.expedient.cloud over port 443. When an Instance is provisioned, it must be able to reach the platform via https://ctrl.expedient.cloud, or the Agent will not be installed. To summarize, the VM needs internet access with outbound access to https://ctrl.expedient.cloud on Port 443.

Agent install validation

To confirm if the Agent is installed and reporting healthy, navigate to Infrastructure → Compute → Virtual Machines and click on the VM you wish to troubleshoot

On the Information page, the status should be a green and white circle with a white checkmark if the Agent is reporting healthy. Additionally, if the Agent is not installed, there should be no API key in the info section.

Agent restart

In some situations, it may be necessary to restart the Morpheus Agent on the host to re-sync communication from the Agent to the Morpheus appliance.

• Linux
  • On the target host, run sudo morpheus-node-ctl restart morphd and the Morpheus agent will restart. morpheus-node-ctl status will also show the agent status.
• Windows
  • The Windows Agent service can be restarted in Administrative Tools -> Services.