IBM Support

IJ26471: SYSTEMCTL AND ITM RUNINFO INCONSISTENCIES CAUSE SYSTEMCTL STOP TO FAIL AT SHUTDOWN

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When an ITM agent is started by systemctl and then stopped and
    started by itmcmd directly, the systemctl status and the ITM
    RunInfo (cinfo -r) status become out of sync and systemctl is
    no longer able to stop the agent at system shutdown.
    This can
    lead to incorrect information remaining in the ITM RunInfo file
    which can cause a problem when systemctl attempts to start the
    agent at system startup.
    
    RECREATE INSTRUCTIONS:
    These recreate
    steps are Linux (RedHat 7 and above, Suse 12 and above)
    specific.
    1) Install the OS agent from the 063000700 media.
    2)
    Configure the OS agent.
    3) Start the OS agent.
    4) Stop the OS
    agent.
    5) Apply 6.3.0.7-TIV-ITM-SP0003
    6) Run
    UpdateAutoRun.sh
    7) Start the OS agent using systemctl
    8) Run
    systemctl status and cinfo -r
     Notice that it started
    correctly.
    9) Stop the OS agent using systemctl
    10) Run
    systemctl status and cinfo -r
     Notice that it stopped
    correctly.
    11) Start the OS agent using systemctl
    12) Run
    systemctl status and cinfo -r
     Notice that it started
    correctly.
    13) Stop the OS agent using itmcmd directly
    14) Run
    systemctl status and cinfo -r
     Notice that it stopped, however
    systemctl shows the agent status as failed.
    15) Start the OS
    agent using itmcmd directly
    16) Run systemctl status and cinfo
    -r
     Notice that it started, however systemctl shows the agent
    status as failed.
    17) Stop the OS agent using systemctl
    18) Run
    systemctl status and cinfo -r
     ERROR: Notice that it did not
    stop and systemctl shows the agent status as failed.
    

Local fix

Problem summary

  • The systemctl status and ITM RunInfo inconsistencies cause
    systemctl stop to fail at shutdown
    
    
    When an ITM agent is started by systemctl and then stopped and
    started by itmcmd directly, the systemctl status and the ITM
    RunInfo (cinfo -r) status become out of sync and systemctl is no
    longer able to stop the agent at system shutdown.
    This can lead to incorrect information remaining in the ITM
    RunInfo file which can cause a problem when systemctl attempts
    to start the agent at system startup.
    

Problem conclusion

  • The script UpdateAutoRun.sh has been changed to fix the problem.
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
    | Service Pack | 6.3.0.7-TIV-ITM-SP0007
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ26471

  • Reported component name

    OMEG DIST INSTA

  • Reported component ID

    5608A41CI

  • Reported release

    630

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-07-23

  • Closed date

    2021-04-07

  • Last modified date

    2021-04-07

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"630","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
08 March 2023