by Albook
While upgrading my JazzSM 1.1 environment, using silent installation method, I experienced some issues that initially prevented the successful completion of the process.
Doing a quick search I realized that very similar scenarios have been also faced by other people, for this reason, once I resolved the problem, I wanted to share this experience so that you can take advantage of it in case you are currently struggling with the same issue (but it can be a good reading in case you are planning to upgrade your JazzSM 1.1 in the short term).
Despite from a user perspective the external symptoms are the same, the root cause may indeed vary.
This is a very common call stack you can find in the Fixpack Installation log file after having executed the FixPack installation using a response file:
---
org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:508)
org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:418)
org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
---
What really does matter is anyway the set of messages you see before the above call stack.
Most of the time it is enough to understand where the installation failed.
In my case, for example, I've got the following messages:
---
/opt/IBM/JazzSM/install/fsconfig.xml:183: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/fsconfig.xml:187: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/fsconfig.xml:179: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/was/stop_was.xml:17: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/was/was.xml:161: exec returned: 255
---
Looking the xml files at the row specified in the message you can understand a bit more about what the installer was doing in that moment.
Even from the file name you can anyway gather useful information about the involved feature and the action executed at error time.
In the above example, the error occurred while trying to stop the WAS.
If a similar pattern is repeated for different components/features, than you can be quite sure the problem is really related to WAS management (stop/start).
In my case I've actually found the same pattern as follow:
---
/opt/IBM/JazzSM/install/fsconfig.xml:269: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/fas_ui/fas_ui_config.xml:31: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/fas_ui/fas_ui_config.xml:53: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/fas_ui/fas_ui_config.xml:58: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/fas_ui/fas_ui_tip_config.xml:371: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/was/stop_was.xml:17: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/was/was.xml:161: exec returned: 255
..
..
/opt/IBM/JazzSM/install/tip/tipWrapperInstall.xml:200: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/tip/tipWrapperInstall.xml:220: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/tip/tipWrapperInstall.xml:224: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/fsconfig.xml:179: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/was/stop_was.xml:17: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/was/was.xml:161: exec returned: 255
---
From this example, independently by the involved component, it is quite clear that the failing action deals with stop_was.xml file.
When reaching this point, the installer tries to stop the WAS and in this case it does fail.
In order to know the root cause you should check the related WAS profile logs (SystemOut.log and stopServer.log) but 90% of the time this
kind of error can be associated to the following 2 root causes:
1) wrong WAS user password in the response file.
Action required: Double check you are using the correct password and in case encrypt it again and modify the response file accordingly
2) JazzSM/WAS shutdown timed out. This is a known issue usually observed after upgrading WAS from 8.5.0.1 to 8.5.5.4.
Action required: verify if the JazzSM server really takes long time to shut down by doing it manually.
If you confirm there is an issue with WAS shutdown, you can fix the problem by following the steps suggested in this link:
http://www-01.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/tshoot/psc_ts_jazzsm_start_stop.html
In my case, I verified the password was OK, so moved to option 2.
JazzSM was really taking long (long!) time to stop, so I've followed the steps suggested in the link and
was then able to complete FixPack 3 installation.
If the error messages showed in the Fixpack installation log instead look like:
---
/opt/IBM/JazzSM/install/tip/tipWrapperInstall.xml:206: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/tip/tipWrapperInstall.xml:245: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/tip/tipWrapperInstall.xml:256: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/tip/dashFixpack.xml:800: The following error occurred while executing this line:
/opt/IBM/JazzSM/install/tip/dashFixpack.xml:1190: CTGWA0129E Fail to deploy a war module to isc.ear.
---
Most of the time this is caused by a shortage of space in the filesystems where JazzSM and WAS are installed.
Double check you have enough room, extend the filesystem if possible (or cleanup the filesystem from unwanted/old files) and try the installation again.
If, despite you have enough space in the file system, you continue to receive above error message, then it can be a good idea to contact
IBM Customer Support after having collected the following set of diagnostic doc:
A) IM Log files: follow the instructions from this link to export the IM data
http://www-01.ibm.com/support/knowledgecenter/SSDV2W_1.6.0/com.ibm.silentinstall12.doc/topics/t_silent_dataexport.html
B) Collect the WAS log files. For example:/opt/IBM/WebSphere/AppServer/logs
C) Collect the WAS profile log files: JazzSM_WAS_Profile/logs