Problem
When you are trying to install (push/manual) an agent to SUSE Enterprise Linux server without success, and you have already installed all the pre-requirements, your server pings well, you can log in via SSH and the name resolution is ok as well you should definitely check this article. Especially when you receive the following error message: "Core connection test failed".
Error message
Wed Oct 24 15:39:41 CEST 2018
/tmp/.ldcfg-3880-114916/install.sh: line 292: NOOEM=1: command not found
Wed Oct 24 15:39:45 CEST 2018: ERROR: Core connection test failed: KRLANDESK.name.ex -- aborting
Failed to properly install the client.
CBA 8 X509 operation : -2147481845 (8000070b8u) : Unable to contact the remote agent.
NT File Sharing: 1222 (4c68u): The network is not present or not started.
NT File Sharing: 53 (358u): The network path was not found.
Error: [last attempted operation] RemoteExecute, /bin/sh "/tmp/.ldcfg-3880-114916/install.sh" \"NOOEM=1\"
Possible last exit_code: -1917517823
Cause
At present, our installer "forcibly" checks the Core in order to see if it needs to download anything else. In the future versions, probably we will get an option for NIXCONFIG added later (something like an "--offline_install" or so) as an explicit option to ignore this.
Solution
Please open the NIXCONFIG in your editor of choice and disable this Core existence check. In order to do it please search for the following lines of content in the NIXCONFIG.SH file:
# Verify connection to Core can be established.
test_connection "${CORE_ADDR}"
[ $? -ne 0 ] && abort "Core connection test failed: ${CORE_ADDR}" 1
log $INFO "Core connection test successful: ${CORE_ADDR}"
Essentially, just search for the string "Verify connection to Core can be established" and you will get to the right place. Then please just comment those 3 below's lines out with #. The result should be the following:
# Verify connection to Core can be established.
#test_connection "${CORE_ADDR}"
#[ $? -ne 0 ] && abort "Core connection test failed: ${CORE_ADDR}" 1
#log $INFO "Core connection test successful: ${CORE_ADDR}"
Other troubleshooting steps
General troubleshooting
Please check all the following steps: How to troubleshoot the Agent for Linux deployment.
Services
Please verify if the service "LANDesk Inventory Server" on your Ivanti Core Server is running or is the Inventory service stopped. Service "LANDesk Inventory Server" should / must be running on the Core Server.
Ping
Please ping the IP address of the affected client machine from the Ivanti Core Server with a switch '-a' and check if the Windows Server can resolve the device name for it's IP address. Please try to ping the FQDN but also try to ping the IP address of your core server from this client device.
UDD
Please delete the device name '10.228.28.227' (where the 10.228.28.227 should be replaced by your client machine IP address) from Pending unmanaged client deployment, perform a scan of the IP range 10.228.28.227 through 10.228.28.227 from within the Unmanaged Device Discovery, and then install/attempt to install/reinstall the Agent for Linux again.
Ports
Please also check if the TCP port 80 is open for traffic between this Linux client and the core server as the installation script is using WGET command to test the communication to the core. WGET is using HTTP on port 80. Please also try to use wget to access a file on the core (for example from \\your-core-server\ldlogon folder). Are you using default HTTP/HTTPS ports in your network and are they open for the traffic to and from LDMS core server?
SSH
If you haven't already, please make sure that ssh and connection to and from the core server work correctly.
DNS
Please manually add an A record on the Microsoft Windows DNS server for the Linux machine 'landsktest64f05' with an IP address 10.228.28.227 (where the 10.228.28.227 should be replaced by your client machine IP address and landsktest64f05 by your client machine hostname ), verify that the Core Server can then ping that Linux machine by its name, and then please attempt to install/reinstall the Ivanti Agent for Linux again.
IIS
Please check all your IIS configuration with the article below starting from verification if all your application pools are well started: IIS Troubleshooting and LANDESK Management Suite: 101
Manual install
If all the steps above will not help you, please use instructions below to manually install the Agent for Linux from the Linux machine itself. You just need to change the names of the Core Server, the name of the certificate file, and the name of the Agent for Linux configuration to match your environment as the example below is based on our test environment. The following commands will uninstall the Agent for Linux and then install/reinstall the Agent for Linux. When you add the switch '-k' you can specify the name of the certificate hash file and that certificate hash file will be retrieved from the LDMS / EPM core server during the installation of the Agent for Linux.
In the example below:
- The core server name is it13 in domain tse.net.
- The name of the Agent for Linux configuration is 'agent_linux_x64' and the corresponding *.ini file is called 'agent_linux_x64.ini'
- The certificate hash file is called 29264735.0
Please substitute those values accordingly as per your LDMS / EPM environment.
On the target Linux host please execute the following set of commands in the right order:
su -
mkdir /install
cd /install
wget http://it13.tse.net/ldlogon/unix/nixconfig.sh
wget http://it13.tse.net/ldlogon/agent_linux_x64.ini
wget http://it13.tse.net/ldlogon/29264735.0
chmod +x nixconfig.sh
./nixconfig.sh -r all -R
./nixconfig.sh -a it13.tse.net -c agent_linux_x64.ini -i all -p -k 29264735.0 -l /install/agent_install.log
When running nixconfig.sh you can also include the "-d" parameter. This will add debug lines to the install log and should point to where the problem is if the above steps don't help.
In the subject of manual installation please check also the 2 articles below:
Non-root user install
For a non-root user Linux agent install please check the following article: How To: Push an Agent version 2017.3 for Linux using a non-root user with some Agent for Linux install troubleshooting notes (only for the Agent version 2017.3 and newer)