Troubleshoot Web server plug-ins installation and removal

Troubleshoot Web server plug-ins installation and removal

+
Search Tips | Advanced Search

This topic describes troubleshooting the installation and removal of the Web server plug-ins for WebSphere Application Server.

Before you begin

Use this procedure if you are having problems installing or uninstalling the Web server plug-ins for WebSphere Application Server. Otherwise:

If you are trying to install, see Installing Web server plug-ins.
If you are trying to uninstall the Web server plug-ins for WebSphere Application Server, see Uninstalling the Web server plug-ins for WebSphere Application Server.
If you are trying to uninstall the WebSphere Application Server, see Uninstalling the product.

Overview

This procedure is divided into three parts:

Troubleshooting plug-ins installation
Troubleshooting plug-ins removal
Miscellaneous messages, tips, and hints

Log files for Web server plug-ins for WebSphere Application Server
The following log files are in the plug-ins plugins_install_root/logs/install directory:

log.txt

Records all of the ISMP events that occur during the installation. The log also describes whether the installation was local or remote. Messages at the end of the file indicate whether manual configuration steps are required to complete the installation.

masterConfigurationLog.txt

Records all of the configuration events that occur during the installation.

installGSKit.log

Records events that occur during the installation of the GSKit code.

installWeb_serverPlugin.log

Records events that occur during the installation of a Web server plug-in. The name of the file varies to reflect the Web server:

installAPACHEPlugin.log
installIHSPlugin.log
installIISPlugin.log
installSUNONEPlugin.log
installDOMINOPlugin.log

configure_Web_server_webserver.log

Records events that occur during the configuration of a Web server plug-in. The name of the file varies to reflect the Web server:

configure_APACHE_webserver.log
configure_IHS_webserver.log
configure_IIS_webserver.log
configure_SUNONE_webserver.log
configure_DOMINO_webserver.log

Steps for this task (dependent on configuration)

Troubleshooting plug-ins installation

Does the installation image have the proper directories?
The following directories are required for a successful installation:

parent_directory/plugin
parent_directory/JDK"
parent_directory/GSKit

Remember: The parent_directory variable is the directory where one can unpack the images. All of the directories in the list must have the same parent directory.
If the directories are not present, or if the directories are empty, download a new installation image or discuss the product CD that you are using with someone who is knowledgeable about its creation. The IBM product discs are certified.
Reinstall using the IBM product disc.
Is there any sign that the installation occurred?
If not, look for the temporaryPluginInstallLog.txt file in the temporary directory of the user who installed the plug-ins.
For example, the /tmp/temporaryPluginInstallLog.txt file might exist if the root user installed the plug-ins on a Linux or UNIX system.
This log is of particular interest after a silent installation. Suppose that the silent installation responsefile.txt file has incorrect entries. The installation cannot succeed. The cause of the problem is recorded in the temporaryPluginInstallLog.txt file.
If the responsefile.txt does not pass validation, the failure is logged as an INSTCONFFAILED entry. The installation does not occur. Correct the failure and run the silent installation again.
See responsefile.txt for information about editing the file properly. You might have to start with a new copy of the file that is on the product disc if one cannot get your copy to work.
Does the installation result in a INSTCONFPARTIALSUCCESS status?

Look for errors in the log.txt file.
Look for an entry in the log.txt file that shows the location of the masterConfigurationLog.txt file.
Edit the masterConfigurationLog.txt file.
Starting at the end of the file, scan towards the front of the file looking for configuration scripts that could not run.
For example, the following stanza shows a configuration script that could not run
<record> <date>2004-10-08T10:31:43</date> <millis>1097245903200</millis> <sequence>189</sequence> <logger>com.ibm.ws.install.configmanager.ConfigManager</logger> <level>INFO</level> <class>com.ibm.ws.install.configmanager.ConfigManager</class> <method>dumpNonFatalFailedActionsInfoToLogFile</method> <thread>10</thread> <message>This action failed to execute: C:\Plugins\properties\version\install\plugin\6.0.0.0\config\full\install\99SGSKitInstall.ant</message> </record>

A configuration script that fails to run is likely the cause of a partially successful installation status. To debug the example, look at the installGSKit.log, which is the log file for GSKit. Look for signs of a failed installation to determine if one can correct the problem.

Configuration script log files and recovery procedures: The following configuration scripts run during the configuration of supported Web servers.
Configuration script: 98SConfigureWebserverDefinition.ant

Log file to investigate for error Recovery

configureWeb_server_type_webserver.log
For example, the file might be named:

configure_IHS_webserver.log

Logs the Web server definition creation.

If the Web server definition partially exists, delete the Web server definition.
Run the Web server definition script manually. The Web server definition is referenced in the script. The script is in the plug-ins_install_root/bin directory, with a name similar to the following convention:

