HP Insight Control for Linux 6.0 Installation Guide

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 61).
9.1.7 06_vmm_dependency.sh dependency error if you do not install the supported
PSP
The following message is generated by the install.sh script if the PSP supported for this
release is not installed on the CMS before you began the Insight Control for Linux installation:
Apr 3: 06_vmm_dependency.sh - An RPM dependency is missing: compat-libstdc++-296-2.96
The PSP contains the compat-libstdc++-296 RPM, which provides the
compat-libstdc++-296-2.96 library required by hpvmm.
Corrective Action: Before you can continue with the installation, you must install the PSP to
satisfy this dependency, or if you are running Insight Control for Linux in a Xen VM guest you
must obtain the compat RPM from Novell.
If the CMS is installed on a virtual machine or the PSP cannot be installed, this dependency must
be met by the appropriate RPM package for the distribution. See Section 3.2 (page 15) on running
the CMS in a virtual machine.
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 24), 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 24).
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 45) to restart the Insight Control for Linux installation
process.
64 Troubleshooting