Troubleshoot Web server plug-ins installation and removal

 

+

Search Tips   |   Advanced Search

 

  1. Overview
  2. Plug-ins installation
  3. Plug-ins removal
  4. Miscellaneous messages, tips, and hints

 

Overview

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

See also...

 

Log files for Web server plug-ins for WAS

The following log files are in...

plug-ins plugins_root/logs/install

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

Troubleshooting plug-ins installation

  1. Are you reinstalling with an INSTCONFSUCCESS message but no files are being installed?

    If you do not use the Web server Plug-ins uninstaller program to uninstall the plug-ins, a reinstall can fail with an INSTCONFSUCCESS message.

    The Web server Plug-ins installer is an Install Shield for Multiplatforms (ISMP) wizard. The wizard uses the vpd.properties file or the operating system registry to determine if the plug-ins are installed.

    If you do not use the uninstaller program for the plug-ins, neither the vpd.properties file nor the operating system registry is updated properly. You might see a...

    plugins_root/logs/install/log.txt

    ...with content similar to the following example:

    Plugin.Install, com.installshield.product.service.product.
       PureJavaProductServiceImpl$InstallProduct, msg1, 
       Did not replace installed object (IBM WebSphere Application 
       Server - Plugins) with object (IBM WebSphere Application 
       Server - Plugins)
    Plugin.Install, ... msg1, Did not replace installed object 
       (WebServer Plugin Binaries and Configurations) with 
       object (WebServer Plugin Binaries and Configurations)
    Plugin.Install... Did not replace installed object (GSKit) with object (GSKit)
    Plugin.Install... Did not replace installed object (LAP Component) with 
       object (LAP Component)
    Plugin.Install...Did not replace installed object (WebServer Plugin 
       Binaries) with object (WebServer Plugin Binaries)
    Plugin.Install... Did not replace installed object (Additional Bytes 
       for non-HP) with object (Additional Bytes for non-HP)
    Plugin.Install... Did not replace installed object (GSKit) with object (GSKit)
    Plugin.Install... Did not replace installed object (Standalone JDK) 
       with object (Standalone JDK)
    
    

    Use the uninstaller program in the...

    plugins_root/uninstPlugin

    ...directory to uninstall the Web server Plug-ins. For example, do not delete the...

    plugins_root

    ...directory to uninstall the plug-ins without running the installer program first.

    If you have this problem, follow the uninstall procedure and the manual uninstall procedure to clean up your system before reinstalling the Web server Plug-ins.

    See Uninstall the Web server plug-ins for WAS for more information.

  2. Does the installation image have the proper directories? The following directories are present on the installation image of the full product. The directories in bold are required for a successful installation of the plug-ins:

    • ./WAS
    • ./IHS
    • ./plugin
    • ./AppClient
    • ./JDK
    • ./GSKit

    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.

 

Symptoms that can occur when the JDK directory is missing or is not used:

If log file...

plugins_root/logs/install/log.txt

...records the following errors, the installer program did not use the correct Java 2 SDK, which is in the JDK directory on the installation image:

Plugin.Install, com.ibm.ws.install.ni.ismp.actions. ISMPComponentizedFileRepositoryDeployAction, msg1, Processing component: prereq.jdk

Plugin.Install, com.ibm.ws.install.ni.ismp.actions. ISMPComponentizedFileRepositoryDeployAction, err, Component not found: prereq.jdk

Plugin.Install, com.ibm.ws.install.ni.ismp.actions. ISMPComponentizedFileRepositoryDeployAction, err, ComponentNotFoundException.message

The installation program can pick up another Java 2 SDK 1.4 on the system when running from the command prompt in terminal window that already has set the Java 2 SDK for the environment. Another way to point the installation program to a particular SDK is with the option...

-is:javahome

...option for the ISMP wizard.

In either case, the JDK directory on the installation image is not being used. When the installation attempts to install the prereq.jdk component, the wizard cannot find the JDK directory and throws the error in...

