IJ34239: AGENT GETS RANDOMLY HIGH CPU USAGE WHEN USING THE SCRIPTING FEATURE

IBM Tivoli Monitoring 6.3.0 Fix Pack 7 Service Pack 9 (6.3.0.7-TIV-ITM-SP0009)

APAR status

• Closed as program error.

Error description

• Approver:  MK
  Reported Release: 630 FP7
  Environment:  Across versions
  
  On Windows when using the OS Agent Scripting feature, sometimes
  the agent will have high CPU usage.
  

Local fix

• Workaround:
  Set the environment variable KNT_FCP_ENABLE_CPCI_CHECK_THREAD to
  false in the KNTENV file:
  KNT_FCP_ENABLE_CPCI_CHECK_THREAD=false
  
  This turns off an extra check done in the code so the code that
  is looping does not get called.
  
  Related Files and Output: In the agent RAS1 log file,
  <hostname>_nt_kntcma_<timestamp>-0<n>.log, the log will be
  filled with the message:
  
  (5F315837.0C21-3144:factorycustomprovidertemplate.cpp,3023,"fac
  toryProviderCPCICheckThread")WARNING: pthread_cond_wait failed w
  error). Now: '1627431115', timing out at: '1627430877' (-1 means
  no timeout)
  

Problem summary

• When using the OS Agent Scripting feature, sometimes the agent
  will have high CPU usage.
  
  
  When using the OS Agent Scripting feature, sometimes the agent
  will have high CPU usage due to an unexpected return code from
  an API call.  The problem was reported on the Windows operating
  system.
  

Problem conclusion

• The Windows pthread_cond_wait API call sometimes returns an
  unexpected return code which causes in the agent code to loop
  resulting in high CPU.  The code has been updated to better
  handle the unexpected return code.  The problem was reported on
  Windows, but the improved error handling was done for Windows,
  UNIX, and Linux OS Agents.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
     | service pack | 6.3.0.7-TIV-ITM-SP0009
  

Temporary fix

• Set the environment variable KNT_FCP_ENABLE_CPCI_CHECK_THREAD to
   false in the KNTENV file:
  KNT_FCP_ENABLE_CPCI_CHECK_THREAD=false
  
  or use the tacmd setagentconnection command to set the variable
  remotely and restart the agent, for example:
    tacmd setagentconnection -t nt -e
  KNT_FCP_ENABLE_CPCI_CHECK_THREAD=false -n <Primary:system:NT>
  this will add the environment variable to the kntcma.ini file.
  
  This turns off an extra check done in the code so the code that
  is looping does not get called.
  

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

  ITM AGENT WINDO

• Fixed component ID

  5724C040W

Applicable component levels

• R630 PSY

     UP