configureWeb_server_definition_name.sh
configureWeb_server_definition_name.bat

Configuration script: 99SBootStrapPluginsSunOne.ant

Log file to investigate for error Recovery
installSunOnePlugin.log
Investigate the log file to determine what failed:

If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.
If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.
If the Web server configuration files do not update, investigate the files to verify that they exist and that the file permissions are correct.

We can manually configure the Web server by following the procedure documented in Configuring the Sun Java System Web Server.
We can rerun the Plug-ins installation wizard. Select the existing plug-ins installation root directory. Doing so results in the Web server being configured to use the existing binaries.

Configuration script: 99SBootStrapPluginsDomino6.ant

Log file to investigate for error Recovery
installDomino6Plugin.log
Investigate the log file to determine what failed:

If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.
If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.
If the Web server configuration files do not update, investigate the files to verify that they exist and that the file permissions are correct.

We can manually configure the Web server by following the procedure documented in Configuring Lotus Domino.
We can rerun the Plug-ins installation wizard. Select the existing plug-ins installation root directory. Doing so results in the Web server being configured to use the existing binaries.

Configuration script: 99SBootStrapPluginsDomino5.ant

Log file to investigate for error Recovery
installDomino5Plugin.log
Investigate the log file to determine what failed:

If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.
If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.
If the Web server configuration files do not update, investigate the files to verify that they exist and that the file permissions are correct.

We can manually configure the Web server by following the procedure documented in Configuring Lotus Domino.
We can rerun the Plug-ins installation wizard. Select the existing plug-ins installation root directory. Doing so results in the Web server being configured to use the existing binaries.

Configuration script: 99SBootStrapPluginsIIS6.ant

Log file to investigate for error Recovery
installIIS6Plugin.log
Investigate the log file to determine what failed:

If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.
If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.
Start the Internet Information Services (IIS) application and investigate the IIS configuration.

We can manually configure the Web server by following the procedure documented in Configuring Microsoft Internet Information Services (IIS).
We can rerun the Plug-ins installation wizard. Select the existing plug-ins installation root directory. Doing so results in the Web server being configured to use the existing binaries.

Configuration script: 99SBootStrapPluginsIIS5.ant

Log file to investigate for error Recovery
installIIS5Plugin.log
Investigate the log file to determine what failed:

If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.
If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.
Start the IIS application and investigate the IIS configuration.

We can manually configure the Web server by following the procedure that is documented in Configuring Microsoft Internet Information Services (IIS).
We can rerun the Plug-ins installation wizard. Select the existing plug-ins installation root directory. Doing so results in the Web server being configured to use the existing binaries.

Configuration script: 99SBootStrapPluginsApache.ant

Log file to investigate for error Recovery
installApachePlugin.log
Investigate the log file to determine what failed:

If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.
If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.
If the Web server configuration files do not update, investigate the files to verify that they exist and that the file permissions are correct.

We can manually configure the Web server by following the procedure documented in Configuring Apache HTTP Server V2.0.
We can rerun the Plug-ins installation wizard. Select the existing plug-ins installation root directory. Doing so results in the Web server being configured to use the existing binaries.

Configuration script: 99SBootStrapPluginsIHS.ant

Log file to investigate for error Recovery
installIHSPlugin.log
Investigate the log file to determine what failed:

If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.
If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.
If the Web server configuration files do not update, investigate the files to verify that they exist and that the file permissions are correct.

We can manually configure the Web server by following the procedure documented in Configuring IBM HTTP Server v6.
We can rerun the Plug-ins installation wizard. Select the existing plug-ins installation root directory. Doing so results in the Web server being configured to use the existing binaries.

Configuration script: 99SGSKitInstall.ant

Log file to investigate for error Recovery
installGSKit.log
Investigate the log file to determine what failed:

In cases where the CD layout is not correct, then the gskit installer program cannot be found. GSKit fails to install.
In cases where GSKit is already installed, the installation might incorrectly report a failure. If the logs show that an installation already existed, you can safely ignore the error.

Manually install GSKit by running the installer program. The installGSKit.log file shows the installer program that runs to install GSKit.
Run the following command from the /cdrom/GSKit directory:

/cdrom/GSKit/gskit.sh

Run the following command from the "E:\GSKit\ directory, assuming the E drive is the CD-ROM drive:

"E:\GSKit\Setup.exe" WASPLUGIN60_041008085014 "C:\Program Files" -s -z -f1"E:\GSKit\setup.iss"

Configuration script: 99SSolarisGSKitInstall4.ant

Log file to investigate for error Recovery
On Solaris, the installation is logged to the installGSKit.log file.
Investigate the log file to determine what failed:

In cases where the CD layout is not correct, then the gskit installer program cannot be found. GSKit fails to install.
In cases where GSKit is already installed, the installation might incorrectly report a failure. If the logs show that an installation already existed, you can safely ignore the error.