plugins_root/logs/install/log.txt

Verify the cause of the error by examining the values of ...

CURRENT_WORKING_DIRECTORY
JAVA_INSTALL_PATH

The working directory value is typically...

CD_root/plugin

An erroneous Java path might be...

non_CD_root/java/jre

The correct Java path is...

CD_root/JDK/repository/prereq.jdk/java/jre
In such a case:

  1. Verify that the JDK directory is on the product disc.

  2. Close the current command window.

  3. Open a new command window.

  4. Change directories to the plugin directory on the product disc.

  5. Restart the installation: ./install

 

Symptoms that occur when the GSKit directory is missing:

If the JDK directory is present, but the GSKit directory is not present, the installation is only partially successful, as shown in the logs by the indicator...

INSTCONFPARTIALSUCCESS

The log file...

plugins_root/logs/install/masterConfigurationLog.txt

...shows that the 99SGSKitInstall.ant script failed to run. Complete the full installation by manually installing GSKit. The file...

plugins_root/logs/install/installGSKit.log

...shows the command to use for the manual installation in the GSKIT 7 entry.

 

Configuration script log files and recovery procedures:

The following configuration scripts run during the configuration of supported Web servers.

 

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.

  1. If the Web server definition partially exists, delete the Web server definition.

  2. Run the Web server definition script manually. The Web server definition is referenced in the script. The script is in the...

    plugins_root/bin

    ...directory, with a name similar to the following convention:

      configureWeb_server_definition_name.sh

 

99SBootStrapPluginsSunOne.ant

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

  1. If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.

  2. If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.

  3. If the Web server configuration files do not update, investigate the files to verify that they exist and that the file permissions are correct.

 

99SBootStrapPluginsDomino6.ant

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

  1. If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.

  2. If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.

  3. If the Web server configuration files do not update, investigate the files to verify that they exist and that the file permissions are correct.

  • You can manually configure the Web server by following the procedure documented in Configure Lotus Domino.

  • You 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.

 

99SBootStrapPluginsDomino5.ant

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

  1. If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.

  2. If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.

  3. If the Web server configuration files do not update, investigate the files to verify that they exist and that the file permissions are correct.

  • You can manually configure the Web server by following the procedure documented in Configure Lotus Domino.

  • You 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.

 

99SBootStrapPluginsIIS6.ant

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

  1. If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.

  2. If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.

  3. Start the Internet Information Services (IIS) application and investigate the IIS configuration.

 

99SBootStrapPluginsIIS5.ant

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

  1. If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.

  2. If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.

  3. Start the IIS application and investigate the IIS configuration.

 

99SBootStrapPluginsApache.ant

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

  1. If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.

  2. If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.

  3. If the Web server configuration files do not update, investigate the files to verify that they exist and that the file permissions are correct.

  • You can manually configure the Web server by following the procedure documented in Configure Apache HTTP Server V2.0.

  • You 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.

 

99SBootStrapPluginsIHS.ant

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

  1. If the error is due to plugin-cfg.xml not existing, investigate why this file is not present.

  2. If the error is due to the Web server definition creation failing, address this as discussed under the 98SConfigureWebserverDefinition.ant description.

  3. If the Web server configuration files do not update, investigate the files to verify that they exist and that the file permissions are correct.

  • You can manually configure the Web server by following the procedure documented in Configure IBM HTTP Server V6.x.

  • You 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.

 

99SGSKitInstall.ant

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

  1. In cases where the CD layout is not correct, then the gskit installer program cannot be found. GSKit fails to install.

  2. 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. [AIX] [HP-UX] [Linux] [Solaris] Run the following command from the /cdrom/GSKit directory:

  • /cdrom/GSKit/gskit.sh

[Windows] 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"

[Solaris] 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:

  1. In cases where the CD layout is not correct, then the gskit installer program cannot be found. GSKit fails to install.

  2. 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. [Solaris] Run the following command from the /cdrom/GSKit directory:

  • /cdrom/GSKit/gskit4.sh

