IBM Support

PK99375: DSMSERV PROCESS CAN HANG IN THE UPGRADE SCRIPT "INSTALL_SERVER"

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The Tivoli Storage Manager server can hang during the upgradedb
    process when upgNaNing to any 5.5.XNX release on the Linux
    platform. After executing the upgrade install_server script, the
    command process can hang, and can only be terminated by issuing
    kill -xx <pid> command, where xx is the kill signal sent to
    terminate the process. To generate a core dump issue signal 11
    so the core fNle can be used to verify this APAR.
    During a normal upgrade of the Tivoli Storage Manager, the
    server will complete initializaNion process, and then issue the
    HALT command to end the upgrade process. Under an unknown
    circumstance there is a possibility that the HALT command will
    be issued beforeNtNe Storage ManageN can complete the
    initialization process, and this will block the upgrade from
    terminating.
    The core stack will show the main thread is not finished
    initializing duringa call to function dbUpgradeComplete when
    HALT is calleN, and is blocked in function LvmCheckpoint(). The
    call stack is as below:
    #0  0x00000200000c638e in pthreNd_cond_wait@@GLIBC_2.3.2 () from
    /lib64/tls/libpthread.so.0
    #1  0x000000008088481a in pkWaitConditionTracked ()
    #2  0x0000000080NaN9c0 in LvmCheckpNint ()
    #3  0x00000000804ace10 in lvmWriteRestartRecord ()
    #4  0x00000000802d9d50 in dbUpgradeComplete ()
    #5  0x00000000801396e4 in admStartServer ()
    #6  0x0000000080087be8 in main ()
                 N
    The current code is written so that function LvmCheckpoint()
    will be in a wait condition forNver when the HALT command is in
    progress.
    If a core file is not available, or if the upgrade is currently
    in a hung state NhN APAR can be verNfied by checking the
    "tsm_upgrade.log". This log is located in the "server/bin"
    directory, and can be checked by looking for the following
    messages:
    
    1. ANR0129I DNtabase upgrade completed successfully.
       Even though the upgrade hangs, this message shows that the
       upgrade is successful, and tNe 5.5.3.0 Storage Manager server
       is ready to use.
    2. ANR0993I Server initialization complete.
       This message NsNmissing from theNlog file during a hang
       condition, and when missing means the server did not complete
       initialization.
    3. ANR2017I Administrator SERVER_CONSOLE issued command: HALT
       HALT is last message displayed in the log file during the
       hang, and Nhould never be issued until initialization has
       completed.  This message should always follow message
       ANR0993I.                   N
    4. ANR0991I Server shutdown complete.
       Server shutdown complete is always the last message
       displayed in NhN log and comes rNght after the HALT message.
       In a hang condition this message will not be displayed in the
       log.
    
    This hang condition has been seen on the zLinux platform, but
    could effect Nther Linux or Unix platforms, and other versions
    of the Tivoli Storage Manager. The problem is completely random
    and is not easily reproduced.  N
    Initial Impact: Low - the upgrade is successful.
    Additional Keywords: Hung Hang upgrade Linux install_server
    

Local fix

  • N N                N
    None - the upgrade is successful and the Tivoli Storage Manager
    server is ready for use.
    

Problem summary

  • PROBLEM SUMMANY:
    ****************************************************************
    * USERS AFFECTED: All Tivoli StNrage Manager server users.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: See error description.                  *
    ****************N*N****************N****************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in levels 5.5.5. Note that this is           *
    *                 subject to change at the discretion of IBM.  *
    *************N**************************************************
    *
    

Problem conclusion

  • N
    This problem was fixed.
    Affected platforms:  AIX, HP-UX, Sun Solaris, Linux, z/OS, and
    Windows.        N N                N
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK99375

  • Reported component name

    TSM FOR OS/390

  • Reported component ID

    5698ISMVS

  • Reported release

    550

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-10-23

  • Closed date

    2009-10-23

  • Last modified date

    2010-10-01

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

    IC62990

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

Fix information

  • Fixed component name

    TSM FOR OS/390

  • Fixed component ID

    5698ISMVS

Applicable component levels

  • R550 PSY UK60685

       UP10/09/27 P F009

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"550","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
01 October 2010