IBM Tivoli Monitoring, Version 6.3

UNIX and Linux install.sh command fails with error code: 99 and error code: 4

If you get a runGSkit failure while running the install.sh command, install the libstdc++.so.5 library.

Installation on UNIX and Linux systems uses install.sh command; running this command fails with a "runGSkit failure: Return error code: 99" and a "install.sh failure: Return error code: 4". Because it failed within runGSkit when it called verifyInstall, review the InstallDirectory/logs/candle_installation.log file and look for references to runGSkit. For example, output similar to the following might be present:

runGSkit: ----- Running command: /opt/IBM/ITM/ls3263/gs/bin/private_verifyinstall
/opt/IBM/ITM/ls3263/gs/bin/gsk7ver: error while loading shared libraries: 
libstdc++.so.5: 
cannot open shared object file: No such file or directory
Error: Verify Failed
Expected Details of gskit in /opt/IBM/ITM/ls3263/gs
Got 
runGSkit: return code from command is 99
runGSkit: ----- End of running command -----
runGSkit: error Return error code: 99
runGSkit: error GSKit check failure, script: /opt/IBM/ITM/ls3263/gs/bin/private_
verifyinstall
runGSkit: error ls3263 - GSK check error, verifyInstall test failed

In the example above, the libstdc++.so.5 file is not present. This comes from the package compat-libstdc++-33-3.2.3-61.s390.rpm. When this package is installed, the problem no longer occurs.

Feedback