IBM Support

PM33510: INCORRECT LOG MESSAGES IN INSTALL LOGS, REPORTED SUCCESS INSTEAD OF FAILURE WHEN PROFILE CREATION FAILED.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • On Websphere Application Server v7.0, when profile creation
    failed due to incorrect hostname configuration: Operating
    System "hostname" is configured on machine, but there is no
    entry for this hostname in file "/etc/hosts". The install log in
    <WAS_HOME>/install/logs directory still shows a success
    message: INSTCONFSUCCESS. This is mis-leading message, instead
    should be INSTCONFPARTIALSUCCESS as profile creation failed.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users who install IBM WebSphere Application *
    *                  Server and create profiles during the       *
    *                  install process on the system which meet    *
    *                  the following two conditions:               *
    *                  1) Operating System "hostname" is           *
    *                  configured on the machine;                  *
    *                  2) There is no entry for this hostname in   *
    *                  the configuration file "/etc/host".         *
    ****************************************************************
    * PROBLEM DESCRIPTION: When installing Application             *
    *                      Server &#175;   &#146;profile creation will fail,
    *                      but the installer reports               *
    *                      "INSTCONFSUCCESS" in log.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    WebSphere Application Server Installer invokes Profile
    Management Tools (PMT) for profile generation, and checks the
    return code from PMT to understand if the operation was
    successful or not. In this very limited situation PMT
    encountered an exception and the profile was not created,
    however PMT returns zero as a return code to the installer.
    That's why installer thinks profile creation was successful.
    

Problem conclusion

  • Besides the return code, the installer will also check
    "Standard Output" from PMT to understand if profile creation
    was successful or not.
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.19. The change will take effect when customer s
    build a Customized Installation Package (CIP) via Install
    Factory (IF), using WebSphere Application Server plus the
    fix pack which contains this fix.
    Please refer to the Recommended Updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM33510

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-02-24

  • Closed date

    2011-04-04

  • Last modified date

    2011-04-04

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM33510

Modified date: 04 April 2011