Embedded Messaging installation fails on Solaris because "checkinstall script did not complete successfully"
 Technote (troubleshooting)
 
Problem(Abstract)
This document describes specific problems which can occur while installing the Embedded Messaging component for IBM® WebSphere® Application Server versions 5.0 and 5.1 on Solaris™ platforms. The mq_install.log file shows an error which says "checkinstall script did not complete successfully".
 
Cause

Symptoms
The WebSphere Application Server versions 5.0 or 5.1 installer throws an error during installation. If the installation takes place in the install wizard, the wizard may produce a panel which shows the content of a log file which contains the error. The error is related to the installation of the Embedded Messaging component.

The error occurs when installing the Embedded Messaging server, client, or both. The error is logged in the mq_install.log file, which is placed into the appserver_install_root/logs directory. The error text is similar to the excerpt below. This text excerpt appears approximately 50 lines into the mq_install.log file and the error text of interest is in boldface type:


wmsetup: [timestamp] installing component mqm ...
Licensed Materials - Property of IBM
                 
 5724-B41
  (C) Copyright IBM Corporation 1994, 2002
 
All rights reserved.
US Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
/my_install_directory/sun/messaging/mqm/install/checkinstall: /my_install_directory/sun/messaging/mqm/install/checkinstall: cannot open
pkgadd: ERROR: checkinstall script did not complete successfully

Installation of <mqm> failed.
No changes were made to the system.
wmsetup: [timestamp] Set capacity units
/my_install_directory/sun/messaging/wmsetup: /opt/mqm/bin/setmqcap: not found
wmsetup: [timestamp] ... Return code 1 from pkgadd
wmsetup: [timestamp] ERROR: installation of mqm failed - rolling back


Specifically, the error text of interest is:

checkinstall: cannot open
pkgadd: ERROR: checkinstall script did not complete successfully

Note concerning other operating systems
Similar symptoms can occur on other UNIX® or Linux®-based platforms which support WebSphere Application Server versions 5.0 or 5.1. The log messages will vary from platform to platform, since each platform uses different utilities and methods of installing native packages. Despite these differences, the recommendations below may still be effective.
 
Resolving the problem

Check the directory ownership of the installation image
The most likely cause for this problem is related to file and directory ownership. The root user must own all files and directories in the product installation image. In addition, the root user must own and have read access to each directory in the path hierarchy which leads to the checkinstall file. If a non-root user owns one of the directories in the path, then the installation process will fail with the messages excerpted in the section above.

For example, if the installation image is copied to a local filesystem, in a directory named "/mnt/images/websphere5", then the full directory path for checkinstall is:

/mnt/images/websphere5/sun/messaging/mqm/install/checkinstall

The "mnt", "images", and "websphere5" directories are created by the system administrator. The "sun", "messaging", and other directories below those are part of the installation image.

In this example, the directories "mnt", "images", "websphere5", "sun", "messaging", "mqm", and "install" must ALL be owned by the root user and a standard administrative group (such as the group named "other"). The "checkinstall" file itself should also be owned by the root user. If any one of the directories in the path are owned by a non-root user, the install will fail.

Other factors to consider
If the installation image is read by a Windows®-based or OS X-based system, then transmitted to the local UNIX system, the image data is corrupted. (The capitalization of the file names become invalid, file permissions are stripped, and file ownership may change.) If the installation image was provided in the form of an archive file, such as a TAR or gz file, then extract the image directly onto the local system. Do not FTP individual files from another system to this one; otherwise, the install image is hosed.

The installation must take place as the actual root user. This requirement also excludes the "sudo" command. Do not use "sudo root" to install the product on Solaris (or other UNIX or Linux-based) platforms. Install the product while logged in as the actual root user. Unfortunately, the Embedded Messaging prerequisite detector does not detect the appropriate information concerning active group membership when invoked under "sudo", and this usually results in an incomplete product installation. (The Embedded Messaging components will be entirely missing under such circumstances.)
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Install
Operating system(s): Solaris
Software version: 5.1
Software edition:
Reference #: 1242556
IBM Group: Software Group
Modified date: May 30, 2008