Charon Emulator Log File

The configuration of each Charon emulator instance contains the definition and location of an emulator log file, which contains important information about the emulator's activities. It also contains information about which license was found and error messages, for example if a license was removed. The log files are text files and can be viewed using a text editor.

Please note:

For a full description of configuration parameters pertaining to log files, please refer to the respective user's guide of your Charon product.
For the actual location of the emulator log file, check the emulator configuration.
For some hints regarding monitoring tools, please refer to Monitoring Licenses.

Default Log File Location on Linux

If the log file location is not specified explicitly in the configuration, the default log file location on host-based Charon emulator products is as shown in the table below:

Charon Product

Default Log file Location

Charon-AXP/VAX

If the setting of the template configuration is used: directory from which the emulator instance was started.

Charon-SSP

If instance was created using Charon-SSP Manager:
/opt/charon-agent/ssp-agent/ssp/[sun-4m|sun-4u]/<configuration-name>/

Charon-PAR

The default location of the log file is the directory in which the emulator is started. Filename format:

Old versions:

hppa_log-<date-and-time>-000000000.log

New versions:

charon-par.<date-and-time>-0000.log

Default Log File Location on Windows

Charon-AXP/VAX/PDP Product

Version

As Service

Log File Location

< 4.8

Yes

Log files are stored in the home directory of the service.

< 4.8

No

The log file is stored in the same directory as the configuration file of the Charon instance.

>= 4.8

Yes

The log file is stored in the home directory defined when creating the Charon instance via the Virtual Machines Manager.

(The Virtual Machines Manager always starts an emulator instance as a service.)

Charon-AXP/SMA Product

There is no default. The parameter must be specified when an emulator instance is created.

Examples

The following shows the license related log entries at the startup of Charon-AXP for Windows versions up to version 4.8:

The following shows a periodic license check on the same system after the license has been removed:

And the following shows another periodic license check where the license is present again:

Please note: the system used to collect the examples above has two USB dongles installed. You can see that in the first sample Charon-AXP selects one of the dongles and in the last example it selects the other one, because no primary key has been defined.

The log file format in version Charon-AXP/VAX on Windows version 4.9 and above has changed. Below is a sample output showing the removal of a license key:

Please note that the configuration parameter log_repeat_filter is set to on by default for Charon-AXP/VAX on Windows. To receive all messages, this parameter must be set to off in the emulator configuration file. This will create a more detailed output as shown below. In particular, it shows the grace period after which the emulator will stop:

Please note: the format of the log files is different for the various Charon emulator products, but they provide very similar information.

The following shows the log entries of a Charon-SSP instance on Linux for a situation similar to above (emulator start, license missing at periodic check and found again at next check):

System Log Files

System Log File on Linux

On systems using systemd, which uses the journald utility to log messages, the messages for the Sentinel runtime software (aksusbd) can be viewed using the journalctl command.

On systems using syslog or a variant thereof the Sentinel messages can be found in the file /var/log/messages.

The following is an example for Sentinel runtime messages logged via journald showing the aksusbd startup and the adding and removing of a HASP dongle.

Sentinel Runtime Driver Log Files

You can enable access and error logging in Sentinel ACC. Please refer to the following article: Enabling logging in Sentinel Admin Control Center.