Verbose Debug Log Messages
If a producer enables the verbose information to be displayed in debug logs, you would be observing extra info being printed in the logs.
Enabling the verbose information affects the following events :
• | OUT |
• | IN |
• | QUEUED |
• | DEQUEUED |
• | DENIED |
For instance, the following is the OUT debug log message format after enabling the verbose information:
“feature“ @host (num_license) ^^^ ver user ip pid handle in_use out_of project_name flex_version flex_revision date time is_dup_group ^^^
Terminology |
Description |
feature |
Indicates the feature name. |
@host (num_license) |
Indicates the client’s host name. |
ver |
Indicates the feature’s version as requested in the client application. |
user |
Indicates the client’s user name. |
ip |
Specifies the client’s IP (Internet Protocol) address. |
pid |
Specifies the client’s Process ID. |
handle |
Indicates the client handle. |
in_use |
Specifies the licenses in use. |
out_of |
specifies the total number of licenses including all the licences in use. |
project_name |
Indicates value of the LM project. |
flex_version |
Specifies the FlexNet Publisher version of client. For instance, flex_version for 11.19 version is 11. |
flex_revision |
Specifies the FlexNet Publisher Revision of client. For instance, flex_revision for 11.19 version is 19. |
date |
Indicates the date of operation. |
time |
Indicates the time of operation. |
is_dup_group |
Indicates the value of is_ dup_group attribute. |
For more informaton on the IN, OUT, QUEUED, DEQUEUED, and DENIED debug log messages, see the Informational Messages.
Note:The following shows the difference in the OUT debug log messages without and with enabling the verbose information:
• | By default, the vendor daemon generates the 8:41:54 (demo) OUT: "f1" ADas@BLR-LT-104276 debug log message. |
• | If your vendor has enabled the verbose information, the vendor daemon generates the OUT : 8:41:54 (demo) OUT: "f1" ADas@BLR-LT-104276 ^^^ 1.0 ADas 127.0.0.1 29865 0x12CE 1 3 N/A 11 19 8-8-2023 8:41:56 YES ^^^ debug log message. |
Note:These verbose debug log messages can be used as inputs for the lmreporter tool. For more information, see lmreporter.