VoyenceControl: When third-party agents are running on the server voyence service reports "Address already in use"
book
Article ID: 303552
calendar_today
Updated On:
Products
VMware
Issue/Introduction
Symptoms:
How do I change the default mutex seed port?
ERROR: Starting Device Server Service: Device Service is already started, stop the other process first before starting the services: Address already in use When third-party agents are running on the server voyence service reports "Address already in use"
When the voyence service is not running, one or more of ports 9991-9998 are in use.
Environment
VMware Smart Assurance - NCM
Cause
By default, the voyence service uses ports 9991-9998 for singleton mutex. Some third-party agents overlap on these ports, preventing the voyence service from starting.
Resolution
To allow the voyence service and the third-party agents to coexist, you can change the mutex seed port that the voyence service uses:
On the Application server, change to the voyence cgi-bin directory as follows:
cd $voyence_HOME/cgi-bin
Source the /etc/voyence.conf file:
source /etc/voyence.conf
Output the infrastructure database to a temp file:
./cflist.cgi > tmpfile
Open the file for editing and locate the end of the POP line for the device server you need to change the mutex seed port on.
Append the CM_MUTEXPORT variable to this line and set its value to a open seed port range (the below example uses seed port 10000, which provides the range 10001-10008).