IBM Support

IV31183: KCAWD RESTARTED WHEN CPUTHRESHOLD SET

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Please open an apar with the following severity and information:
    
    Severity:         2
    Approver:         MK
    Reported Release: 622 FP5
    Compid:           5724C04LN  Linux OS Agent
    Abstract:         kcawd restarted when cpuThreshold set
    Environment:      ITM 622
    
    Problem Description:  When the cpuThreshold value is specified
    in the kcawd_default.xml or kcawd.xml file for Watchdog, it can
    result in the Watchdoig process (kcawd) to be continually
    restarted (up to the maximum restarts for the day).   This is
    due to an incorrect calculation for the CPU percentage for the
    process when kcawd is first started.
    
    This problem can also result in the Process System CPU (Percent)
    and Process User CPU (Percent) values displayed on the Agents'
    Runtime Status workspace to be inaccurate or greater than 100%
    when an agent is first started.
    
    Local fix/workaround:  Stop the OS Agent, remove the
    <cpuThreshold> specification in the kcawd_default.xml or
    kcawd.xml file, then restart the OS Agent.
    
    Related Files and Output:  None.
    

Local fix

  • Local fix/workaround:  Stop the OS Agent, remove the
    <cpuThreshold>
    specification in the kcawd_default.xml or kcawd.xml file, then
    restart
    the OS Agent.
    

Problem summary

  • Watchdog process (kcawd) restarted when cpuThreshold set.
    
    When the cpuThreshold value is specified in the kca_default.xml
    or kca.xml file for Watchdog, it can result in the Watchdog
    process (kcawd) to be continually restarted (up to the maximum
    restarts for the day).  This is due to an incorrect calculation
    for the CPU percentage for the process when the process is first
    started.  This problem can also occur when other agents which
    are being monitored are started.
    
    This problem can also result in the Process System CPU (Percent)
    and Process User CPU (Percent) values displayed on the Agents'
    Runtime Status workspace to be inaccurate or greater than 100%
    when an agent is first started.
    

Problem conclusion

  • The code was changed to correctly calculate the CPU percentage
    when the kcawd process or agent is started.
    
    
    The fix for this APAR is contained in the following maintenance
    packages:
    
       | fix pack | 6.2.3-TIV-ITM-FP0003
    

Temporary fix

  • Stop the OS Agent, remove the <cpuThreshold> specification in
    the kca_default.xml or kca.xml file, then restart the OS Agent.
    

Comments

APAR Information

  • APAR number

    IV31183

  • Reported component name

    ITM AGENT LINUX

  • Reported component ID

    5724C04LN

  • Reported release

    622

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-31

  • Closed date

    2012-12-12

  • Last modified date

    2013-05-10

  • 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

    ITM AGENT LINUX

  • Fixed component ID

    5724C04LN

Applicable component levels

  • R622 PSY

       UP

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

Document Information

Modified date:
30 December 2022