Black Box ET0010A User Manual
Learning About Problems
EncrypTight User Guide
241
Viewing Log Files
Each component in the EncrypTight system creates and maintains log files that you can use to
troubleshoot issues. This section includes the following topics:
troubleshoot issues. This section includes the following topics:
●
●
●
ETPM Log Files
ETPM and ETEMS record significant events and failures in the application log. The application log file is
a fixed length list of entries that records significant events and failures in ETEMS and ETPM.
a fixed length list of entries that records significant events and failures in ETEMS and ETPM.
The events recorded in the application log include:
●
Communication operations and failures
●
SSH connections
●
Runtime exceptions, which occur when incorrect or corrupted data is sent by ETEMS or ETPM, or
received from a PEP. Contact customer support if you receive an error of this type.
received from a PEP. Contact customer support if you receive an error of this type.
EncrypTight provides several options for viewing application log events. You can view log events from
within ETPM or ETEMS by selecting View > Application Log on the main menu bar. You can also
configure EncrypTight to send log events to a syslog server, or export the log as a text file.
within ETPM or ETEMS by selecting View > Application Log on the main menu bar. You can also
configure EncrypTight to send log events to a syslog server, or export the log as a text file.
For more information on the application log, refer to
.
ETKMS Log Files
Each ETKMS creates a daily log file (kdist.log) and stores these files in the /var/log/etkms directory on
an external ETKMS and in the \tools\ETKMS\log directory on a local ETKMS (relative to the installation
directory). These logs provide information about significant events and failures in ETKMS
communications with the ETPM and PEPs. View the daily log file with any text editor for each day in
question. Communications failures are clearly marked with an ERROR tag.
an external ETKMS and in the \tools\ETKMS\log directory on a local ETKMS (relative to the installation
directory). These logs provide information about significant events and failures in ETKMS
communications with the ETPM and PEPs. View the daily log file with any text editor for each day in
question. Communications failures are clearly marked with an ERROR tag.
When the ETKMS saves a daily log file in order to start a new one, it names the file as
kdist.log.xxxx-xx-xx
where
xxxx-xx-xx
is the year, month and date of the log file (for example, 2010-05-05).
You can view the available log files with a text editor. With external ETKMSs, you need to log in directly
on the ETKMS server (if you have physical access to the ETKMS), or you can use an ssh client to log in
remotely and retrieve the log file.
on the ETKMS server (if you have physical access to the ETKMS), or you can use an ssh client to log in
remotely and retrieve the log file.
On a periodic basis, you can delete or archive any or all of these daily log files without affecting the
operation of the ETKMS or EncrypTight.
operation of the ETKMS or EncrypTight.