Troubleshooting installation

This topic describes troubleshooting the installation of the WebSphere Application Server product.

Before you begin

If you are looking for troubleshooting information for the Web server plug-ins for WebSphere Application Server, see Troubleshooting Web server plug-ins installation and removal. This topic does not describe the plug-ins.

Use this topic after installing your WebSphere Application Server product.

A successful installation of a WebSphere Application Server product installs the core product files and creates the server1 Application Server.

[Solaris] Attention: If the InstallShield MultiPlatform (ISMP) process (install command) fails, you can continue this task of collecting diagnostic information to determine the cause of failure. However, you can try to perform the installation of the core product files by invoking Java directly using the following command.
../JDK/jre.pak/repository/package.java.jre/java/jre/bin/java -cp
setup.jar run
This work around process can successfully perform the installation.

If an installation is not successful, use this troubleshooting information to correct the problems.

About this task

Use this topic to help interpret the log files and diagnose possible problems when the installation is unsuccessful.

The installer program records the following indicators of success in the logs:
  • INSTCONFSUCCESS
  • INSTCONFPARTIALSUCCESS
  • INSTCONFFAILED

Procedure

  1. Use the First steps console to run the installation verification test (IVT).

    The installation wizard can start the First steps console at the end of installation. Select Installation verification. Check the profile_root/logs/ivt.log file for a summary of test results. Correct any errors and retry. If you performed a custom installation, the location of the default profile is in the profiles installation root directory that you selected during the installation.

    If you created another profile using the Profile Management tool or the manageprofiles command, the location of the profile and the name of the profile are different than what is displayed in the example.

  2. Run the installver command to calculate and compare checksums for all installed components to the bill of materials list for the product.

    See Verifying checksums of installed files for more information.

    Compare the output from the installver command to the installation log files that are described in the next step.

  3. Check the installation log files for errors after installing:

    The app_server_root/logs/install/log.txt file and the app_server_root/logs/manageprofiles/profile_name_create.log file record installation and profile creation status.

    If the error happens early in the installation, look for the log.txt file in the system temporary area. The installation program copies the log from the temporary area to the logs directory at the end of the installation.

    During installation, a single entry in the app_server_root/logs/install/log.txt file points to the temporary log file, either %TEMP%\log.txt on Windows platforms, or /tmp/log.txt on platforms such as AIX or Linux. The installation program copies the file from the temporary directory to the app_server_root/logs/install/log.txt location at the end of the installation.

    If the installation fails and the log.txt file has only this one pointer to the temporary directory, open the log.txt file in the temporary directory. The log might have clues to the installation failure.

    Uninstalling creates the app_server_root/logs/uninstall/log.txt file.

    Log more information when InstallShield MultiPlatform (ISMP) cannot start the installation wizard.

    Certain events can prevent the installer from starting the installation wizard. Such an event is not enough disk space to launch the installation wizard, for example. If your installation fails and there is no information in the installation logs, use the -log parameter to record entries for events that cause the installer program to fail to start the installation wizard. The syntax of the install command for logging such events is:
    install  -options fully_qualified_options_response_file_name               
             -silent
             -log # !fully_qualified_log_file_name  @ALL 
    • [AIX]
      install -options "/usr/IBM/WebSphere/silentFiles/myresponsefile.txt" 
              -silent -log # !/usr/IBM/WebSphere/myOptionFiles/log.txt  @ALL
      
    • [Linux] [HP-UX] [Solaris]
      install -options "/opt/IBM/WebSphere/silentFiles/myresponsefile.txt" 
              -silent -log # !/opt/IBM/WebSphere/myOptionFiles/log.txt  @ALL
      
    • [Windows]
      install.exe -options "C:\IBM\WebSphere\silentFiles\myresponsefile.txt" 
                  -silent -log # !C:\IBM\WebSphere\silentFiles\log.txt  @ALL

    Log file names and locations

    The following information shows the log files for all of the installable components on the product disc.

    Log files for IBM HTTP Server

    The following table shows the installation log locations when installing IBM HTTP Server.
    Table 1. Installation log locations when installing IBM HTTP Server
    Windows system log path name Log path name on operating systems such as AIX or Linux

    [Windows] C:\Program Files\IBM HTTP Server\log.txt

    [Windows] C:\Program Files\IBM HTTP Server\ihsv61_install.log

    [AIX] /usr/IBMHttpServer/ log.txt

    [AIX] /usr/IBMHttpServer/ ihsv61_install.log

    [Linux] [HP-UX] [Solaris] /opt/IBMHttpServer/ log.txt

    [Linux] [HP-UX] [Solaris] /opt/IBMHttpServer/ ihsv61_install.log

    Log files for Application Client for WebSphere Application Server

    The following table shows the installation log locations when installing the Application Client.
    Table 2. Installation log locations when installing the Application Client for WebSphere Application Server
    Windows system log path name Operating system log path name on systems such as AIX or Linux

    [Windows] C:\Program Files\IBM\WebSphere\ AppClient\logs\log.txt

    [AIX] /usr/IBM/WebSphere/AppClient/logs/log.txt

    [Linux] [HP-UX] [Solaris] /opt/IBM/WebSphere/AppClient/logs/log.txt

    Product Log files: The following table shows the installation logs, content, and indicators of success and failure for the product:
    Table 3. Installation and profile creation log files
    Log Content Indicators
    app_server_root /logs/install/log.txt Logs all installation events
    Return code
    Meaning
    0
    Success
    1
    Failure
    2
    Partial Success
    app_server_root/logs/install/ installconfig.log.gz
    • Logs the activities of ANT configuration scripts that run at the end of the installation procedure
    • Gzip file
    Configuration action failed:
    Unsuccessful ANT script configuration.
    Configuration action succeeded:
    Successful ANT script configuration.

    Description of the profile_name_create.log file

    The profile_name_create.log file is an XML file that contains a record of the events that occur during the creation of the last profile.

    In addition to the date tag at the beginning of the file, other tags of interest in the log files include the sequence tag, the level tag, the method tag, and the message tag:
    • The sequence tag records the sequence of events that occur during the creation of the profile.
    • The level tag is an early indicator of event status:
      INFO
      Indicates a normal event.
      WARNING
      Indicates an event that occurred with errors that do not prevent the creation of the profile.
      ERROR
      Indicates an event that prevents the creation of the profile.
    • The method tag indicates the name of the routine that recorded the event.
    • The message tag describes the event and contains any data returned by the method.
    The following stanza is an example of how an event is documented in each log file:
    <record>
      <date>2004-09-08T11:51:39</date>
      <millis>1094658699225</millis>
      <sequence>0</sequence>
      <logger>com.ibm.ws.profile.WSProfile</logger>
      <level>INFO</level>
      <class>com.ibm.ws.profile.WSProfile</class>
      <method>getRegistryFile</method>
      <thread>10</thread>
      <message>Returning registry file at: 
         C:\IBM\WebSphere\AppServer\properties\profileRegistry.xml
      </message>
    </record>

    Log files created during the creation of the Application Server profile

    In addition to the logs created within the core product files, the following logs are created in the profile_root/logs directory.

    Both the Profile Management tool and the manageprofiles command create the log when creating an application server profile:

    activity.log
    Compiled activity log from various installation activities
    amjrte_config.log
    Tivoli Access Manager configuration log for its Java Runtime Environment
    collect_metadata.log
    Collects metadata information about managed objects in the system to evaluate and prevent potential installation conflicts
    createDefaultServer.log
    A log from wsadmin recording the creation of the server1 process in the default profile
    createshortcutforprofile.log
    Windows tool log for creating menu entries and shortcuts
    defaultapp_config.log
    JACL script log from configuring default application resources
    defaultapp_deploy.log
    Application DefaultApplication installation log
    node_name Service.log
    Start and stop events for server1
    filetransfer_config.log
    Application filetransfer installation log
    ivt_config.log
    Application ivtApp installation log
    mejb_config.log
    Application ManagementEJB installation log
    query_config.log
    Application Query installation log
    samples_config.log
    Configuration log for the PlantsByWebSphere Samples application
    samples_install.log
    Installation log for the SamplesGallery and PlantsByWebSphere Samples applications
    scheduler.cal_config.log
    Application SchedulerCalendars installation log
    SIBDefineChains.log
    Creation log for service integration bus endpoints, inbound channels and channel chains, outbound thread pool, and outbound channel and channel chains
    SIBDeployRA.log
    Deployment log for the service integration bus function
    webui_config.log
    Application administrative console installation log
    winservice_config.log [Windows]
    Service log for the Windows service created for server1
    The following logs are created in the profile_root/logs/server1 directory:
    startServer.log
    Log of start server events
    stopServer.log
    Log of stop server events
    SystemErr.log
    Record system errors
    SystemOut.log
    Log of all activity within the system
    trace.log
    Log of all traced events within the system
    The following logs are created in the profile_root/logs/ffdc directory:
    server1_exception.log
    First failure data capture log for server1 errors
    server1_numeric_identifier.txt
    Any first failure data capture logs

    Log files for Web server plug-ins for WebSphere Application Server

    See Troubleshooting Web server plug-ins installation and removal for a description of log files and other troubleshooting information.

  4. Determine whether the installation problem is caused by a failing ANT script.

    The app_server_root/logs/instconfig.log file indicates ANT configuration problems that could prevent the product from working correctly. The log file is not present on systems such as AIX or Linux.

    See Diagnosing a failing ANT configuration script for a description of how to manually diagnose and fix an ANT script problem.

  5. Verify that no files exist in the app_server_root/classes directory.

    IBM Support sometimes queues work for customers and provides test or debugging fixes. A common location for the fixes is in the app_server_root/classes directory.

    By default, the app_server_root/classes directory is picked up first in the WebSphere Application Server class path to let it override other classes.

    Putting a fix in the directory lets you verify that the fix does indeed solve your problem. After verifying that the fix solves the problem, you are supposed to delete the fix from the app_server_root/classes directory to return the system to a working state.

    If you do not remove such fixes from the app_server_root/classes directory, you can experience errors.

  6. Uninstall the product, if possible, and reinstall after turning on tracing if the error logs do not contain enough information to determine the cause of the problem.
    • Report the stdout and stderr logs to the console window, by adding the -is:javaconsole parameter to the install command:
      • [AIX] [HP-UX] [Linux] [Solaris]
        ./install -is:javaconsole
        Capture the stream to a file with the following commands:
        ./install -is:javaconsole > captureFileName.txt 2>&1
      • [Windows]
        install.exe -is:javaconsole
        Capture the stream to a file with the following commands:
        install -is:javaconsole > drive:\captureFileName.txt
      Avoid trouble Avoid trouble: Although the usage of -is:javaconsole is supported, the usage of -console, for example install -console, is not supported.gotcha
    • Capture additional information to a log of your choice with the -is:log file_name option.
    • Turn on additional installation logging by passing the -W Setup.product.install.logAllEvents="true" parameter to the install command:
      • [AIX] [HP-UX] [Linux] [Solaris]
        install -W Setup.product.install.logAllEvents="true"
      • [Windows]
        install -W Setup.product.install.logAllEvents="true"
  7. Use the First steps console or the command line method to start the application server.
    Start the First steps console for a particular node:
    Start the server from the command line:
    1. Change directories to the profile_root/bin directory in the profile.
    2. Start the server process.
      • [AIX] [HP-UX] [Linux] [Solaris] ./startServer.sh server1
      • [Windows] startServer server1
  8. Verify whether the server starts and loads properly by looking for a running Java process and the Open for e-business message in the SystemOut.log and SystemErr.log files.

    If no Java process exists or if the message does not appear, examine the same logs for any miscellaneous errors. Correct any errors and retry.

    You can find the SystemOut.log and SystemErr.log files in the profile_root/logs/server1 (platforms such as AIX or Linux) or profile_root\logs\server1 (Windows platforms) directory in an Application Server profile.

  9. Start the Snoop servlet to verify the ability of the Web server to retrieve an application from the Application Server.

    Test your environment by starting your Application Server, your Web server, and using the snoop servlet with an IP address.

    1. Start the Application Server.
      Change directories to the profile_root/bin directory and run the startServer command:
      • [AIX] [HP-UX] [Linux] [Solaris] ./startServer.sh server1
      • [Windows] startServer server1
    2. Start the IBM® HTTP Server or the Web server that you are using.

      Use a command window to change the directory to the IBM HTTP Server installed image, or to the installed image of your Web server. Issue the appropriate command to start the Web server, such as these commands for IBM HTTP Server:

      To start the IBM HTTP Server from the command line:

      Access the apache and apachectl commands in the IBMHttpServer/bin directory.
      • [AIX] [HP-UX] [Linux] [Solaris] ./apachectl start
      • [Windows] apache
    3. Point your browser to http://localhost:9080/snoop to test the internal HTTP transport provided by the Application Server. Point your browser to http://Host_name_of_Web_server_machine/snoop to test the Web server plug-in.

      The HTTP Transport port is 9080 by default and must be unique for every profile. The port is associated with a virtual host named default_host, which is configured to host the installed DefaultApplication and any installed Samples. The snoop servlet is part of the DefaultApplication. Change the port to match your actual HTTP Transport port.

    4. Verify that snoop is running.

      Either Web address should display the Snoop Servlet - Request/Client Information page.

    5. Remote IBM HTTP Server only:
      Verify that the automatic propagation function can work on a remote IBM HTTP Server by using the following steps. This procedure is not necessary for local Web servers.
      1. Create a user=adminUser, password=adminPassword in the IHS_root /conf/admin.passwd file. For example: c:\ws\ihs60\bin\htpasswd -cb c:\ws\ihs60\conf\admin.passwd adminUser adminPassword
      2. Use the administrative console of the Application Server to enter the User ID and password information that you created for the administrative user of IBM HTTP Server. Go to Servers > Web server > Web_server_definition > Remote Web server administration. Set the following values: admin Port=8008, User Id=adminUser, Password=adminPassword.
      3. Set the correct read/write permissions for the httpd.conf file and the plugin-cfg.xml file. See the IHS_root /logs/admin_error.log file for more information.
      Automatic propagation of the plug-in configuration file requires the IBM HTTP administrative server to be up and running. If you are managing an IBM HTTP Server using the WebSphere® Application Server administrative console, the following error might display:
      "Could not connect to IHS Administration server error"
      Perform the following procedure to correct the error:
      1. Verify that the IBM HTTP Server administration server is running.
      2. Verify that the Web server host name and the port that is defined in the WebSphere Application Server administrative console matches the IBM HTTP Server administration host name and port.
      3. Verify that the fire wall is not preventing you from accessing the IBM HTTP Server administration server from the WebSphere Application Server administrative console.
      4. Verify that the user ID and password that is specified in the WebSphere Application Server administrative console under remote managed, is created in the admin.passwd file, using the htpasswd command.
      5. If you are trying to connect securely, verify that you export the IBM HTTP Server administration server keydb personal certificate into the WebSphere Application Server key database as a signer certificate. This key database is specified by the com.ibm.ssl.trustStore directive in the sas.client.props file in the profile where your administrative console is running. This consideration is primarily for self-signed certificates.
      6. If you still have problems, check the IBM HTTP Server admin_error.log file and the WebSphere Application Server logs (trace.log file) to determine the cause of the problem.
  10. Start the WebSphere Application Server administrative console.
    1. Start the Application Server.
    2. Point your browser to http://localhost:9060/ibm/console.

      The HTTP Admin port is 9060 by default and must be unique for the administrative console of each stand-alone Application Server. The port is associated with a virtual host named admin_host, which is configured to host the administrative console, which is installed by default as a system application. Change the port to match your actual HTTP Admin port.

      If you have problems accessing the administrative console after installation, check the installAdminConsole.log file for a failure indication. Clean up the system temporary directory and reinstall the administrative console using the wsadmin scripting facility.

    3. Type any ID and click OK at the administrative console window.

    The server starts. The administrative console starts. You can access the administrative console through the browser. The administrative console accepts your login.

  11. Resolve any IP address caching problems.

    By default, the Java 2 SDK caches the IP address for the domain name service (DNS) naming lookup. After resolving the host name successfully, the IP address stays in the cache. By default, the cache entry remains forever.

    This default IP caching mechanism can cause problems, as described in the following problem scenarios.

    Problem scenario 1

    Suppose the Application Server at host1.ibm.com has an initial IP address of 1.2.3.4. When a client at host2.ibm.com conducts a DNS lookup of host1.ibm.com, the client stores the 1.2.3.4 address in the cache. Subsequent DNS name lookups return the cached value, 1.2.3.4.

    The cached value is not a problem until the host1.ibm.com IP address changes, to 5.6.7.8, for example. The client at host2.ibm.com does not retrieve the current IP address, but always retrieves the previous address from the cache.

    If this scenario occurs, the client cannot reach host1.ibm.com unless you stop and restart the client process.

    Problem scenario 2

    Suppose the Application Server at host1.ibm.com has an initial IP address of 1.2.4.5. Although the IP address of the application server does not change, a network outage can record an exception code as the IP address in the cache, where it remains until the client is restarted on a working network.

    For example, if the client at host2.ibm.com disconnects from the network because of an unplugged cable, the disconnected lookup of the Application Server at host1.ibm.com fails. The failure causes the IBM Developer Kit to put the special exception code entry into the IP address cache.

    Subsequent DNS name lookups return the exception code, which is java.net.UnknownHostException.

    For more information about the Java 2 SDK

    The Java 2 Platform Standard Edition (J2SE) 1.4.2 Web site and the Java 2 Platform Standard Edition (J2SE) 1.5 Web site describe the private sun.net.inetaddr.ttl property, which works in both J2SE 1.4.2 (WebSphere Application Server Version 5.1 and Version 6.0) and J2SE 1.5 (WebSphere Application Server Version 6.1).

  12. [Linux] Restore the original copy of the /etc/issue file if the file is modified.

    The prereqChecker program in the installation wizard uses the file to verify the version of the operating system. If you cannot restore the original version, ignore the Operating System Level Check message about the operating system being unsupported. The installation can continue successfully despite the warning.

Results

This procedure results in debugging errors that might occur during installation.

What to do next

The Installation problems contains more detailed debugging and reporting instructions. See Installation component troubleshooting tips for more information about troubleshooting the installation.

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


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.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 4:53:43 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-dist&topic=tins_trouble
File name: tins_trouble.html