The Engine Shows as "Offline" in the Engine Management UI

Possible solutions:

Check that the engine has been activated. To activate an engine, open the site that contains the engine and then choose "Activate" from the context menu on the row containing the engine.
- Check that the engine server is active. Create a direct SSH connection to the engine server and run the following command:
Copy
```
sudo systemctl status clientmgr
```
- Ensure that the Status is Active:
Copy
```
Active: active (running) since Tue 2022-11-29 19:44:19 UTC; 8s ago
```
- The above command also prints the latest engine logs. Check the output for any clear errors such as:
Copy
```
Process: 53415 ExecStart=/usr/local/bin/clientmgr (code=exited, status=1/FAILURE)
```

Check for any clear errors by running the following command (internal only):

Copy

journalctl -u clientmgr -r

Check the printed output for any clear errors, such as the following:

Copy

Nov 29 19:57:11 ip-10-200-21-138.eu-west-1.compute.internal clientmgr[53431]: Post "https://tenant.ras-tunnels.delinea.app/registrar/registration": remote error: tls: unrecogniz>

Check the Engine Update Version:
- Any engine version 0.0.23 or lower must be manually deleted and a new installation must occur to update to the latest version.
- Verify the UI engine record has been Deleted from the Site. See the following online help page for more information.

Unable to Open an SSH Session From the Web UI

Use telnet or netcat to connect to the target server from the engine server on port 3389. Being unable to connect to the target server may indicate that the problem is occurring on the target server. The same command may also be used to debug SSH problems by connecting to the target server on port 22 (or whichever port on the target is hosting the SSH daemon).

telnet <tar.get.ip.here> 22
netcat <tar.get.ip.here> 3389 OR nc <tar.get.ip.here> 3389

Unable to Open an RDP Session From the Web UI

Telnet into target server from the engine server on port 3389. Being unable to telnet into the target server indicates an issue is occurring on the target server.

Copy

telnet <tar.get.ip.here> 3389

Engine Seems to be Functioning in an Unexpected Manner

Check that the server resources are available and not overloaded
Check available disk/storage space
Copy
```
df -h
```

Check that memory is available and not "swapping"
Copy
```
free -m
```

Check that CPU is not overloaded (check the %Cpu row, item = id/idle)

Copy

top

Setting a Static UUID

UUIDs need to persist between reboots. If you are using any virtualized infrastructure where UUIDs are changing, please make sure to keep the UUID stable.

Setting a Static UUID in Skytap

Before creating a static UUID, check to see if the engine is offline by running the following command:

Copy

sudo systemctl status clientmgr.service

If the web UI shows the engine is offline, proceed to creating a static UUID:

SSH into the server with the following command:
Copy
```
sudo cat /sys/devices/virtual/dmi/id/product_uuid
```
In Skytap > Navigate to the Environment Page > VM Settings
Select the name of the Linux VM from the drop-down.
Copy and paste the UUID into the web UI.

The VM needs to be stopped prior to entering the UUID in the web UI.
Save the web form and start the server.
Run the same terminal commands in the Linux machine to verify it's the same.
Install the PRA engine