Manually install GSKit by running the installer program.
Run the following command from the /cdrom/GSKit directory:

/cdrom/GSKit/gskit4.sh

Configuration script: 90SCreateWinRegPlugin.ant

Log file to investigate for error Recovery

This script does not have an associated log file.
The script creates the Windows registry entry for the Web server plug-ins for WebSphere Application Server.
HKEY_LOCAL_MACHINE > Software > IBM > Web server Plug-ins for IBM WebSphere Application Server > 6.0.0.0
Add the HKEY_LOCAL_MACHINE > Software > IBM > Web server Plug-ins for IBM WAS > 6.0.0.0 key manually with the actual value of the installation location.
Set the following registry values under this key:

Name: plug-ins_install_root
Type: REG_SZ
Data: plug-ins_install_root

Configuration script: 99SModifySetupCmdLine.ant

Log file to investigate for error Recovery

This script does not have an associated log file.
Investigate the plug-ins_install_root/bin/setupCmdLine.sh script to verify that the PLUGIN_HOME variable is set to the Web server plug-ins installation root directory.
Verify that file permissions are 755 (rwxr-xr-x) on Linux and UNIX systems.

We can edit the setupCmdLine file, replacing $(PLUGIN_HOME) with the location to the plug-ins installation root directory.
Change the file permissions to 755. Issue the following command from the plug-ins_install_root/bin directory
chmod 755 setupCmdLine.sh

If you do not find the cause of the problem, open the plug-ins_install_root/logs/Web_servername directory. The directory is empty until the Web server loads the plug-in and errors occur. The plug-in then creates the http_plugin.log file to record the errors. If no errors occur, the directory is empty. Examine any relevant files for error entries. Correct any errors and reinstall.
Does the installation result in a INSTCONFFAILED status?

This is a serious failure of the installation.
Analyze the log files to determine the problem.
Uninstall the plug-ins.
Delete the plug-ins installation root directory.
Install the plug-ins again.

Do errors occur when you start the snoop application?
See "Start the Snoop servlet" in the installation troubleshooting file.
If errors occur, look at the plug-ins_install_root/logs/Web_servername/http_plugin.log file for causes.
Also investigate the WAS installation logs and the logs for your supported Web server.
Do you have the correct file permissions for the configureWeb_server_definition_name script?
On Linux and UNIX systems, copying the configureWeb_server_definition_name.sh script from one operating system, such as AIX, to another, such as HP-UX, can cause the file permissions of the script to be invalid for running the script.
Verify that file permissions are 755 (rwxr-xr-x) on Linux and UNIX systems.

Troubleshooting plug-ins removal

Does the plug-ins_install_root/logs/uninstall directory have any log files?
If log files exist, examine them, correct the errors, and reinstall.
Is there any sign that the removal occurred?
If not, look for the temporaryPluginUnInstallLog.txt file in the temporary directory of the user who installed the plug-ins.
For example, the /tmp/temporaryPluginUnInstallLog.txt file might exist if the root user uninstalled the plug-ins on a Linux or UNIX system.
Does the installation result in a INSTCONFPARTIALSUCCESS status?

Look for errors in the log.txt file.
Look for an entry in the log.txt file that shows the location of the masterConfigurationLog.txt file.
Edit the masterConfigurationLog.txt file.
Starting at the end of the file, scan towards the front of the file looking for configuration scripts that could not run.
For example, the following stanza shows a configuration script that could not run
<record> <date>2004-10-08T10:31:43</date> <millis>1097245903200</millis> <sequence>189</sequence> <logger>com.ibm.ws.install.configmanager.ConfigManager</logger> <level>INFO</level> <class>com.ibm.ws.install.configmanager.ConfigManager</class> <method>dumpNonFatalFailedActionsInfoToLogFile</method> <thread>10</thread> <message>This action failed to execute: C:\Plugins\properties\version\install\plugin\6.0.0.0\ config\full\uninstall\99SGSKitUnInstall.ant</message> </record>

A script that fails to run is likely the cause of a partially successful installation status. To debug our example, look at the installGSKit.log, which is the log file for GSKit. Look for signs of a failed removal to determine if one can correct the problem.

Configuration script Log file to investigate for error

99SBootStrapPluginsSunOneUninstalluniqueID.ant
99SBootStrapPluginsDomino6UninstalluniqueID.ant
99SBootStrapPluginsDomino5UninstalluniqueID.ant
99SBootStrapPluginsIIS6UninstalluniqueID.ant
99SBootStrapPluginsIIS5UninstalluniqueID.ant
99SBootStrapPluginsApacheUninstalluniqueID.ant
99SBootStrapPluginsIHSUninstalluniqueID.ant

