- Flexera Community
- Flexera One
- Flexera One Forum
- Re: Help needed to fix linux agent
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
Help needed to fix linux agent
I'm using the following command to resolve linux agent
following commands on server
/opt/managesoft/bin/mgsconfig -i /opt/managesoft/install/default.ini /opt/managesoft/bin/mgspolicy -t Machine -o DownloadRootURL=http://VMWWxxxxx.mars-ad.net/ManageSoftDL
Getting below error, after executing the steps . [root@vmwlxxxx ~]# /opt/managesoft/bin/mgsconfig -i /opt/managesoft/install/default.ini sed: can't read /etc/managesoft.ini: No such file or directory
ERROR: ManageSoft has not been configured. Please make sure you have a /etc/managesoft.ini file with the correct InstallDir set.
Execution aborted. [root@vmwlxxxxx ~]# /opt/managesoft/bin/mgspolicy -t Machine -o DownloadRootURL=http://VMWWxxxxxx.mars-ad.net/ManageSoftDL sed: can't read /etc/managesoft.ini: No such file or directory ERROR: ManageSoft has not been configured. Please make sure you have a /etc/managesoft.ini file with the correct InstallDir set.
RPM for managesoft is installed [root@vmwlxxxxx ~]# rpm -qa | grep -i managesoft
The output there suggests that the /etc/managesoft.ini file does not exist on the computer. This file contains key details about the installation of the agent itself that the agent needs to operate.
I think I'd probably be looking at doing an uninstall and re-install of the agent RPM package to try to recover from this.
Check with root privileges that you have the file /var/opt/managesoft/etc/config.ini
In case you do not have that file you probably need to reinstall the agent otherwise try out the attached post installation script that you can modify for your needs, like server FQDN, certification security parameters etc.
Only those 2 lines which has server.domain.cc
I'm only used with the on-premise FNMS, I'm not sure how the security is configured if you are using the FNMS cloud service, if you for example need to add tenant or a special certificate.
Thanks, yes we are FNMS cloud, not on-prem, we have two beacons configured
So will server.domain.cc, be replaced by a beacon server name?
And you might need to adjust port (80, 443,..) or protocol (http/https) depending on your setup. If you look in the registry on a windows client/server you will recognize these settings.