IT34596: BACKUP HANGS, ERROR LOG FILLS WITH ANS0361I MUTEX LOCK FAILED: 6RELEASE MUTEX FAILED WAIT CONDITION FAILED

APAR status

• Closed as program error.

Error description

• Backup applications that use the IBM Spectrum Protect
  Application Programming Interface (API) can hang if the
  connection to the IBM Spectrum Protect Server is severed.
  The hang can occur only when client-side deduplication is used.
  
  When the hang occurs, the following messages occur repeatedly in
  the API error log (dsierror.log):
  
    ANS0361I DIAG: ..\..\common\winnt\psthread.cpp( 616):
     Mutex lock failed: 6.
    ANS0361I DIAG: ..\..\common\winnt\psthread.cpp( 713):
     Release mutex failed; reason 6.
    ANS0361I DIAG: ..\..\common\winnt\psthread.cpp( 822):
     Wait condition failed; Error unlocking mutex: -1
  
  The above example is from Windows, but the messages are similar
  for other platforms.
  
  This issue can affect any application that uses the IBM Spectrum
  Protect API, including Data Protection for *, Db2, and other
  3rd-party applications.
  
  Customer/Support Diagnostics:
  
  The backup process will be hung and will need to be killed.
  Error log may grow until disk space is exhausted.
  
  Spectrum Protect Versions Affected:
  IBM Spectrum Protect Backup-Archive Client for Windows
  versions 7.1.x and 8.1.x
  IBM Spectrum Protect Backup-Archive Client for UNIX and Linux
  versions 7.1.x and 8.1.x
  
  Initial Impact: Low
  
  Additional Keywords:
  TS004141482 mutex deduplication
  

Local fix

• Disable client side deduplication. Also limit the error log size
  to prevent exhausting disk space if you continue using client
  side deduplication.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect API versions 7.1 and 8.1 running on all *
  * platforms.                                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * see ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is projected *
  * to be fixed in level 8.1.12.                                 *
  * Note that this is subject to change at the discretion of     *
  * IBM.                                                         *
  *                                                              *
  ****************************************************************
  

Problem conclusion

• API will not hang anymore.
  

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:

Modules/Macros

• tsmapi
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels