LICENSE.LOG

As noted earlier, if this file exists on the WEB License Manager server in /usr/lib/basic, the manager will record statistics for every session that starts and stops. Below is an example:

06/26 17:54:14 (W) Activate UC=14 GC=0 192.168.24.29 49859 16998

06/26 17:54:22 (W) Activate UC=15 GC=0 192.168.24.129 34086 29393

06/26 18:11:31 (W) Release UC=14 GC=0 192.168.24.129 34086 29393

06/26 19:02:58 (W) Release UC=13 GC=0 192.168.24.29 49859 16998

The first two entries are users starting Tbredserv (Activate). The first entry is the 14 user running Tbredserv. It connected from ip address 192.168.24.29. Since multiple Virtual Machines and Containers can have the same IP address, the WEB License Manager captures a node name CRC value. This node name CRC value is a new string function in the 8.8.3 Tbredserv: INF(2,3). The first entry above has a node name value of 49859. The last value 16998 is the Linux process id.

The second entry is another Tbredserv connection coming from another IP address (with a different node name value).

The third and fourth entries (Release) are Tbredserv sessions releasing. Notice the UC count drops 1 each time.

Other values not as common include: Vanished, *Version, and *Denied*. See Recovering User Counts for Vanished.

06/26 18:31:58 (W) *Denied* UC=64 GC=0 192.168.24.29 49859 31306

This indicates the Basic connection was denied access. This is usually because the user count is maxed out. Notice the UC count is 64.

06/26 19:23:08 (W) *Version UC=12 GC=0 192.168.24.129 00000 28997

This indicates there was a Version mismatch between Basic and the License Manager.

Starting with release level 8.9.0, the WEB License Manager will log the Heartbeat process if the WEB License Manager was started with the -l argument.

02/02 17:10:33 (W) Heartbeat UC=0 GC=0 192.168.24.129 34086

Restarting the WEB License Manager

If for some reason the WEB License Manager needs to be restarted (i.e. after a reboot), it will inherit its last state of known connections. Instead of seeing a Starting message, you will see a Recovery message.

./tslicmgrw

06/26 17:15:33 (W) Recovery UC=13 UL=64 GC=2 GL=62 242000002

Notice the UC and GC values (number of users and ghosts in use) are not 0.

Recovering User Counts

It is possible while the WEB License Manager was not accessible, a Tbredserv task released and could not update the WEB License Manager. When the WEB License Manager recovers, the count of active users will be off.

It is also possible that a Tbredserv process goes away without going through RELEASE (i.e. kill). That also will not be counted.

The Tbredserv cpio file includes a heartbeat monitor. You can control how often it sends a heartbeat to the WEB License Manager (i.e. every 5 minutes). The heartbeat monitor will prompt the WEB License Manager for a list of Tbredserv process ids from that IP address and node name. The heartbeat monitor will then verify each of those process ids are still running Tbredserv. If any process is not still active, the heartbeat monitor will send a Vanished record to the WEB License Manager. The heartbeat monitor runs on the Tbredserv application server. To start it:

./tslicuhbw -d 5

In this example the heartbeat monitor will check every 5 minutes. The heartbeat monitor will send a Vanished status for any process that is not running. You will see the following entry in LICENSE.LOG on the WEB License Manager server.

06/26 18:31:58 (W) Vanished UC=4 GC=0 192.168.24.29 49859 31306

Installing the WEB License Manager Heartbeat Service

Starting with release level 8.8.4, the Tbredserv cpio file will include files for installing the WEB License Manager Heartbeat as a service.

To install the WEB License Manager Heartbeat service, the loadservice.sh script will copy the service file from the TSLICUHBW directory to the appropriate system directory or the service files can be loaded manually.

To install the WEB License Manager Heartbeat service via the script, run the following as root:

# cd /opt/tbred/tbwse/TSLICUHBW
# cp tslicuhbw /usr/lib/basic

To manually install the WEB License Manager Heartbeat service:

# cp /opt/tbred/tbwse/TSLICUHBW/tslicuhbw.systemd /etc/systemd/system/ tslicuhbw.service
# systemctl daemon-reload

The service file defaults to running the WEB License Manager Heartbeat program from the /usr/lib/basic directory with a 5-minute heartbeat interval. If the WEB License Manager Heartbeat program has been installed into a different directory or needs to run with a different interval, change the tslicuhbw.systemd file before installing the service.

Ghost Tasks

The WEB License Manager by default can support up to 62 ghost tasks just like a standard Tbredserv license. If you have multiple application servers, they will share the 62 ghosts. Their combined total number of ghost task will be 62. Since the application server controls the task ids, it is possible for multiple application servers to have G0, G1, G2, G3, etc.

It is possible to increase the number of total supported ghost tasks across multiple application servers. Each application server will still be limited to 62 (G0-G9, GA-GZ, Ga-Gz).

To increase the number of supported ghosts you will need to contact your Thoroughbred Sales Rep to license additional Ghost Licenses and receive a new Activation Code. You will use the WEB License Manager Activation program to add additional ghosts.

./tslicactw -g

You will be prompted to enter the new number of ghost tasks and an Activation Code supplied by Thoroughbred.

From the Web License Manager, version 8.9.1. Open this page in the PDF