Log files and debugging

Logging can be enabled for the Four Js License Manager (FLM).

Requests and responses that are sent and received by the 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.

FLM logs

Logs can be enabled by setting the log entries in the $FLMDIR/etc/flmprofile.
FLM configuration

To affect licenses managed by the FLM server, enable logging in its configuration file. 

; Four Js License Manager configuration

# ...

[log]
enabled=true
directory="${FLMDIR}/log"
categories="error,warning,info" # debug
maxfiles=5
maxsize="512M"
# ...
Where:
  • The enabled option, enables logging.
  • The categories option specifies the type of events to record in the logs; error, warning, info, and debug. The debug category will produce an additional log file with the extension .dlog.
  • The directory option specifies the directory where logs are stored.
  • The maxsize option specifies the maximum log file size. Log files will be rotated automatically when the specified size is reached. The default value is -1 (no limit).
  • The maxfiles option specifies the number of log files to keep before rotating. The default value is -1 (no limit). For more information on log file rotation, see Log file rotation.

After making a configuration change, you will need to restart the FLM. After the restart, you get the log file in the directory you specified.

For more information on working with the configuration file, see Configure the License Manager and Example: flmprofile.

FLM Log files
The FLM tool generates two distinct log files in the specified directory:
  • flmprg.log is the log created by the flmprg command.
  • flmprgd.log is the FLM daemon log file. This file records details of events set in the categories configuration. This file is affected by the log configuration for file rotation specified by maxfiles and maxsize. For more information on log file rotation, see Log file rotation.
  • If the category debug is enabled, the FLM produces an additional log file with the extension .dlog.
    Note: The .dlog logs are encoded and are not intended to be readable by users. These may be requested by your Four Js support center if you encounter issues.
    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. For more information see the License logs page in Install and License your Genero Products manual

Contact your local Four Js support center for additional assistance.

Log file rotation

You enable the log rotation mechanism by configuring the maxsize and maxfiles elements.

When the current log file (flmprgd.log) reaches maxsize, the FLM closes it. It rotates it by renaming and renumbering the number of log files (maxfiles) you have configured it to keep; flmprgd.log, becomes flmprgd.1.log, flmprgd.1.log becomes flmprgd.2.log, and so on. It deletes the log file whose number exceeds the maxfiles value. It creates a new empty log file (flmprgd.log) after the current one is rotated.