Operational Defect Database
BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 358311
VoyenceControl: Unable to start voyence service; Receive message "Device Server Service is already running"
Last update date:
3/22/2024
Affected products:
Smart Assurance - NCM
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Unable to start VoyenceControl voyence service Receive the following error when trying to start VoyenceControl voyence service: Device Server Service is already running... [FAILED] After stopping VoyenceControl voyence service, status still shows as running
Cause
One or more of the child daemon processes under the voyence service is not stopping.
Resolution
To resolve this issue, you must determine which child daemon processes under the voyence service are still running, and manually stop them. This is done as follows: Run ps afx on the server and look for the following process names: autodiscd cfgmgrd commmgrd evdispatchd syssyncd zebedee For each one found, note its Process ID, or pid, and kill it (the pid is found in the first column of the command output, see Notes): kill -9 pid If you find multiple processes, you can append them to the command: kill -9 pid [pid...] Restart the voyence service (it is normal for it to report failure when stopping): /etc/init.d/voyence restart
Related Information
Example ps afx output snippet from a healthy Combination Server: 16085 ? S 0:00 /opt/voyence/bin/voyenced start16086 ? S 0:00 \_ zebedee -s -f /opt/voyence/conf/appServer.zbd16087 ? S<l 1:37 \_ syssyncd master16089 ? S 0:00 \_ cfgmgrd master16090 ? S 0:00 /opt/voyence/bin/voyenced start16091 ? S 3:24 \_ evdispatchd none16092 ? S<l 3:27 \_ syssyncd server16093 ? Sl 0:27 \_ autodiscd -r16094 ? Sl 6:55 \_ commmgrd -r16098 ? S 0:00 \_ zebedee -s -f /opt/voyence/conf/devServer.zbd
