Deploying a OSIM job to some machines under a specific Boot Server starts correctly, but the progress of the job is not correctly displayed in DSM Explorer, it remains in Active state.
Client Automation 14.5 and above
In this particular scenario, the issue was present on a specific Boot Server and, when checking the logs of this SS, it’s seen that a lot of poll messages are being received from Agents:
|INFO | - Receive(): *** U-CSMSERVER: 475 bytes from $U-CSMAGENT@##.###.##.###***
|DETAIL | . <?xml version="1.0" encoding="UTF-8"?>
<message>
<head>
<type code="11">poll</type>
<sender type="agent" host="hostname” addr=“##.###.##.##” csmuuid="BB2D818F-4823-4B36-A833-E81EC62A71E9" hostuuid="4ADC7B5E-04DA-4175-846D-2DDAAC737FB8"/>
|INFO | - Receive(): *** U-CSMSERVER: 473 bytes from $U-CSMAGENT@##.###.##.###***
|DETAIL | . <?xml version="1.0" encoding="UTF-8"?>
<message>
<head>
<type code="11">poll</type>
<sender type="agent" host="hostname2” addr=“##.###.##.###” csmuuid="EE5EDE19-7383-417E-A23F-44DAEA83AE9E" hostuuid="D55DCAA6-2D1D-44F1-8429-A2EF79B2EC60"/>
|INFO | - Receive(): *** U-CSMSERVER: 475 bytes from $U-CSMAGENT@##.###.##.###***
|DETAIL | . <?xml version="1.0" encoding="UTF-8"?>
<message>
<head>
<type code="11">poll</type>
<sender type="agent" host="hostname3” addr=“##.###.##.###” csmuuid="E71CDAD2-C667-43F0-AECA-409775218059" hostuuid="85698DD8-3228-4FA2-8A18-162E8547D431"/>
In 5 minutes, 211 poll messages were received.
Checking few Agents logs, its seen that csmpollinterval was not correctly set in all:
Agent1 (Polling Disabled):
|DETAIL | API call: GetParameterValueInt(itrm/agent/cc, csmpollinterval, <piParameterValue>, NULL)
|DETAIL | GetParameterValueInt(itrm/agent/cc, csmpollinterval, ..., NULL) successfully completed. Parameter value: 0
Agent2 (Poll every 300 seconds = 5 minutes):
|DETAIL | API call: GetParameterValueInt(itrm/agent/cc, csmpollinterval, <piParameterValue>, NULL)
|DETAIL | GetParameterValueInt(itrm/agent/cc, csmpollinterval, ..., NULL) successfully completed. Parameter value: 300
Based on this, there is a configuration policy applied to some Agents which set the polling every 5 minutes, causing that the Scalability Server os overflowed by messages, causing that OSIM jobs are not being updated correctly due to this long queue.
The suggestion is to set the policy “Poll Interval” to 0 and apply it to all Agents. The policy can be found under:
DSM -> Agent -> Common Configuration