IZ75702: SGID BIT ON KUXAGENT CAUSES ORACLE AGENT FAILURE

IBM Tivoli Monitoring 6.2.2 Fix Pack 8 (6.2.2-TIV-ITM-FP0008)
IBM Tivoli Monitoring 6.2.2 Fix Pack 9 (6.2.2-TIV-ITM-FP0009)
IBM Tivoli Monitoring 6.2.2 Fix Pack 6 (6.2.2-TIV-ITM-FP0006)

APAR status

• Closed as program error.

Error description

• ********************** START OF APAR OPEN TEMPLATE
  *********************
  
  * Please open an apar with the following severity and
  information:     *
  *
  *
  APAR Type:            Field
  Approver Initials:    AS
  Severity:             2
  Reported Release:     621
  Compid:               5608A41CI Distributed Installer
  ABSTRACT:             SGID bit on kuxagent causes oracle agent
  failure
  PROBLEM DESCRIPTION:
  
  After upgrading the ITM Infrastructure beyond ITM 6.21 IF04,
  SetPerm
  sets the SGID bit for the kuxagent. With the OS agent running as
  root, using Portal client or tacmd CLI to start the Oracle
  monitoring
  agent causes the Oracle monitoring agent to fail searching for
  libcIntsh.so.10.0.2.0
  
  
  RECREATE INSTRUCTIONS:
  
  Install OS agent, TEMS, TEPS and app support from ITM 6.21 GA as
  root
  Install Oracle agent and app support
  Configure installed components
  Run "chgrp -R itmuser $CANDLEHOME"
  Run "SetPerm -a"
  Start OS agent, TEMS, TEPS
  Start Oracle monitoring agent
  Verify that all agents report successfully in Tep
  Upgrade OS agent to ITM 6.21 FP2
  Stop the Oracle agent.
  Start the Oracle agent using the Tep
  In the Tep, select an item in the Oracle agent work-space
  <ERROR> Notice that the agent terminates.  The Oracle agent
  collector log will show "cannot find libcIntsh.so.10.0.2.0"
  six times, and then the agent gives up, and shuts down.
  
  
  LOCAL FIX:
  
  Change the permission for kuxagent from 6750 to 4750
  
  
  MDVREGR caused by APAR IZ35328 in 6.2.0-TIV-ITM-FP0003
  
  *********************** END OF APAR OPEN TEMPLATE
  **********************
  

Local fix

• Change the permission for kuxagent from 6750 to 4750
  

Problem summary

• Upgrading the UNIX OS agent as root causes SetPerm to run
  automatically at the end of the installation. Running SetPerm
  causes the GID bit to be set for the UNIX OS Agent which in turn
  causes the remote command handler to run as the specific group.
  This causes an Oracle Agent started remotely to fail soon after
  starting.
  

Problem conclusion

• Fix SetPerm so that it does not set the GID bit for kuxagent.
  
  The fix for this APAR is included in the following maintenance
  vehicle:
      | fix pack | 6.2.1-TIV-ITM-FP0003
  

Temporary fix

• After SetPerm is run and exits, run the following command on the
  command line:
  chmod 4755 $CANDLEHOME/*/bin/kuxagent
  

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

  OMEG DIST INSTA

• Fixed component ID

  5608A41CI

Applicable component levels

• R621 PSY

     UP