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

Known Issue: Usage files may not be generated and uploaded from computers which are not turned on for at least 24 hours (IOJ-1902994)

Known Issue: Usage files may not be generated and uploaded from computers which are not turned on for at least 24 hours (IOJ-1902994)

Summary

The usage agent does not reliably generate and upload files containing usage metering data unless the computer is turned on (and the agent runs for) longer than the agent’s UsagePeriod preference setting value. The default value for this preference is 24 hours.

Usage data will rarely (or never) be saved and uploaded from computers which are rarely (or never) turned on for longer than this period.

Symptoms

The primary symptom of this issue that may be observed is that expected usage data does not appear from computers, especially when viewing raw data on the Raw Software Usage web UI page.

Information about when (if) usage data files are generated on a computer can be found by inspecting the usageagent.log file. Logging similar to the following is output whenever a usage file is generated:

[11/20/2021 5:46:27 PM (G, 0)] {2772} Finished reading the session cache, sessions summarized to file C:\ProgramData\ManageSoft Corp\ManageSoft\Usage Agent\UsageData\computername at 20211120T174627.mmi

If a usage data file is not generated at any point over the course of a week, that data may be discarded and not included in any usage data file that is subsequently generated.

Mitigation

The impact of this issue can be minimized by reducing the value of the UploadPeriod agent preference to a value that is less than the typical duration for which computers are turned on. For example, setting UploadPeriod to “21600” (seconds, in other words, 6 hours) will ensure usage data is generated and uploaded from computers as long as they are turned on for at least 6 hours.

IMPORTANT: Decreasing the UploadPeriod preference can result in a larger number of usage data files being generated and uploaded than would otherwise be the case. This may place additional load on beacons, inventory and database servers as they process this data.

A typical rule of thumb applied when planning how many beacons to deploy is to allow for 10,000 computers per top level beacon in the beacon hierarchy. However if the UploadPeriod preference is configured so that computers will to generate more than one usage data file per day, the number of beacons may need to be increased accordingly. For example: if computers generate an average of 2 usage files per day, a top level beacon may only be able to upload files from 5,000 computers in a day.

Additional information

The UploadPeriod agent preference is typically configured in the following entry under HKLM\SOFTWARE\WOW6432Node\ManageSoft Corp in the Windows registry, or the agent’s config.ini file on Unix-like operating systems: ManageSoft\Usage Agent\CurrentVersion\UploadPeriod

See documentation for the UploadPeriod agent preference: Gathering FlexNet Inventory > The FlexNet Inventory Agent > UploadPeriod

Fix status

This issue is still open but not currently scheduled to be addressed.

Other information

Affected components: Agent, Usage

Master issue ID: IOJ-1902994

Also known as: FNMS-63984

Labels (1)
Was this article helpful? Yes No

Tip: If you have been impacted by this issue, please click the KUDOS button above. This helps to track the relative significance and importance of issues. Clicking on an option against "Was this article helpful?" also helps assess and improve the usefulness of content.

No ratings
Comments

Hi,

Would it be possible to update the UploadPeriod from the application like this?

2022-08-09_09h37_20.png

I guess updating agents manually won't be an option for most customers.

BR,

Markward

Edit: corrected the screenshot; As mentioned by Chris, beacon target needs to be set accordingly for Windows, Linux, MacOS or custom targets 

@mfranz - yes, the setting can be configured through agent policy in this way. Some points to note:

  • The KeyName should be "CUsageAgentUploadPeriod" (not the value shown the screenshot above).
  • The BeaconTargetID value of "4" shown in the screenshot will be different for different targets.
  • Remember to "EXEC BeaconPolicyUpdateRevision" after "EXEC BeaconTargetPropertyValueAdd" in order to update the beacon policy revision number so that beacons will pick up the change.

See the SQL script embedded in the following post which gives a more complete example of how to update policy settings using this approach: Finding installations of Apache Log4j (or other) files on computers with FlexNet Manager Suite.

Version history
Last update:
‎Aug 05, 2022 02:29 PM
Updated by: