Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Div
classcommandline

20180530:111134.451689:warn:Communication with the license key "445532399" lost.

....

20180530:121042.834152:Checking the available license key "445532399".

20180530:121042.837140:warn:Unable to log in to the key "445532399", feature 0.

20180530:121042.837198:err:HASP runtime (50): Unable to locate any Feature matching scope.

20180530:121042.837250:warn:Failed to log in to the Sentinel HASP key: "445532399".

20180530:121042.837295:warn:Connection to license key:"445532399" id:"1001688" lost.

Application will stop at 31-May-2018 00:10:42.



Monitoring Tools

Linux Toolkit for Charon-AXP/VAX and Charon-PAR

...

The Linux Toolkit provides monitoring functions covering the license-specific log information. For example:

...

Please refer to Charon Linux Toolkit for more information.

Samples of Open Source Tools for Charon-SSP Hosts and

...

other Linux Hosts

There are commercial tools that can be adapted to monitor the Charon emulator log files. However, there are also some Open Source tools that can be used (with the proper customization). Two examples are listed below (this does not constitute a recommendation - but is meant to illustrate what may be available in the Open Source area):

  • Logwatch
    Logwatch is a customizable, pluggable log-monitoring system. It will go through your logs for a given period of time and create a report in the areas that you wish providing the detail that you wish. It is easy to use, but will have to be customized for use with the Charon emulator log files.
  • Zabbix
    A professional comprehensive monitoring tool that can be adapted to most customers' needs. There are also companies providing professional support for customization and implementation.

Additional tools:

  • Standalone license expiration monitoring tool. This was originally part of the Linux Toolkit, but is now available for all Linux-based Charon host platforms. More information is provided further below in this chapter.

Monitoring aksusbd Messages in the Linux System Log

The background process aksusbd and hasplmd log their messages via the journald daemon. These logs can be monitored by the Linux Toolkit. Alternatively, they can be extracted using the journalctl command.

Example: to extract messages specific to the aksusbd software for the last five minutes, use the following command:

...

If a dongle had been removed within this time span, the output is similar to the following:

Div
classcommandline

Aug 12 14:57:49 host1 aksusbd[17450]: aksusbd_usb_dev_remove: device '/dev/aks/hasp/1-14.2'

If a dongle is connected, a message similar to the following will be displayed:

Div

Apr 11 19:44:37 redhat7.localdomain aksusbd[15047]: aksusbd_usb_dev_connect: device '/dev/aks/hasp/2-1'

A journalctl command similar to the one above can be run regularly within a cron-job that sends an alert if the license has been removed. This method of monitoring has the advantage of being independent of different emulator log file formats and the different check periods set for the individual products. 

Charon-AXP/VAX version 4.9 and Charon-PAR version 1.10 and newer also show messages corresponding to the journalctl messages in the emulator log file (with a delay of about one minute) that can be captured by log monitoring tool such as logwatch. Below is a sample for the Charon-AXP/VAX product:

Div

20180413:100557:WARN :1:0000024D:licenseman(1830): Communication with the license key "527889790" lost.

20180413:182106:WARN :1:0000024D:licenseman(1830): Communication with the license key "527889790" restored.

Please note: If you use Charon-AXP/VAX, the Linux Toolkit can be used to implement this monitoring option.

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-AXPCharon-VAXCharon-SSP and Charon-PAR 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.

...

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-AXPCharon-VAXCharon-SSP and Charon-PAR 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.

Monitoring aksusbd Messages in the Linux System Log

The background process aksusbd and hasplmd log their messages via the journald daemon. These logs can be monitored by the Linux Toolkit. Alternatively, they can be extracted using the journalctl command.

Example: to extract messages specific to the aksusbd software for the last five minutes, use the following command:

$ journalctl --since="$(date '+%Y-%m-%d %H:%M:%S' -d '5 minutes ago')" -t aksusbd --no-pager

If a dongle had been removed within this time span, the output is similar to the following:


Div
classcommandline

Aug 12 14:57:49 host1 aksusbd[17450]: aksusbd_usb_dev_remove: device '/dev/aks/hasp/1-14.2'


If a dongle is connected, a message similar to the following will be displayed:


Div

Apr 11 19:44:37 redhat7.localdomain aksusbd[15047]: aksusbd_usb_dev_connect: device '/dev/aks/hasp/2-1'


A journalctl command similar to the one above can be run regularly within a cron-job that sends an alert if the license has been removed. This method of monitoring has the advantage of being independent of different emulator log file formats and the different check periods set for the individual products. 

Charon-AXP/VAX version 4.9 and Charon-PAR version 1.10 and newer also show messages corresponding to the journalctl messages in the emulator log file (with a delay of about one minute) that can be captured by log monitoring tool such as logwatch. Below is a sample for the Charon-AXP/VAX product:


Div

20180413:100557:WARN :1:0000024D:licenseman(1830): Communication with the license key "527889790" lost.

20180413:182106:WARN :1:0000024D:licenseman(1830): Communication with the license key "527889790" restored.



Please note: If you use Charon-AXP/VAX, the Linux Toolkit can be used to implement this monitoring option.

Charon-PAR Special Monitoring Options

...