Smarts NCM: commmgrd process keeps restarting on Smarts NCM Device server after the server is re-deployed
search cancel

Smarts NCM: commmgrd process keeps restarting on Smarts NCM Device server after the server is re-deployed

book

Article ID: 303542

calendar_today

Updated On:

Products

VMware

Issue/Introduction

Symptoms:




After re-deployment of Smarts Network Configuration Manager (Smarts NCM) device server, the commgrd process keeps restarting
After redeployment of a Smarts NCM Device server, the commmgrd process keeps restarting after bringing up services

commmgrd Process ID (PID)  keeps changing on Smarts NCM device server as seen in the commmgr.log

Smarts NCM Jobs are not resumed or are not being processed properly after a Smarts NCM device server redeployment

Environment

VMware Smart Assurance - NCM

Cause

After redeployment of the Smarts NCM device server, the commmgrd service is unable to properly process acmd files. This is because when a Smarts NCM device server restarts, it looks for pending previous jobs in acmd files and starts executing them, and the commmgrd service is unable to process one or more of these files.

Resolution

If you encounter this issue, do the following:

  1. Delete all acmd files found in the following folder on the Smarts NCM Application server:

    VOYENCE_HOME/data/appserver/pops/pop1000/syssync/commmgr/toMaster/deviceupdate

     
  2. Install/start the re-deployed Smarts NCM Device server.
  3. Once communication between the Smarts NCM Application server and Device server is verified and the all processes on the Device server are stable with no constant restarting processes, jobs previously queued may need to be cancelled and run manually at a later time.