IC65434: SERVER HALT COMMAND CAN TAKE A LONG TIME TO COMPLETE, CAN APPEAR TO BE HUNG AND CAN USE A LOT OF CPU.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A Tivoli Storage Manager server halt command can take a long
    time to complete, can use a lot of cpu and will appear to be
    hung.
    
    Customer/L2 Diagnostics:
    
    Forcing a core on the dsmserv process and analysing the  core
    file, we can see from the stack trace:
    
    #0  0x000000357960ab99 in pthread_cond_wait@@GLIBC_2.3.2 ()
       from /lib64/libpthread.so.0
    #1  0x0000000000c610b2 in pkWaitConditionTracked (condP=<value
    optimized out>,
        mutexP=<value optimized out>, abstime=0, file=0xdb2892
    "dbiinit.c",
        line=1288) at pkmon.c:873
    #2  0x000000000070a8de in dbiHalt (bypassADMCheck=False,
        bypassActLogShutdown=<value optimized out>,
    quiesceOnly=False,
        signalHaltToOutputSvcs=True) at dbiinit.c:1288
    #3  0x0000000000520128 in admStartServer
    (startUpMode=NoConsoleStart,
        upgradeDB=False) at admstart.c:1456
    #4  0x000000000046c162 in main (argCount=6,
    argVector=0x7fffb390aa18)
        at dsmserv.c:123
    
    The main thread is waiting on a condition variable in dbiHalt()
    in dbiinit.c
    
    This can be caused by runstats running on a large table.
    
    
    Tivoli Storage Manager Versions Affected: 6.1 All
    Unix/Linux/Windows
    
    Initial Impact: Low
    
    Additional Keywords: halt cpu hung hang runstats
    

Local fix

  • Allow more time for halt to complete
    
    or
    
    Use the option
    RUNSTATSCHKINTERVAL <interval_between_checks_in_mins>
    in dsmserv.opt to increase the interval between runstats
    to lessen the chance of runstats running at time of halt.
    The value is in minutes, and can be between 10 and 1440
    (the default is 10).
    

Problem summary

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

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IC65434

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    61L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-01-06

  • Closed date

    2010-02-02

  • Last modified date

    2010-02-02

  • 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

    TSM SERVER

  • Fixed component ID

    5698ISMSV

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61L PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Storage Manager

Software version:

61L

Reference #:

IC65434

Modified date:

2010-02-02

Translate my page

Machine Translation

Content navigation