Showing results for 
Show  only  | Search instead for 
Did you mean: 


The usage agent on Linux may generate a large volume of logging messages on computers meeting the following conditions:

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

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


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

[Tue 13 Apr 2021 03:31:21 AM CDT (G, 0)] {4073} Got PerformDockerInventoryScan=False, is running: 5280177...
[Tue 13 Apr 2021 03:32:21 AM CDT (G, 0)] {4073} In runloop checking for docker monitor...
[Tue 13 Apr 2021 03:32:21 AM CDT (G, 0)] {4073} Usage agent checking for enable/disable docker monitor...
[Tue 13 Apr 2021 03:32:21 AM CDT (G, 0)] {4073} Got PerformDockerInventoryScan=False, is running: 5280177...

Repeated messages like the following can also appear in the /var/log/messages file:

2020-11-17T12:18:34.726174+01:00 he109987 systemd[1]: Starting LSB: ManageSoft fnms-docker-monitor agent...
2020-11-17T12:18:34.741543+01:00 he109987 fnms-docker-monitor[8749]: Starting fnms-docker-monitor: fnms-docker-monitor    INFO 2020-11-17T12:18:34+01:00 -- logfile: /var/opt/managesoft/log/fnms-docker-monitor.log
2020-11-17T12:18:34.741725+01:00 he109987 fnms-docker-monitor[8749]: fnms-docker-monitor    INFO 2020-11-17T12:18:34+01:00 -- pidfile: /var/run/
2020-11-17T12:18:34.753627+01:00 he109987 fnms-docker-monitor[8749]: ..failed
2020-11-17T12:18:34.753974+01:00 he109987 systemd[1]: fnms-docker-monitor.service: Control process exited, code=exited status=7
2020-11-17T12:18:34.754306+01:00 he109987 systemd[1]: Failed to start LSB: ManageSoft fnms-docker-monitor agent.
2020-11-17T12:18:34.754450+01:00 he109987 systemd[1]: fnms-docker-monitor.service: Unit entered failed state.
2020-11-17T12:18:34.754566+01:00 he109987 systemd[1]: fnms-docker-monitor.service: Failed with result 'exit-code'.

Related information

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

Fix status

This issue has been fixed in the following FlexNet Manager Suite releases: 2022 R1 (On Premises), 2022 R1 / Apr 2022 (Cloud)

Other information

Affected components: Agent, Containers, Usage

Master issue ID: IOJ-2249304

Also known as: FNML-75294

Was this article helpful? Yes No
100% helpful (1/1)
Level 6

When will this be addressed?

By Level 6 Flexeran
Level 6 Flexeran

Hi @GopalRaghvani thanks for bringing this to our attention. We will have a closer look at it and plan to address it on our roadmap.

By Community Manager Community Manager
Community Manager

@GopalRaghvani - in case you didn't receive a separate notification, note that the "Fix status" of this issue has been updated to show information about when this is planned to be addressed.

Version history
Last update:
‎Sep 07, 2022 02:29 PM
Updated by:
Knowledge base article header content