IC94419: SERVER CRASH WHEN PUSHING ALERT TO OPERATIONS CENTER

IBM Tivoli Storage Manager V6.3 Fix Pack 5 (6.3.5.000) Server Downloads

APAR status

• Closed as program error.

Error description

• The Tivoli Storage Manager hub server can crash during
  alert update processing and the spoke is sending its
    alerts to the hub.  During the alert monitor update
    interval the server is updating the status of the alerts
    based on their active, inactive, and closed duration
    criteria and pushing the update to the Operations Center.
    There is a timing issue in which the hub server is pushing
    the alert to the Operation Center and also deleting and
    inserting updated information about the alert from the
    spoke at the same time. The server can crash if it is
    trying to retrieve information about the alert but it is
    deleted or in the window that it is deleted.
  
  Tivoli Storage Manager Versions Affected:
    6.3.4
  Customer/L2 Diagnostics (If Applicable)
    The call stack for the crash:
  
    __memcpy_ssse3 () from /lib64/libc.so.6
    BuildAlertInfo ()
    DoQueAlertUpd ()
    SetAlertStatus ()
    AlertMonitorThread ()
    StartThread ()
    start_thread () from /lib64/libpthread.so.0
    clone () from /lib64/libc.so.6
  Initial Impact:
    Low
  Additional Keywords:
    CORE CRASH Ops Center
  

Local fix

• 1) Use the SET ALERTUPDATEINTERVAL to adjust the interval
       rate to a value that is not a multiple of 10 since the
       spoke server sends updates approximately every 10 minutes.
    2) Another option would be to use the SET ALERTMONITOR OFF
       command to turn off alert monitoring.
  

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.3.4.200 and 6.3.5. Note          *
  *                 that this is subject to change at the        *
  *                 discretion of IBM.                           *
  ****************************************************************
  *
  

Problem conclusion

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

Temporary fix

Comments

APAR Information

• 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

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP

• R63Z PSY

     UP