Identifing and killing the Process ID (PID) of process preventing vcmaster service restart

Products

• VMware Smart Assurance

Issue/Introduction

• How to identify and kill the Process ID (PID) of the process that is preventing the Smarts NCM vcmaster service restart?
• Smarts NCM is not coming up after vcmaster restart because process is running.
• Smarts NCM vcmaster service restart fails because process is running.

Message similar to the following is seen when trying to restart the Smarts NCM vcmaster service:

[root@<HOSTNAME> conf]# service voyence restart
Stopping Device Server Service: [ OK ]
Starting Device Server Service: Device Service is already started, stop the other process first before starting the services: Address already in use
[FAILED]

 

Environment

NCM - 10.1.x

Cause

Restarting the Smarts NCM vcmaster can sometimes fail to restart the other Smarts NCM services because a few processes are running in backend. When this happens, a message similar to the following will be seen:

[root@<HOSTNAME> conf]# service voyence restart
Stopping Device Server Service: [ OK ]
Starting Device Server Service: Device Service is already started, stop the other process first before starting the services: Address already in use
[FAILED]

Resolution

1. Check the processes that are running using the following commands:

• netstat -anp | grep commmgrd | grep LISTEN
• netstat -anp | grep autodiscd | grep LISTEN
• netstat -anp | grep syssyncd | grep LISTEN
• netstat -anp | grep evdispatchd | grep LISTEN
• netstat -anp | grep cfgmgrd | grep LISTEN
• netstat -anp | grep voyenced | grep LISTEN

2. Note the PID of any running processes from Step 1, and kill those processes using the following command:

• kill -9 <PID>

3. Restart the vcmaster service as systemctl start vcmaster in case of NCM 10.1.8 and above or use service vcmaster start.

Additional Information

The following three processes should not be running and their associated ports should not be used by any other processes:

ps -elf | grep commmgrd
ps -elf | grep autodiscd
ps -elf | grep syssyncd

If any other processes are using these ports, find the associated processes using the following command:

netstat -anp | grep <PORT>

Kill any process has been found to be using the specified ports. Once all processes have been stopped, you can start the service.