...
| No Format |
|---|
{timestamp} {clientaddr}:{clientport} {clientid} {method} {url} {function}({functionparams}) {newline} |
Incomplete lmdiag output for FlexNet license server
...
If there is a problem with the output produced by the lmutil lmdiag command, you will see the following message in the log:
"Output of the lmutil lmdiag command is incomplete, which can cause incorrect or incomplete data in License Statistics. Please ensure that your license server is able to correctly print out the lmdiag output."
This error indicates that some or all features included in lmstat output are not described in lmdiag, so License Statistics data may be inaccurate. If a specific feature in the lmstat output does not have any users described and lmdiag does not contain any information about this feature, License Statistics creates the feature as both a floating and node-locked type. In addition, a feature that is not described in lmdiag has no expiration date set.
This error may occur because the vendor's configuration doesn't allow printing out required data. This error may be unresolvable if you are unable to change the license server configuration.
Unidentifiable usernames in lmutil output
...
License Statistics identifies and displays usernames using data provided by the license server using a query tool (normally lmutil). If the license server does not provide valid usernames, License Statistics cannot use the data to display the username in the log or the web-based UI.
...
For example, if the lmutil output for CITRIX does not contain valid usernames for specific checkouts, it will use the syntax "string1 (string2)", where string1 is the value of the string stored in place of an actual username and string2 is an additional string to help distinguish users. This data is not recognizable by License Statistics.