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

Known Issue: Agent config.ini file may become corrupted on Unix-like operating systems and cause agent operations to go haywire (IOK-930635)

Known Issue: Agent config.ini file may become corrupted on Unix-like operating systems and cause agent operations to go haywire (IOK-930635)


FlexNet Inventory Agent preferences in the /var/opt/managesoft/etc/config.ini file on Unix-like operating systems can intermittently and randomly end up with blank or missing values, causing the agent to stop operating correctly.


Common symptoms of the issue occurring on a device are:

  1. Logging from various agent processes starts to appear in a file named /var/opt/managesoft/log/managesoft.log
  2. Logging appearing in one or more files under the /var/opt/managesoft/log/ directory includes a message like the following:
    ***   FlexNet Manager Platform cannot access the directories describing your FlexNet Manager Platform applications.
    Please review your application directory settings.
    See log file for more details.

Other varied symptoms may also be evident, and generally involve one or more agent processes not operating as expected. For example, this might include:

  1. Inventory data that is gathered in NDI files is incomplete, such as missing expected file inventory details.
  2. Uploads or downloads are performed using incorrect beacon details, or are not performed at all due to beacon details not being configured.
  3. The last line in log file(s) may appear to be incomplete, or contain multiple logging messages appearing on a single line.
  4. The /var/opt/managesoft/etc/config.ini file has substantially different content compared to the same file from another computer that does not have problems.


This issue can generally be remediated on a device by re-initializing the agent configuration.

One approach to do this is to:

  1. Uninstall the agent
  2. Execute the following command to remove all cached agent configuration details: rm -rf /var/opt/managesoft
  3. Reinstall the agent.

Alternatively, the following steps can be used to re-initialize the agent configuration without performing a re-installation:

  1. Execute the following to apply default configuration settings: /opt/managesoft/bin/mgsconfig -i /opt/managesoft/install/default.ini
  2. Execute the following to bootstrap the agent policy from an identified beacon URL: /opt/managesoft/bin/mgspolicy -t Machine -o DownloadRootURL=http://your-beacon/ManageSoftDL

Note that this 2nd approach will not apply any custom configuration settings which may be used in your environment, such as configuration applied by your agent installation process.

All commands above should be executed with root rights.

Fix status

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

Other information

Affected components: Agent

Master issue ID: IOK-930635

Also known as: FNMS-76364

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
Version history
Last update:
‎Sep 15, 2022 02:31 PM
Updated by: