IZ58939: ssmagent.bin receives signal 15 (TERM) and restarts unexpectedly on Solaris 10

IBM Tivoli 4.0.0-TIV-SSM-FP0010
IBM Tivoli 4.0.0-TIV-SSM-FP0011
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 12 README 4.0.0-TIV-SSM-FP0012
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 13 README 4.0.0-TIV-SSM-FP0013
IBM Netcool System Service Monitor SSM 4.0 Fix Pack 14 README 4.0.0-TIV-SSM-FP0014
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.14-TIV-SSM-IF0001
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 2 README 4.0.0.14-TIV-SSM-IF0002
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 3 README 4.0.0.14-TIV-SSM-IF0003
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 4 README 4.0.0.14-TIV-SSM-IF0004
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 5 README 4.0.0.14-TIV-SSM-IF0005
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 6 README 4.0.0.14-TIV-SSM-IF0006
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 7 README 4.0.0.14-TIV-SSM-IF0007
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 8 README 4.0.0.14-TIV-SSM-IF0008
IBM Netcool System Service Monitor SSM 4.0 Interim Fix 1 README 4.0.0.15-TIV-SSM-IF0001

APAR status

• Closed as program error.

Error description

• This is a problem with the Solaris 10 service management
  facility (smf). If it detects a child process of ssmagent.bin
  has been terminated (SIGTERM, SIGHUP etc), then it will stop
  andrestart the agent using init.ssmagent.
  
   The problem is that child processes being terminated is not
  uncommon. It happens every time the lotus subagent is unloaded,
  and can even be reproduced with:
  
  $ svcadm enable ssmagent
  $ ssmcons
  Agent> snmp set $psExecute.0 s "/bin/sleep 9999"
  $ kill <PID of /bin/sleep>
  
  The problem does not occur however if a child process exits
  gracefully.
  

Local fix

• A workaround/fix is:
  $ svcadm disable ssmagent
  $ svccfg -s ssmagent addpg startd framework
  $ svccfg -s ssmagent setprop startd/ignore_error = astring:
  signal
  $ svcadm refresh ssmagent
  $ svcadm enable ssmagent
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of SSM 4.0 on Solaris 10
  ****************************************************************
  PROBLEM DESCRIPTION:
  ssmagent.bin receives signal 15 (TERM) and restarts unexpectedly
  on Solaris 10
  ****************************************************************
  RECOMMENDATION:
  Upgrade to Fix Pack 9 for SSM 4.0.
  ****************************************************************
  

Problem conclusion

• Modified the ssmagent service configuration to ignore signals
  received by SSM child processes. These changes will be undone
  when the patch is uninstalled (or when the final version of
  component svccfg is removed in patchman).
  
  The fix for this APAR is contained in the following maintenance
  packages:
  | fix pack | 4.0.0-TIV-SSM-FP0009
  

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

  NETCOOL SYS SVC

• Fixed component ID

  5724P4300

Applicable component levels

• R400 PSN

     UP