Log file guide

Where to Find License Manager Log Files

Before you can analyze license usage, denials, sessions, or peak concurrency, you need the right log file from your license manager. This guide explains where to look for common license manager logs and how they are usually enabled.

Exact paths and settings can vary by vendor, product, operating system, and installation method. If your environment is managed by another team, check with the license server administrator before changing service settings.

Analyze a Log File Supported License Managers

Start with the existing log

In many environments, license logging is already enabled. Before changing anything, check the license server service, vendor admin tool, or configuration file to see where the current log is being written.

Use a copied log file for analysis whenever possible. Avoid editing or moving active logs while the license server is running unless your vendor documentation says it is safe.

Make service or configuration changes during a maintenance window. Back up configuration files before editing license manager settings.

FlexLM / FlexNet Publisher Debug Log

For FlexLM and FlexNet Publisher environments, the most common file used for quick analysis is the debug log written by lmgrd and the vendor daemon.

Where to find it

On Windows, check LMTOOLS or the license service configuration. In LMTOOLS, open the Config Services tab and look for the field named "Path to the debug log file."

Common locations may include:

C:\ProgramData\FLEXlm\lmgrd\debug.log
A vendor-specific folder under C:\ProgramData
A custom path configured by the software vendor or license administrator

On Linux or command-line installations, check the startup command, service file, or init script for an lmgrd command using the -l option.

Example: lmgrd -c /path/to/license.dat -l +/var/log/flexlm/vendor-debug.log

How to generate or enable it

If the debug log is not configured, set a debug log path in LMTOOLS or start lmgrd with the -l option. Adding + before the log path usually means new entries are appended instead of overwriting the file.

Example: lmgrd -c /path/to/license.dat -l +/path/to/debug.log

Restart the license service during a maintenance window if the service configuration is changed.

What to upload

Upload the debug log that contains license activity lines such as checkouts, checkins, denials, timestamps, and vendor daemon messages. If you expect denial data but do not see it, check whether the vendor options file suppresses denial logging.

RLM Report Log

For Reprise License Manager, the best file for usage analysis is usually the RLM report log, not the general debug log.

Where to find it

RLM report logging is normally configured in the ISV options file. This file may be referenced from the ISV line in the license file, or it may be placed next to the license file using the vendor name.

Look for a line that starts with: REPORTLOG

Example: REPORTLOG +/var/log/rlm/vendor-report.log std

How to generate or enable it

Add a REPORTLOG line to the ISV options file. Use + before the file path if you want the server to append new records instead of overwriting the file.

Examples: REPORTLOG +/var/log/rlm/vendor-report.log std REPORTLOG +/var/log/rlm/vendor-report-detailed.log detailed

The standard format is usually enough for regular reporting. The detailed format may include more precise checkout and checkin timing.

After changing the options file, reread or restart the RLM service according to your normal license administration process.

What to upload

Upload the RLM report log if available. It is designed for usage reporting and can include checkouts, checkins, denials, timestamps, and other license activity records.

Sentinel RMS Usage Log

For Sentinel RMS, the relevant file is usually the usage log created by the Sentinel RMS License Manager.

Where to find it

The usage log file name and location are normally controlled by the License Manager startup options or by vendor-specific configuration. Some Windows deployments use a file named lservsta, but this is not guaranteed for every product.

Check:

The Sentinel RMS License Manager service startup options
Vendor documentation for the protected application
Any license manager configuration files
The server folder used by the software vendor

How to generate or enable it

Enable usage logging according to the vendor's Sentinel RMS configuration instructions. If extended logging is available and appropriate for your environment, it may provide more useful user and host details.

Avoid changing the active license service without a maintenance window.

What to upload

Upload the Sentinel RMS usage log that records license requests, releases, denials, commuter activity, and license server startup or shutdown events.

Dassault Systèmes DSLS Logs

For Dassault Systèmes License Server, DSLS logs are generated by the DSLS server process and its service configuration.

Where to find it

First identify the DSLS server installation folder.

Common default command locations include:

Windows: C:\Program Files\Dassault Systemes\DS License Server\win_b64\code\bin

Linux: /usr/DassaultSystemes/DSLicenseServer/linux_a64/code/bin

The server may write logs to its default log folder, or to a custom folder specified when starting the service.

