Some users may experience issues accessing the case portal. For more information, please click here.

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

Help needed to fix linux agent

Hello

 

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.

Execution aborted.

RPM for managesoft is installed [root@vmwlxxxxx ~]# rpm -qa | grep -i managesoft

managesoft-16.0.1-1.x86_64

Any ideas??

0 Kudos
6 Replies
ChrisG
Community Manager Community Manager
Community Manager

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.

(Did my reply solve the question? Click "ACCEPT AS SOLUTION" to help others find answers faster. Liked something? Click "KUDO". Anything expressed here is my own view and not necessarily that of my employer, Flexera.)
mag00_75
Level 8 Champion
Level 8 Champion

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.

0 Kudos

Hi

Please can you confirm which line(s) need to be edited

 

 

0 Kudos
mag00_75
Level 8 Champion
Level 8 Champion

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.

0 Kudos

Hi,

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?

 

 

0 Kudos

yes, correct.

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.