Q100033: How to interpret a FLU license diagnostic

Follow

SUMMARY

The following article discusses how to interpret a Foundry License Utility license diagnostic. 

MORE INFORMATION

The filename of a FLU Diagnostic encodes the machine and a timestamp thus: fld_machine hostname_YYYMMDD_HHMM_SS.log


NOTE:
If your diagnostic output file is very large, then this is most likely because you are diagnosing a license server machine and the RLM and/or FLEXlm server logs, contained in the diagnostic, are very large. If you STOP and START the RLM Server and/or FLEXlm Server, the server log(s) will overwrite and begin from zero size.


=================================================================
========== Foundry License Diagnostics (Version 7.1v1) ==========
=================================================================

information about the machine

========== RLM Environment Variable Settings ========================

settings that point to rlm licenses. (rarely significant in debug)

====================================================================
================== RLM License File(s) Found =======================
====================================================================

lists all rlm license files found in the places we look for rlm licenses

===================== Reading license file =====================

contents of rlm license file. one of these sections for each rlm license found

=============== No License Option File(s) Found ===================

if there's an rlm option file, what is in it (rarely significant in debug)

=========== FLEXlm Cache ========================

settings that point to flexlm licenses. (rarely significant in debug)

========== FLEXlm Environment Variable Settings ========================

settings that point to flexlm licenses. (rarely significant in debug)

=======================================================================
================== FLEXlm License File(s) Found =======================
=======================================================================

lists all flexlm license files found in the places we look for flexlm licenses

===================== Reading license file =====================

contents of flexlm license file. one of these sections for each flexlm license found

=============== No License Option File(s) Found ===================

if there's an rlm option file, what is in it (rarely significant in debug)

======================= RLM Server Log ==============================

rlm server event log; important when there are rlm floating licenses installed

======================= RLM Boot Log ==============================

rlm server boot log (rarely significant in debug)

===================== rlmUtil Output =============================

rlm server event log; important when there are rlm floating licenses installed;
the bottom part shows types and counts of licenses ready to serve

===================== RLM Server Script =====================

rlm server startup script installed with flt7.0 (rarely significant in debug)

======================= FLEXlm Server Log ==============================

flexlm server event log; important when there are flexlm floating licenses installed

======================= FLEXlm Boot Log ==============================

flexlm server boot log (rarely significant in debug)

===================== lmUtil Output =============================

flexlm server event log; important when there are flexlm floating licenses installed; the bottom part shows types and counts of licenses ready to serve

===================== FLEXlm Server Script =====================

flexlm server startup script installed with flt7.0 (rarely significant in debug)

======================= RLM License Log ==============================

rlm license error event log; written by products (e.g. nuke, mari, etc.).
Very important when this machine got a license error when trying to run a rlm-licensed product

======================= FLEXlm License Log ==============================

flexlm license error event log; written by products (e.g. nuke, mari, etc.).
Very important when this machine got a license error when trying to run a flexlm-licensed product

=====================================================================
================ End Foundry License Diagnostics ====================
=====================================================================


============================================
========== Luxology License Files ==========
============================================

lists all Luxology license files found in the places  where Modo and Modo plug-ins look for licenses. Modo plug-ins will only look here. If Modo does not find a license here, Modo  will then look in the standard rlm license directories.

Was this article helpful?
0 out of 0 found this helpful