Agent Health Utility
The agenthealth
utility validates:
-
Super-user privilege
-
CTE Agent installation
-
CTE registration to CipherTrust Manager Server
-
CTE processes/ modules that are running
-
Available disk resources
-
Current GuardPoints
-
Tests if the agent can reach the GuardPoints
-
CTE log directory resource status
-
This directory contains pending CTE log files for upload. This utility reports the size and number of pending files for upload. These text files are logs that contain vmd/SecFS information. They are regenerated whenever secfs restarts. If the number of files is unexpectedly large, this can indicate a problem.
The Agent Health check script
By default, the agenthealth
script is installed in /opt/vormetric/DataSecurityExpert/agent/vmd/bin
.
To run the agenthealth
check script, type:
System Response
Agent Health Return Codes
Previously, the agent health return codes were only available in /var/log/vormetric/agenthealth.log
. Now, the following options are also available through the help pages:
Help
This agent health script checks various facets of the CipherTrust agent to make sure that everything is functioning properly. Results are also logged to /var/log/vormetric/agenthealth.log
.
Syntax
Return Codes
Use the return code option to get a list of the return codes and what they mean. The codes are returned if the Agent is not running.
Syntax
Response
Return Code | Definition |
---|---|
EPERM | User is not root. |
ENOENT | One of the programs used in this script does not exist. See /var/log/vormetric/agenthealth.log for which program is missing. |
ENOPKG | Agent software is not properly installed. Agent configuration directory is missing or corrupt. See /var/log/vormetric/agenthealth.log for more details. |
EPROTO | Agent is not registered to a key manager. Register the agent to a key manager and try again. Try the wait option if the agent has never started correctly after registration. See /var/log/vormetric/agenthealth.log for more details. |
EIO | Kernel modules are not loaded. To load a kernel module, type: /etc/vormetric/secfs start |
ESRCH | VMD is not running. To start vmd manually, type: /usr/bin/vmd |
SECFSD | Secfsd is not running. To start the secfsd manually, type /usr/bin/secfsd |
EHOSTUNREACH | Unable to reach the Key Manager. Check network connectivity. |
ECONNREFUSED | VMD is not listening. VMD did not finish initialization. See /var/log/vormetric/vmd.log |
EWOULDBLOCK | VMD is attempting to connect to the Key Manager but has exceeded the designated wait time. Check /var/log/vormetric/vmd.log to fix any issues and retry. |
Wait Time
Use --w to set a maximum wait time in seconds. The minimum is 10 seconds to test for the VMD to Key Manager initial contact. The default setting is 0, which means that there is no wait. Maximum is 1200 seconds.
Syntax
Example
Response
If the customer did not use the wait time options, the output would look similar to the following: