IJ08784: TSA DAEMON CRASHES.

4.1.1-TIV-SAMP-Linux64-FP0001
4.1.1-TIV-SAMP-AIX-FP0001
4.1.0.4-TIV-ITSAMP-AIX-IJ08784
4.1.0.4-TIV-ITSAMP-LINUX64-IJ08784
4.1.0.4-TIV-ITSAMP-LINUX-IJ08784
4.1.0.4-TIV-ITSAMP-IJ08784
4.1.0-TIV-SAMP-AIX-FP0005
4.1.0-TIV-SAMP-Linux-FP0005
4.1.0-TIV-SAMP-Linux64-FP0005
4.1.0-TIV-SAMP-AIX-FP0006
4.1.0-TIV-SAMP-Linux-FP0006
4.1.0-TIV-SAMP-Linux64-FP0006
4.1.0-TIV-SAMP-AIX-FP0007
4.1.0-TIV-SAMP-Linux64-FP0007
SAMP4107_Verification_Signatures
4.1.1-TIV-SAMP-AIX-FP0000
4.1.1-TIV-SAMP-Linux64-FP0000

APAR status

• Closed as program error.

Error description

• TSA daemon crash in the following two parts:
  
  i) Crash in the memcpy() of the /lib64/libc.so.6
  
  ii) Crash in the mainInitThread() of the GblResRMDaemon.C
  

Local fix

• Change the value of #tasks to "infinity"
  % systemctl set-property srcmstr.service TasksMax=infinity
  % systemctl show srcmstr.service
  .
  Or, here is the alternative way:
  Change the value of
  /sys/fs/cgroup/pids/system.slice/srcmstr.service/pids.max from
  512 to "max" to prevent exception from happening which will
  cause the issue.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Tivoli System Automation for Multiplatforms
  * (SA MP) 4.1 users
  ****************************************************************
  * PROBLEM DESCRIPTION:
  
  * lssam hangs after restarting domain.
  
  * RecoveryRMd was getting restarted, as it was not getting any
    response from GblResRMd which got crashed while printing a
    log when an exception is caught.
  
  * Failed with following error on the terminal:-
    "2610-412 A Resource Manager terminated while attempting
    to enumerate resources for this command."
    "2610-408 Resource selection could not be performed."
    "An unexpected RMC error occurred.The RMC return code was 1."
  
  ****************************************************************
  * RECOMMENDATION:
  ****************************************************************
  

Problem conclusion

• * Updated the code in GblResRMd to handle the correct printing
    of the message when an exception is caught.
  
  * RecoveryRMd should not crash for the above-mentioned reason as
    the GblResRMd can now handle exception while creating multiple
    threads and will print the correct error being caught.
  
   Provided the ifix - 4.1.0.4-TIV-ITSAMP-IJ08784
  
   The official fix for this problem will be included in fix pack
   5 of Tivoli System Automation for Multiplatforms 4.1
   | 4.1.0-TIV-ITSAMP-FP0005 |
   .
   Additional Search Keywords
   .
  

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

  SA MULTIPLATFOR

• Fixed component ID

  5724M0000

Applicable component levels