Troubleshooting/ Debugging CTE-U
This topic is for collecting information for the Support team so that they can help you resolve your issues as efficiently as possible. When you talk to a Support Engineer, they will request this information. Thales recommends gathering this information before calling them.
Warning
Before enabling logs, configure syslog settings to disable rate limiting.
Application level logs for VMD
- By default, VMD stores its logs in
/var/log/vormetric/vorvmd_root.log
To enable the logs:
Filesystem level logs
The filesystem information defaults to the syslog file which defaults to:
RHEL, SLES, Oracle Linux, Amazon Linux
Debian
To enable the FS logs through either secfsd
or voradmin
:
-
For persistent logs (persist even after service restart) enable with
voradmin
: -
Restart CTE-U:
To set the logs for the current life cycle of the SecFS service, use secfsd:
Note
-
Use the
option to enable the logs for a specific GuardPoint. Otherwise, it is not needed. -
Four is the default value. It indicates that logging is off.
-
Eight is the max value. It indicates the highest debug logging.
Collecting System Information
The debugging steps for CTE-U require collecting system information about the system/OS that is running.
To automatically collect all of the information and create a log file at /var/log/vormetric/cte-xxxxx
:
-
Type:
Collecting CipherTrust Manager Information
-
Collect the policy information like key name and key type.
-
In Policies > Policy Elements, collect the resource set name and corresponding definition.
-
In Policies > Policy Elements, collect the user set name and corresponding definition.
-
Capture the Settings > Profiles details.
-
Click on the appropriate Client and collect the GuardPoint status information.