License logs
Logging can be enabled for the Four Js License Manager (FLM) and/or the license controller.
Requests and responses that are sent and received by the license controller or Four Js License Manager (FLM) may be recorded in log files. These logs are intended for the troubleshooting of licensing issues by decoding and reviewing events. You may be asked to activate logging in order to assist Four Js support with a licensing problem.
Activating this logging feature is dependent on how your license management is implemented.
Local license controller logs
If you are using a license controller (fglWrt or greWrt) for license management, the log feature is configured in the license controller configuration file.
- License controller configuration
-
To affect license for the specified controller, enable logging in its license configuration file (fgllicense or grelicense).
Logs can be enabled using these entries:; License configuration file [log] enabled categories=error,warning,info #,debug directory=${TEMP}
Where:- The
enabled
option enables logging. - The
categories
option specifies the type of events to record in the logs;error
,warning
,info
, anddebug
. Thedebug
category will produce an additional log file with the extension .dlog. - The
directory
option specifies the directory where logs are stored.
- The
- Log file names
-
Log file names correspond to your Genero product license controller:
- fglWrt: fglwrt.log
- greWrt: grewrt.log
- If you enable the
debug
category, additional files will appear with the extension .dlog. These may be requested by your Four Js support center if you encounter issues.Note: The .dlog logs are encoded and are not intended to be readable by users.
If logs are enabled and no directory provided, the output goes to stderr.Tip: License controller logs can also be enabled locally when using an FLM.
Contact your local Four Js support center for additional assistance.