This topic describes troubleshooting the installation and removal of the Web server plug-ins for WebSphere Application Server.
Log files for Web server plug-ins for WebSphere Application Server
File name | Description |
---|---|
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, where Web_server is the Web server
you are installing. Web_server can have one of the following
values:
|
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. |
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 Uninstalling the Web server plug-ins for WebSphere Application Server for more information.
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.
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 -is:javahome option for the Install Shield for Multiplatforms (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 the plugins_root/logs/install/log.txt file.
Verify the cause of the error by examining the CURRENT_WORKING_DIRECTORY value and the JAVA_INSTALL_PATH value in the log.txt file. The working directory value is typically the CD_root/plugin directory. An erroneous Java path might be non_CD_root/java/jre. The correct Java path is the CD_root/JDK/repository/prereq.jdk/java/jre directory.
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 INSTCONFPARTIALSUCCESS indicator.
The plugins_root/logs/install/masterConfigurationLog.txt log file shows that the 99SGSKitInstall.ant script failed to run. Complete the full installation by manually installing GSKit. The plugins_root/logs/install/installGSKit.log file shows the command to use for the manual installation in the GSKIT 7 entry.
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 system such as AIX or Linux.
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 you cannot get your copy to work.
Config action failed: 98SConfigureWebserverDefinition - install_root\properties\version\nif\config\install\ 98SConfigureWebserverDefinition.ant Current install/uninstall process is successful. Process type is: install
<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>
Configuration script log files and recovery procedures: The following configuration scripts run during the configuration of supported Web servers.
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. |
|
Log file to investigate for error | Recovery |
---|---|
installSunOnePlugin.log Investigate
the log file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installDomino6Plugin.log Investigate
the log file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installDomino5Plugin.log Investigate
the log file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installIIS6Plugin.log Investigate
the log file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installIIS5Plugin.log Investigate
the log file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installApachePlugin.log Investigate
the log file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installIHSPlugin.log Investigate
the log file to determine what failed:
|
|
Log file to investigate for error | Recovery |
---|---|
installGSKit.log Investigate
the log file to determine what failed:
|
Manually install GSKit by running the installer program. The installGSKit.log file shows the installer program that runs to install GSKit. ![]() ![]() ![]() ![]()
![]()
|
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:
|
Manually install GSKit by running the installer program. ![]()
|
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 WebSphere Application Server > 6.0.0.0 key manually
with the actual value of the installation location. Set the following registry
values under this key:
|
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. |
|
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.
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 WebSphere Application Server installation logs and the logs for your supported Web server.
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.
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
If the Network Deployment product cannot resolve the host name of the server, problems can occur with such situations as adding or administering nodes, or the node agent contacting the application server. To resolve the host name, the product opens a port, or queries for an IP address. The product then waits for the operating system to return the correct information. The operating system might go to multiple places to find the IP address, but the product does not care about the order in which the operating system does this, if the correct information is returned. If the host name of the server cannot be resolved, refer to your network administration documentation to resolve the problem. The following additional information might help you ensure that the host name is resolved.
If in the hosts file mappings exist from the 127.0.0.1 IP address to a host name other than localhost, remove the mappings. The following example illustrates what might happen if the mappings are not removed: When a node agent communicates with the deployment manager, it sends its IP address to the deployment manager. The node agent resolves the node agent host name to 127.0.0.1 if the operating system returns a mapping for the host name from the hosts file. This resolution prevents the deployment manager from sending a message to the node agent because the 127.0.0.1 IP address is also the IP address for the local machine of the deployment manager.
The
hosts file is located at /etc/hosts.
The
hosts file is located at \WINDOWS\system32\drivers\etc\hosts.
hosts=local,bind
If log files exist, examine them, correct the errors, and reinstall.
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.
<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>
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 WebSphere Application Server. HKEY_LOCAL_MACHINE > Software > IBM > Web server Plug-ins for IBM WebSphere Application Server > 6.0.0.0 |
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.
Option | Description |
---|---|
Unable to load mod_was_ap20_http... | This
error means that the following actions have occurred:
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:
|
![]() |
|
This procedure results in troubleshooting the installation or removal of the Web server plug-ins for WebSphere Application Server.
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 you need to resolve a problem. Before opening a PMR, see the IBM Support page.
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience. This feature requires Internet access. Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof. |