uninstallWeb_server_typePlugin.log
For example, the file might be named:
uninstallIHSPlugin.log
Logs the Web server deconfiguration events for the Web server.
99SGSKitUnInstall.ant uninstallGSKit.log
On Windows only, the Web server plugins GSKit key will be unregistered. GSKit is uninstalled if no other product is registered to use GSKit.
On Linux and UNIX, it is your responsibility to uninstall GSKit when no other products are using it.
90SDeleteWinRegPlugin.ant
This script does not have an associated log file.
The script deletes the Windows registry entry for the Web server plug-ins for WebSphere Application Server.
HKEY_LOCAL_MACHINE > Software > IBM > Web server Plug-ins for IBM WebSphere Application Server > 6.0.0.0

Did the uninstall procedure fail?
If the uninstall failed in any way, follow the manual uninstall steps to verify the system is clean and if necessary, remove Web server plug-in entries.

Miscellaneous messages, tips and hints

Option Description
Unable to load mod_was_ap20_http... This error means that the following actions have occurred:

You have the 32-bit version of the Apache Web Server installed on a 64-bit platform.
You used the 64-bit platform CD to install the plug-in for the 32-bit Apache Web Server
You started the Apache Web Server and it could not load the 64-bit plug-in because it requires the 32-bit plug-in.

To fix the problem, install the 32-bit plug-in from the CD for the 32-bit platform. Or manually configure the Apache Web server by changing the httpd.conf file to refer to the correct plug-in. Change the 64bit folder name in the directive to 32bit to fix the reference. For example, change /opt/IBM/WebSphere/Plugins/bin/64bit/mod_was_ap20_http.so to /opt/IBM/WebSphere/Plugins/bin/32bit/mod_was_ap20_http.so on a Linux system.
SAFE_BROWSER_EXCEPTION_CAUGHT This SAFE_BROWSER_EXCEPTION_CAUGHT error means that:

If you do not have a browser, this error is thrown and the roadmap is not launched when it is selected during the installation of the plug-ins.
If you have a supported browser that is not the Konqueror browser, the roadmap is launched. This message is thrown with the supported browser when it is not the Konqueror browser. We can safely ignore this exception and open the roadmap in a supported browser.

number.tmp.sorted
A limitation in ISMP does not remove temporary working files in the / root directory on Solaris operating systems. We can safely ignore or delete the files that follow this naming convention.
WASX7303I: ?????????????
Shell scripts on some operating systems cannot contain double-byte characters or single-byte characters with pronunciation keys.
If the file path to the Web server includes double-byte characters or single-byte characters with pronunciation keys, such as o-umlaut (a diacritic mark over the o), c-cedilla (a mark is under the c), or characters with other keys, the script might not run correctly. Copy the content of such a script to the command line and run the wsadmin command directly.

Result

This procedure results in troubleshooting the installation or removal of the Web server plug-ins for WebSphere Application Server.

What to do next

For current information available from IBM Support on known problems and their resolution, see the IBM Support page.
IBM Support has documents that can save you time gathering the information that we need to resolve a problem. Before opening a PMR, see the IBM Support page.

Option	Description
Unable to load mod_was_ap20_http...	This error means that the following actions have occurred: You have the 32-bit version of the Apache Web Server installed on a 64-bit platform. You used the 64-bit platform CD to install the plug-in for the 32-bit Apache Web Server You started the Apache Web Server and it could not load the 64-bit plug-in because it requires the 32-bit plug-in. To fix the problem, install the 32-bit plug-in from the CD for the 32-bit platform. Or manually configure the Apache Web server by changing the httpd.conf file to refer to the correct plug-in. Change the 64bit folder name in the directive to 32bit to fix the reference. For example, change /opt/IBM/WebSphere/Plugins/bin/64bit/mod_was_ap20_http.so to /opt/IBM/WebSphere/Plugins/bin/32bit/mod_was_ap20_http.so on a Linux system.
SAFE_BROWSER_EXCEPTION_CAUGHT	This SAFE_BROWSER_EXCEPTION_CAUGHT error means that: If you do not have a browser, this error is thrown and the roadmap is not launched when it is selected during the installation of the plug-ins. If you have a supported browser that is not the Konqueror browser, the roadmap is launched. This message is thrown with the supported browser when it is not the Konqueror browser. We can safely ignore this exception and open the roadmap in a supported browser.
number.tmp.sorted	A limitation in ISMP does not remove temporary working files in the / root directory on Solaris operating systems. We can safely ignore or delete the files that follow this naming convention.
WASX7303I: ?????????????	Shell scripts on some operating systems cannot contain double-byte characters or single-byte characters with pronunciation keys. If the file path to the Web server includes double-byte characters or single-byte characters with pronunciation keys, such as o-umlaut (a diacritic mark over the o), c-cedilla (a mark is under the c), or characters with other keys, the script might not run correctly. Copy the content of such a script to the command line and run the wsadmin command directly.