Troubleshooting the Operations CTRL Agent

Background

The Operations CTRL (Morpheus) agent facilitates communication and coordination between server workloads and the Operations CTRL platform. It collects data, executes commands, and relays information about the workload’s status, configuration, and resource utilization back to the central Operations CTRL orchestration platform. Agent connectivity is required for management tasks and workflows, such as OS patching, to function.

Troubleshooting Agent Issues

Offline or disconnected agents will appear with a red “X” Health icon when viewing instances under Provisioning > Instances in the Operations CTRL UI

• Check the status of the Morpheus Windows Agent Service and ensure it’s running
  • Windows

If the service is not running, simply right click and start the agent service

• Linux

If the service is not running, run:

sudo systemctl start morpheus-node-runsvdir

• If the service is running and agent connectivity is not restored, test if the server can reach ctrl.expedient.cloud on port 443 either via browser, or powershell
• Windows 

Test-NetConnection ctrl.expedient.cloud -Port 443

TcpTestSucceeded should show True. If not, further network troubleshooting will need to be performed to see why port 443 is blocked from the server.

• Linux

curl https://ctrl.expedient.cloud

• You can also use netcat if curl is unavailable

nc -zv ctrl.expedient.cloud 443

1. If either curl or netcat cannot connect, further network troubleshooting will need to be performed to see why port 443 is blocked from the server.
2. If the server can connect to ctrl.expedient.cloud, run the following command to reconfigure the agent with the OpsCTRL platform, and sync the morpheus server API key with the agent.

sudo morpheus-node-ctl reconfigure