| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
...
|
...
The following very basic example shows how to monitor the emulator log files with logwatch and send an email if the dongle removal message appears in the emulator log file.
This example does not apply to Charon-SSP Baremetal.
| Note |
|---|
Most of the messages show in the examples above are not written to the emulator log file immediately when the license is removed. They are written when the periodic license check is performed. Exception: Charon-AXP/VAX 4.9 and Charon-HPA 1.10 and higher also write messages to the emulator log - with a short delay - that reflect the messages written to the system log by aksusbd. The aksusbd daemon reports the removal of a license almost instantaneously in the system log. If possible, use the monitoring capabilities of the Charon Linux Toolkit. This will provide alerts for both message types and additional monitoring features, for example monitoring and alerting based on counters. |
...
| Info |
|---|
The Charon-AXP/VAX log file configuration can be set to automatically rotate the log file at configurable intervals. If this is the case, the currently active log file can be accessed by a softlink symbolic link with the default name Note: Even though there would have to be frequent runs to catch the message about a removed dongle before the emulator stops, there is a small risk that the log rotation and the logwatch run could overlap, causing the dongle removal message to be missed. Hence, the use of rotating log files is not recommended when using logwatch. This risk can be avoided by using the Linux Toolkit. |
...
| Info |
|---|
Some versions of logwatch convert the log file path to lowercase. This prevents the log files from being found if uppercase characters are used in the LogDir target. A workaround is to create a softlink symbolic link consisting of lowercase characters pointing to the target directory and to use the softlink symbolic link as the LogDir value. |
2. Create the service definition file:
...
Monitoring aksusbd Messages in the Linux System Log
This example does not apply to Charon-SSP Baremetal as the underlying operating system is not accessible to the user.
The background process aksusbd logs its messages via the journald daemon. These logs can be extracted using the journalctl command.
...
| Info |
|---|
If you use Charon-AXP/VAX, the Linux Toolkit can be used to implement this monitoring option. |
| Div | ||
|---|---|---|
| ||
Charon License Expiration Check
The Charon Linux Toolkit includes a license expiration check utility that can send alert emails, and/or execute a custom script, a specified number of days before the license expires. This utility can be installed in standalone-mode to be used on Charon-AXP, Charon-VAX,Charon-SSP (non-Baremetal versions) and Charon-HPA without installing the Charon Linux Toolkit.
To download the utility, you must issue a request via email to the Stromasys support team or ask your reseller.
Please refer to How-to install Charon license expiration check on a Linux server for detailed installation and configuration instructions.
Charon-HPA Special Monitoring Options
...
Starting with version 4.9 of Charon-AXP/VAX, logmond will also monitor messages with code 0000040B in the log file (indicating that the emulator has started to use a different license). If such a message occurs, it will run a file called license_changed.bat. The examples in this section refer to the nolicense.bat file.
To see all the command-line options of the utility open a command window (press WIN+R and enter cmd.exe or use the Start menu) and enter the following command:
...