How to generate or control the log location

DSLS can be started with options that control logging.

Example: DSLicSrv -startServer -logDir C:\DSLSLogs -logFileSize 20 -compressLog

On Windows, DSLS often runs as a service. You can inspect the current service command using an elevated command prompt: sc.exe qc "DS License Server"

If you change DSLS service options, restart the service during a maintenance window.

What to upload

Upload the DSLS log file that contains the relevant license server activity for the period you want to analyze. If you are not sure which file is correct, start with the main server log from the configured DSLS log directory.

Altair ALM License Logs

Altair License Manager uses transactional license logs for usage reporting. These are different from the normal operational or debug log.

Where to find it

Check the Altair License Manager installation directory and the alus.conf configuration file. Transactional log settings are controlled from this configuration, and usage log files are usually written under the ALM data directory.

Common folders may include:

data/sent
data/detailed

How to generate or enable it

Check the ALUS_LOG_LEVEL value in alus.conf.

Typical logging levels:

0 -- no usage logging
1 -- anonymous usage logs
2 -- anonymous and detailed usage logs

If you need user, host, or detailed reporting, detailed logs are usually more useful than anonymous logs. Restart the license service during a maintenance window if the logging configuration is changed.

What to upload

Upload the transactional usage log, not only the operational server log. The operational or debug log is useful for troubleshooting, but the transactional usage log is usually the better source for usage analysis.

LM-X Debug Logs

For LM-X License Manager, the relevant file is usually the LM-X License Server log file. Depending on configuration, this log may include checkouts, checkins, denials, warnings, and other server activity.

Where to find it

The easiest way to find the log is through LM-X License Server Client. Open the Log File tab to view, search, and download the license server log.

The log path can also be configured in the LM-X license server configuration file. Some installations write a default log file under the license server directory.

Common configuration examples: LOG_FILE = C:\Program Files\lmx-server.log LOG_FILE = /home/user1/lmx-serv.log

How to generate or enable it

Use the LM-X License Server Client or the LM-X configuration file to enable logging and set the log file location. If available, extended logging may provide more detail.

After changing logging settings, restart the LM-X license server if required by the configuration tool.

What to upload

Upload the LM-X license server log file. If multiple logs exist, choose the log that covers the time range you want to analyze.

Which log should I use?

License Manager	Best file to upload	Main place to check
FlexLM / FlexNet Publisher	Debug log	LMTOOLS, service command, or `lmgrd -l`
RLM	Report log	ISV options file with `REPORTLOG`
Sentinel RMS	Usage log	License Manager startup options or vendor configuration
DSLS	DSLS server log	DSLS log directory or service start options
Altair ALM	Transactional usage log	`alus.conf` and ALM data directory
LM-X	License server log	LM-X License Server Client or configuration file

Before uploading the log

Before uploading a log file, check that it covers the period you want to analyze. For example, if you need monthly usage, make sure the log contains the full month and was not rotated too early.

Also check whether usernames, hostnames, project names, or feature names are sensitive in your organization. If needed, use a copied and anonymized version of the log.

FAQ

Do I need to stop the license server to copy a log file?

Usually, no. In many cases you can copy the current log file and analyze the copy. Do not move, rename, or delete an active log file unless your vendor documentation says it is safe.

Should I upload a debug log or a report log?

Use the file that contains actual license activity. For FlexLM, that is often the debug log. For RLM, the report log is usually better. For Altair ALM, use the transactional usage log. For Sentinel RMS, use the usage log.

Why are denials missing from my log?

Denials may be missing if the license manager was not configured to log them, the wrong file was selected, the relevant time period is missing, or a vendor options/configuration file suppresses those records.

Can I analyze an old rotated log?

Yes, if the rotated log is a plain text log format supported by the analyzer and contains the time period you want to review.

What should I do if I cannot find the right file?

Check the license server service configuration first. If you still cannot find the file, ask the software vendor, your license administrator, or contact NYBS Consulting for help identifying the correct log source.

Ready to analyze your license log?

Upload the right file and generate clear reports.

Once you have the right file, upload it to License Log Analysis to generate clear reports for usage, denials, active users, sessions, heatmaps, and utilization.

Analyze a Log File View Supported License Managers