search cancel

Client Automation - SD Job Containers remains in building or terminating state

book

Article ID: 214613

calendar_today

Updated On:

Products

CA Client Automation - IT Client Manager CA Client Automation - Software Delivery

Issue/Introduction

SD Job Containers remain in building state
and
SD Job Containers remain in terminating state
 

Cause

This could have multiple causes but one possible cause is that plugin "Notification Server (cfnotsrvd)" is not processing the CAM messages from its queue U-NS

This could be checked with this command :

camstat -l | findstr "U-NS Qlen ---"

 

Example :

In below example there are 22348 messages in queue for U-NS

 

Application           proto state  port  Qlen  m/sent  m/recv  retry  disc hold
---------------       ----- ----- ----- ----- ------- ------- ------ ----- ----
U-NS                    tcp   CON  4105 22348   34526     951      0     0   60
U-NSC                   tcp   CON  4105 0     567    1179      1    13   60

 

If the same command is executed 1 minute later, Qlen value is growing but value in m/sent is not changed

Application           proto state  port  Qlen  m/sent  m/recv  retry  disc hold
---------------       ----- ----- ----- ----- ------- ------- ------ ----- ----
U-NS                    tcp   CON  4105 22457   34526     951      0     0   60
U-NSC                   tcp   CON  4105 0     567    1179      1    13   60

 

Environment

Client Automation - All Versions

Resolution

"Notification Server (cfnotsrvd)" has a problem. It needs to be restarted and its queue U-NS emptied.
 
caf stop cfnotsrvd
camq -c U-NS
caf start