Client Automation Domain Manager ccsmact Performance Degradation from Excessive BootServer Hello Messages
search cancel

Client Automation Domain Manager ccsmact Performance Degradation from Excessive BootServer Hello Messages

book

Article ID: 372485

calendar_today

Updated On:

Products

CA Client Automation - IT Client Manager CA Client Automation

Issue/Introduction

The process ccsmactd.exe can consume memory exceeding 1 GB leading to process crashes and requiring a full server restart.
Also performance of some tasks like activation/processing of configuration jobs or activation/processing of OSIM jobsccsmactd.exe are affected. Some OSIM or configuration policy jobs remains in waiting status and are not updated.

The symptoms are : 

  • High memory usage of process ccsmactd.exe (> 1 GB)
  • Slow deployment of OSIM or Configuration policy jobs. They remain in status activated or waiting

Environment

Client Automation 14.5, 14.6
Domain Manager on Windows. Lot of scalability servers attached to the Domain Manager (several hundred).

Cause

By default Boot server on the scalability servers are sending a Boot Server Hello message to Domain Manager (plugin "Configuration and State Management agent controller" ccsmact) every 20 minutes;

Example in TRC_CSMACT*.log on Domain Manager :

200624-07:54:53.0967205L|011232|00002be8|ccsmact   |csmtrace        |message.cpp         |000093|INFO   | - Receive(): *** Message from $U-CSMSERVER@<IP_ADDRESS> ***
200624-07:54:53.0973894L|011232|00002be8|ccsmact   |csmtrace        |message.cpp         |000119|INFO   | -
<?xml version="1.0" encoding="UTF-8"?>
<message>
<head>
<type code="2">statereport</type>
<sender type="agent" host="<agent_name>" addr="<agent_addr>" csmuuid="<csmuuid>" hostuuid="<hostuuid>"/>
...
</head>
<body>
<state interval="7200" name="bootserver hello" rc="1 Report">
<resource type="bsinfo">
<status code="1">boot server presence reported successfully</status>

If there are a lot of Scalability servers, ccsmact plugin could receive a lot of Boot Server Hello messages per hour. This could affect the performance of other tasks like activation/processing of configuration jobs or activation/processing of OSIM jobsccsmactd.exe could take a lot of CPU and have a high memory usage.

Example : If there are 1000 scalability servers, it is 3000 (1000*3) "Bootserver hello" messages sent per hourHow to decrease the frequency of BootServer hello message sending ?

Resolution

On a Scalability Server, BootServer Hello frequency value is stored in the file C:\Program Files (x86)\CA\DSM\Agent\CCSM\bsinfo.xml (or /opt/CA/DSM/Agent/CCSM/bsinfo.xml on Linux).
By default its value is 1200 (=20 minutes)

As workaround it is possible to change the "BootServer Hello" frequency from 1200 to 7200 minutes by editing the file bsinfo.xml on the scalability servers.

This could be done using the attached Bootserver.7z file (see below). This is a SD Package "BootServer Hello Message Frequency 1.0" which could be used to update the frequency in bsinfo.xml to 7200 (=2 hours)

This package could be sent on all Scalability Servers (on Windows or Linux)


With this change all scalability servers will send the "boot server Hello" every 2 hours instead every 20 minutes.

This package contains the procedure "Set Frequency" with 7200 as first parameter. If needed, the procedure could be updated (or a new procedure created) to specify another value of Bootserver hello message frequency :

 

This job generates a log under C:\Program Files (x86)\CA\DSM\logs\bootserver.log (or /opt/CA/DSM/logs/bootserver.log) and also a SD Job output

Additional Information

See also this article ccsmact performance problem - all connections closed for another performance problem with ccsmact.exe process.

Attachments

Bootserver.7z get_app