Summary

The usage agent on Unix-like operating systems may generate a large volume of logging messages referring to the "Usage coordinator".

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

Details

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

[Mon Feb 21 12:37:01 2022 (G, 0)] {28064} Usage coordinator in run...
[Mon Feb 21 12:37:01 2022 (G, 0)] {28064} Usage coordinator run main loop top...
[Mon Feb 21 12:37:01 2022 (G, 0)] {28064} Usage coordinator running callback...
[Mon Feb 21 12:37:01 2022 (G, 0)] {28064} Usage coordinator callback done...
[Mon Feb 21 12:37:01 2022 (G, 0)] {28064} Usage coordinator check package db process...
[Mon Feb 21 12:37:01 2022 (G, 0)] {28064} Usage coordinator done checking database proc, checking upload...
[Mon Feb 21 12:37:01 2022 (G, 0)] {28064} Usage agent is configured not to run on this machine

This issue affects FlexNet inventory agent versions 17.2 to 17.4.

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 Windows generates excessive logging related to the Docker monitor service (IOJ-2181680)
• 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 release: 2022 R1 / Apr 2022 (Cloud)

Other information

Affected components: Agent, Usage

Master issue ID: IOJ-2250660

Also known as: FNML-75366