NCM Jobs and tasks are stuck in a "queued for execution" state

Products

• VMware Smart Assurance

Issue/Introduction

NCM Jobs and tasks are stuck in "queued for execution" state, and includes:

"Pull after cut-thru"-type jobs are stuck in "queued for execution" state.
"Pull after Syslog"-type jobs are stuck in "queued for execution" state.

Environment

NCM 10.1.X

Cause

The task numbers for cmd files created by the Healthcheck service are shorter than regular pull/push task numbers. 

When unlinking the tasks for the Healthcheck it is possible to match a portion of other pull/push task numbers, accidentally removing those task files before they are started.  Those push/pull tasks are abandoned.

Resolution

The Healthcheck PERL script requires a slight modification to give it's task files unique task numbers:

• On the Application server, change to the Voyence Healthcheck directory as follows:
  

  cd $Voyence_HOME/Healthcheck
  

   
• Open the healthcheck.pl file for editing and locate the following line on or about line 97:
  
  

  $ID=time;
  

  
   
• Modify the line to read as follows:
  
  

  $ID="01".time."0000";
  

  
   
• Save your changes and close the file.
  
   
• Restart the Healthcheck service:
  
  

  /etc/init.d/Healthcheck restart