[Windows] 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 WAS.

HKEY_LOCAL_MACHINE > Software > IBM > Web server Plug-ins for IBM WAS > 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:

 

99SModifySetupCmdLine.ant

Log file to investigate for error Recovery

This script does not have an associated log file.

Investigate the...

plugins_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 systems such as AIX or Linux.

  • You 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...

    plugins_root/bin

    ...directory:

    chmod 755 setupCmdLine.sh
    

If you do not find the cause of the problem, open the...

plugins_root/logs/web_server_name

...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?

    1. This is a serious failure of the installation.

    2. Analyze the log files to determine the problem.

    3. Uninstall the plug-ins.

    4. Delete the plug-ins installation root directory.

    5. 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...

    plugins_root/logs/web_server_name/http_plugin.log

    ...file for causes.

    Also investigate the WAS installation logs and the logs for your supported Web server.

  • [AIX] [HP-UX] [Linux] [Solaris] Do you have the correct file permissions for the configureWeb_server_definition_name script?

    On operating systems such as AIX or Linux, 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 systems such as AIX or Linux.

  • [AIX] [HP-UX] [Linux] [Solaris] Are you using the configureWeb_server_definition_name script when the Web server machine is running dynamic host configuration protocol (DHCP)?

    The configureweb_server_name.sh script can contain null values for the name of the host machine of the Web server when using DHCP. Examine the script to see if the last few parameters include the word null. If so, you have this problem.

    The plugins.install log file might also have an entry for the problem:

     (MMM DD, YYYY HH:MM:SS AM|PM),
    Plugin.Install, com.ibm.ws.install.ni.ismp.actions.ISMPLogFileAction, msg1, WEB_SERVER_HOSTNAME : null
    
    

    Some systems such as AIX or Linux create an association between the host name of the machine and the loopback address -- 127.0.0.1. Red Hat Linux and other Linux systems set the association by default, for example.

    In addition, the /etc/nsswitch.conf file uses the /etc/hosts path before looking up a server using a DNS name server. This setup can cause failures when installing the Web server plug-ins for WAS. Perform the following steps to successfully create the configuration script for creating and configuring the Web server definition in the appserver node:

    1. Uninstall the Web server plug-ins.

    2. Remove the 127.0.0.1 mapping to the local host in the /etc/hosts file.

    3. Edit the /etc/nsswitch.conf file so that the hosts line reads:

       hosts:  files [NOTFOUND=return] nis [NOTFOUND=return] dns
      
      

    4. Install the Web server plug-ins again.

     

    Troubleshooting plug-ins removal

    1. Does the...

      plugins_root/logs/uninstall

      ...directory have any log files?

      If log files exist, examine them, correct the errors, and reinstall.

    2. 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 system such as AIX or Linux.

    3. Does the installation result in a INSTCONFPARTIALSUCCESS status?

      1. Look for errors in the log.txt file.

      2. Look for an entry in the log.txt file that shows the location of the masterConfigurationLog.txt file.

      3. Edit the masterConfigurationLog.txt file.

      4. Start 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>
        

      5. 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 you 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 operating systems such as AIX or Linux, 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 WAS.

      HKEY_LOCAL_MACHINE > Software > IBM > Web server Plug-ins for IBM WAS > 6.0.0.0

    4. 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/WAS/Plugins/bin/64bit/mod_was_ap20_http.so to /opt/IBM/WAS/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.

    • [AIX] [HP-UX] [Linux] [Solaris] 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. You can safely ignore this exception and open the roadmap in a supported browser.

    [Solaris] number.tmp.sorted

    [Solaris] A limitation in ISMP does not remove temporary working files in the / root directory on Solaris operating systems. You can safely ignore or delete the files that follow this naming convention.

    [AIX] [HP-UX] [Linux] [Solaris] 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.

     

    Results

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

     

    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 resolve a problem. Before opening a PMR, see the IBM Support page.


     

    Related tasks


    Troubleshooting installation