Summary

The usage agent on Windows may generate large numbers of logging messages on computers meeting the following conditions:

• The usage agent is enabled
• The FlexNet inventory agent Docker service is not running (for example, because Docker is not installed)

This can result in log files growing over time to be very large.

Details

The following details may appear approximately every 40-90 seconds in the usage agent log (usageagent.log) due to this issue.

[2021-01-29 15:26:35 (G, 0)] {3160} In AppMeterC::Step checking for docker monitor...
[2021-01-29 15:26:35 (G, 0)] {3160} Usage agent checking for enable/disable docker monitor...
[2021-01-29 15:26:35 (G, 0)] {3160} Got PerformDockerInventoryScan=True, is running: no...
[2021-01-29 15:26:35 (G, 0)] {3160} Starting docker monitor service...
[2021-01-29 15:26:35 (G, 0)] {3160} DockerMonitorDaemonHelper: 0 

This issue affects FlexNet inventory agent versions 2019 R2.3 (14.3) through 2020 R2 (16.0).

Fix details

The agent has been changed to avoid generating frequent log messages related to the Docker monitor.

Related information

See the following articles for other issues related to usage agent logging:

• Usage agent on Linux generates excessive logging related to the Docker monitor daemon (IOJ-2249304)
• Usage agent on Unix-like operating systems generates excessive logging related to the "Usage coordinator" (IOJ-2250660)
• usageagent.log does not rotate until usage agent is restarted, potentially leading to a log files growing very large over time (IOJ-2243344)

Fix status

This issue has been fixed in the following FlexNet Manager Suite releases: 2020 R2.1 / Feb 2021 (Cloud), 2021 R1 (On Premises)

Other information

Affected components: Agent, Containers, Usage

Master issue ID: IOJ-2181680

Also known as: FNML-73076