HP Insight Control for Linux 7.1 Installation Guide

post installation phase.
Contact HP Software Technical Support for assistance.
Corrective Action: Rerun the install.sh script, and make sure you enter the correct user name
(which must be root) and the root password when prompted.
9.1.5 Installation hangs if *_proxy environment variables are defined
The installation process will hang at "Starting Systems Insight Manager" when the wget command
determines when Systems Insight Manager has finished loading. The hang occurs if a *_proxy
environmental variable is defined (for example, http_proxy) because wget tries to use the
defined proxy to access the local host.
Corrective action: Unset the proxy environment variables before running the install.sh script.
You can define proxy settings in either the /etc/wgetrc file or via an environment variable, so
ensure that no proxy variables are set in either location.
9.1.6 Cannot install older OS after an upgrade
Corrective Action: Use a text editor to manually add older operating systems to the /opt/mx/
icle/SupportMatrix.xml file as described in Section 8.4 (page 56).
9.1.7 Dependency error on SLES11 CMS if you do not install the RPM required by
HP virtualization
The following message is generated by the install.sh script if the required dependency for the
HP virtualization software is not installed on the SLES 11 CMS before you began the Insight Control
for Linux installation:
Apr 3: 06_vmm_dependency.sh - An RPM dependency is missing:
compat-32bit compat-libstdc++-296-2.96 libstdc++33
Corrective Action: Before you can continue with the installation, you must install the libstdc++33
RPM, which is contained in the vendor distribution. This RPM provides the capabilities required by
hpvmm.
9.1.8 What to do if you see install.sh authentication errors
This section describes what to do if you see the following message generated by the install.sh
script:
Logging in
Proxy = https://172.17.91.6:50001/mxsoap/services/MxpiMain5_2
java.lang.Exception: Authentication failed.
ERROR: create_MxpiMainService returned 2304
Error: /opt/hptc/cms/bin/setup_cms returned: 1
Error: post install failure
Install error: 10_mgmt_postinstall.sh exited with error code 132
If you did not revise the /etc/hosts file to add the CMS IP address and host name as described
in Section 3.4.2.3 (page 22), the postinstallation scripts do not create the trusted certificate because
they are not able to log in to Systems Insight Manager.
Corrective Action:
1. Edit the /etc/hosts file according to the instructions in Section 3.4.2.3 (page 22).
2. Stop Systems Insight Manager:
# /opt/mx/bin/mxstop
3. Start Systems Insight Manager:
# /opt/mx/bin/mxstart
4. Use the instructions in Section 5.4 (page 42) to restart the Insight Control for Linux installation
process.
58 Troubleshooting