User guide

Appendix C - Troubleshooting Guide
FLEXLM_DIAGNOSTICS
120 FLEXnet Licensing End User Guide
- Did the server start correctly?
Look for a message such as:
server xyz started for: feature1 feature2.
- What is the output from running lmstat -a?
- Are you running other FLEXenabled products?
- Are you using a combined license file or separate license files?
- Are you using a three-server redundant license server (multiple SERVER lines in your
license file)?
FLEXLM_DIAGNOSTICS
Note The ability for FLEXnet Licensing to produce diagnostic output is controlled by your software
vendor.
FLEXLM_DIAGNOSTICS is an environment variable that causes the application to produce
diagnostic information when a checkout is denied. The format of the diagnostic information
may change over time.
On UNIX, the diagnostic output goes to stderr.
On Windows, the output is a file in the current directory called
flexpid.log, where pid is
the application’s process ID.
Level 1 Content
If FLEXLM_DIAGNOSTICS is set to 1, then the standard FLEXnet Licensing error message is be
presented, plus a complete list of license files that the application tried to use. For example:
setenv FLEXLM_DIAGNOSTICS 1
FLEXlm checkout error: Cannot find license file (-1,73:2) No such file or directory
license file(s): /usr/myproduct/licenses/testing.lic license.lic
Level 2 Content
If FLEXLM_DIAGNOSTICS is set to 2, then, in addition to level 1 output, the checkout arguments
are presented. For example:
setenv FLEXLM_DIAGNOSTICS 2
FLEXlm checkout error: No such feature exists (-5,116:2) No such file or directory
license file(s): /usr/myproduct/licenses/testing.lic license.lic
lm_checkout("f1", 1.0, 1, 0x0, ..., 0x4000)
Note that the error message actually contains two separate problems, which both occurred
during the checkout:
• There’s no such feature in the license it did find