IV97694: ITMAGENTS* DOES NOT START COMPONENTS AT RE-BOOT ON SLES 12

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

APAR status

• Closed as program error.

Error description

• SLES 12 sys5 to systemd conversion does not support the sys5
  Required-Start: $all dependency.
  Changing "$all" to "$remote_fs $network $named $portmap" allows
  the ITMAgents sys5 boot scripts to be executed under systemd
  boot processing, instead of being rejected.
  
  RECREATE INSTRUCTIONS:
  Install a Linux OS agent from any 6.30.XX.00 ITM base agents
  media on a SLES 12 system.
  Configure the OS agent.
  Run UpdateAutoRun.sh as root if the OS agent configuration was
  not run as root.
  Start the OS agent.
  Verify that it is running.
  Re-boot the system.
  Verify that the OS agent is not running after the boot
  completes.
  Run the command: journalctl -u ITMAgents*
  Notice messages like the following:
  ITMAgents1.service - LSB: IBM Tivoli Monitoring
     Loaded: loaded (/etc/init.d/ITMAgents1; bad; vendor preset:
                    disabled)
     Active:   inactive (dead)
       Docs:   man:systemd-sysv-generator(8)
  
  Jun 09 13:27:25 xtsappx1 systemd[1]: ITMAgents1.service: Job
  ITMAgents1. service/start deleted to break ordering cycle
  starting with multi-user.
  target/start
  

Local fix

Problem summary

• /etc/init.d/ITMAgents* boot script does not start ITM components
  at re-boot for SLES 12 and above and also for RHEL 7.3 and
  above.  SLES12 and above and RHEL 7.x and above, have changed
  boot processing from init.d to systemd.  systemd processing of
  init.d boot scripts does not properly handle "Required-Start:
  $all"
  

Problem conclusion

• The script UpdateAutoRun.sh has been changed as follows:
  On Linux systems that are systemd enabled, the script will
  generate systemd service and target files instead of the init.d
  boot file.  On Linux systems that are not systemd enabled, and
  on AIX, HP-UX and Solaris systems, there is no change to the
  boot script that is generated.
  
  Additional Technical Info:
  For the purpose of this explanation, the environment variable
  NUM is set to the content of the $CANDLEHOME/registry/AutoStart
  file.
  
  NUM=$(cat $CANDLHOME/registry/AutoStart)
  
  1) The new ITMAgents${NUM} systemd service and target files are
     generated without regard to the existing init.d
     ITMAgents${NUM} boot file.  This means that commented out
     start or stop lines in the existing init.d boot file are not
     represented in the systemd
     ITMAgents${NUM}\.<PROD>.<INST>.service files. You will need
     to modify the kcirunas.cfg file as previously documented
     here:
  
  https://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm
  .itm.doc_6.3/install/newauto.htm
  
     Read the sections related to the <autoStart> tab in
     particular.
  
     An additional tool to make it easier to manage the
     kcirunas.cfg and <HOST>_kdyrunas.cfg files is available as an
     attachment to the following Technote:
  
     https://www-01.ibm.com/support/docview.wss?uid=swg21271332
  
     Download and expand the IZ52380.* attachemnts for the tools
     and documentation.
  
  2) Although not explicitly documented, it is common practice to
     use the ITMAgents${NUM} init.d boot script to manually stop
     and start the same set of agents and agent instances using
     the same IDs as would be started (or stopped) at boot time.
     There is no single file in the set of systemd service and
     target files that allows the same processing.  The
     ITMAgents${NUM}.target file can not be used for this purpose.
     The following commands will not reliably restart the agents
     specified in ITMAgents${NUM}*.service files if any of the
     agents have been stopped and/or started manually outside of
     systemd:
  
  
     systemctl stop ITMAgents${NUM}\.\*.service
     systemctl start ITMAgents${NUM}\.\*.service
  
  3) Some additional useful systemctl commands are:
  
     systemctl list-units ITMAgents${NUM}\.\* -all
     systemctl list-unit-files ITMAgents${NUM}\.\* -all
     systemctl status ITMAgents${NUM}\.\*
  
  4) To TEMPORARILY prevent an agent or agent instance from
     starting at reboot, you can disable the service file.
  
     For a non-instance agent:
  
        systemctl disable ITMAgents${NUM}\.<PROD>.service
  
     For an instance agent (or TEMS):
  
         systemctl disable ITMAgents${NUM}\.<PROD>.<INST>.service
  
     where: <PROD> is the two character component IDs
            <INST> is the instance name name
  
     When UpdateAutoRun.sh is executed again directly (or
     indirectly by install.sh or itmcmd config) the unit status
     will be reset.
  
  5) To TEMPORARILY allow a previously disabled agent or agent
     instance from starting at reboot, you can enable the service
     file.
  
     For a non-instance agent:
  
       systemctl enable ITMAgents${NUM}\.<PROD>.service
  
     For an instance agent (or TEMS):
  
       systemctl enable ITMAgents${NUM}\.<PROD>.<INST>.service
  
     where: <PROD> is the two character component IDs
            <INST> is the instance name name
  
     When UpdateAutoRun.sh is executed again directly (or
     indirectly by install.sh or itmcmd config) the unit status
     will be reset.
  
  6) When uninstalling products from an installation with the new
     ITMAgents${NUM} systemd service and target files, you may see
     messages similar to the following:
  
  rm '/etc/systemd/system/multi-user.target.wants/ITMAgents1....
  
  
  -or-
  
  Removed symlink /etc/systemd/system/multi-user.target.wants/IT..
  
  
  These messages are expected and can safely be ignored.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | service pack | 6.3.0.7-TIV-ITM-SP0001
  

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

  OMEG DIST INSTA

• Fixed component ID

  5608A41CI

Applicable component levels