IV95024: DELETED INSTANCES RETURN IN BOOT SCRIPT AFTER UPGRADING AGENT

6.3.0.7-TIV-ITM_TEMA-IF0007

IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 1 (6.3.0.7-TIV-ITM-SP0001)

APAR status

• Closed as fixed if next.

Error description

• Upgrading a multi-instance agent which has previously deleted
  instances causes start/stop entries for the previously deleted
  instances to be added to the boot script
  (/etc/rc.itm# for UNIX, /etc/rc.d/init.d/ITMAgents# on Linux)
  by UpdateAutoRun.sh
  
  This can result in false "offline" managed system alerts for
  previously deleted instances.
  
  This issue impacts only UNIX and Linux environments, and can
  occur with any multi-instance agent, including but not
  limited to:
   Agentless agents - R2, R3, R4, R5, R6
   HMC agent - PH
   DB2 agent - UD
   Oracle Extended agent - RZ
   Log File agent - LO
  
  This issue impacts all versions of Common Installer component
  CI on all releases.
  
  This will happen whether install.sh was triggered by
  "tacmd updateAgent" or by "tacmd addSystem" or by a
  local interactive or silent install / upgrade of a
  multi-instance agent component.
  
  It will only occur when the "install.sh" is installing /
  updating
  the multi-instance agent component that the deleted instances
  were configured against.
  
  Uninstalling a multi-instance agent does not remove any entries
  from the config/ConfigInfo file, so re-installing the same
  multi-instance agent component will recreate references for the
  previously deleted instances for that same multi-insance agent
  component.
  
  Installing an OS agent or any non-instance agent or any agent
  except the specific multi-instance agent whose instances were
  previously deleted will NOT cause the deleted instances for the
  specific multi-instance agent to be recreated.
  
  RECREATE INSTRUCTIONS:
  tacmd createnode -h system1 ...
  tacmd addsystem -n system1:KUX -t lo -p INSTANCE=Robert ...
  tacmd addsystem -n system1:KUX -t lo -p INSTANCE=Charles ...
  UpdateAutoRun.sh
  (Notice entries for Robert and Charles in boot script)
  tacmd removesystem -m Robert:system1:LO
  (Cleanup config/.ConfigData/kloenv)
  UpdateAutoRun.sh
  (Notice entries for Charles only in boot script)
  tacmd updateagent -n system1:KUX -t lo
  UpdateAutoRun.sh
  (Notice entries for Robert and Charles in boot script)
  
  Additional Keywords:
  IV32626
  

Local fix

• (1) Stop everything on the agent endpoint
  (2) Confirm no orphaned entries in
   <CandleHome>/config/.ConfigData/RunInfo and RunInfo_Description
  files
  (3) Remove instance config / .cfg for deleted instances in
  <CandleHome>/config
  (4) Edit the k<pc>env file in <CandleHome>/config/.ConfigData
  and remove the instance references for deleted instances
  (5) Edit the ConfigInfo file in <CandleHome>/config/.ConfigData
  and
  remove references for the deleted instances
  (6) Remove <CandleHome>/CAP/pas.dat
  (7) Run <CandleHome>/UpdateAutoRun.sh
  (then check <CandleHome>/registry/AutoStart and review entries
  in boot
  scripts has removed stop/start entries for deleted instances)
  (8) Restart everything (all the agents) using boot script
  (9) Perform install / upgrade operation for multi-instance agent
  component
  

Problem summary

• The script UpdateAutoRun.sh has been changed to analyze each
  instance definition and clean up partially removed instances
  before generating the updated boot script.
  

Problem conclusion

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

Applicable component levels