Skip to main content

vpxd service fails to start with error : Diagnostic server root (/etc/vmware-vpx/docRoot/diagnostics) does not exist!

 

Symptoms
  • Unable to start services on vCenter.

vpxd.log :

020-05-27T21:53:51.239-06:00 info vpxd[04347] [Originator@6876 sub=Locale] LoadResources path (/etc/vmware-vpx/locale/) locale (fr) removeable (false) resMap (00007f673c036a20) extKeys (0000000000000000)
2020-05-27T21:53:51.296-06:00 info vpxd[04347] [Originator@6876 sub=Locale] LoadResources path (/etc/vmware-vpx/extensions/VirtualCenter/locale/) locale (fr) removeable (false) resMap (00007f673c036a20) extKeys (0000000000000000)
2020-05-27T21:53:51.427-06:00 warning vpxd[04347] [Originator@6876 sub=VpxProfiler] Init [AlarmMoManager::Init()] took 989 ms
2020-05-27T21:53:51.431-06:00 warning vpxd[04347] [Originator@6876 sub=vpxUtil] [VpxVmomi] Found previous domain socket /var/run/vmware/vpxd-webserver-pipe. Removing...
2020-05-27T21:53:51.431-06:00 info vpxd[04347] [Originator@6876 sub=HttpSvc.HTTPService] Using default for nonChunkingAgents
2020-05-27T21:53:51.431-06:00 info vpxd[04347] [Originator@6876 sub=HttpSvc.HTTPService] Using default for agentsNeedingContentLength
2020-05-27T21:53:51.431-06:00 info vpxd[04347] [Originator@6876 sub=HttpSvc.HTTPService] Max buffered response size is 104857600 bytes

2020-05-27T21:53:51.443-06:00 warning vpxd[04347] [Originator@6876 sub=MoExtensionMgr] Public key file or VECS info is not found or is not valid for extension com.vmware.vim.stats.report
2020-05-27T21:53:51.444-06:00 warning vpxd[04347] [Originator@6876 sub=MoExtensionMgr] Public key file or VECS info is not found or is not valid for extension com.vmware.vim.vcha
2020-05-27T21:53:51.461-06:00 warning vpxd[04347] [Originator@6876 sub=MoExtensionMgr] Public key file or VECS info is not found or is not valid for extension hostdiag
2020-05-27T21:53:51.547-06:00 error vpxd[04347] [Originator@6876 sub=MoDiagnosticMgr] [DiagnosticManagerMo] Diagnostic server root (/etc/vmware-vpx/docRoot/diagnostics) does not exist!
2020-05-27T21:53:51.547-06:00 error vpxd[04347] [Originator@6876 sub=Main] Init failed. SystemError: N5Vmomi5Fault11SystemError9ExceptionE(Fault cause: vmodl.fault.SystemError
--> )
--> [context]zKq7AVECAAAAAHna9AAKdnB4ZAAA4AArbGlidm1hY29yZS5zbwAAWCUbAP6dGAHu/FN2cHhkAAHp/lMB4FZUAfByVAEZ0VICkAUCbGliYy5zby42AAGlyVI=[/context]
2020-05-27T21:53:51.548-06:00 warning vpxd[04347] [Originator@6876 sub=VpxProfiler] ServerApp::Init [TotalTime] took 4966 ms
2020-05-27T21:53:51.548-06:00 error vpxd[04347] [Originator@6876 sub=Default] Failed to intialize VMware VirtualCenter. Shutting down
2020-05-27T21:53:51.548-06:00 info vpxd[04347] [Originator@6876 sub=SupportMgr] Wrote uptime information
2020-05-27T21:55:47.138-06:00 info vpxd[04347] [Originator@6876 sub=Default] Forcing shutdown of VMware VirtualCenter now

Cause
This issue occurs if /etc/vmware-vpx/docRoot/diagnostics is missing.
Resolution

To solve this issue:

root@vcentersrv1 [ /etc/vmware-vpx/docRoot ]# ls -ltrh

total 136K

-r--r--r-- 1 root root 42K Apr 16 09:30 What-is-a-VCserver.png

-r--r--r-- 1 root root 2.1K Apr 16 09:30 quickstart.pdf

-r--r--r-- 1 root root 793 Apr 16 09:30 print.css

-r--r--r-- 1 root root 4.2K Apr 16 09:30 index.html

-r--r--r-- 1 root root 16K Apr 16 09:30 header-logo.png

-r--r--r-- 1 root root 2.6K Apr 16 09:30 default.css

drwxr-xr-x 2 root root 4.0K May 27 20:34 de

drwxr-xr-x 2 root root 4.0K May 27 20:34 client

drwxr-xr-x 2 root root 4.0K May 27 20:34 scripts

drwxr-xr-x 2 root root 4.0K May 27 20:34 ko

drwxr-xr-x 2 root root 4.0K May 27 20:34 ja

drwxr-xr-x 2 root root 4.0K May 27 20:34 fr

drwxr-xr-x 2 root root 4.0K May 27 20:34 es

drwxr-xr-x 2 root root 4.0K May 27 20:34 en

drwxr-xr-x 2 root root 4.0K May 27 20:34 zh-TW

drwxr-xr-x 2 root root 4.0K May 27 20:34 zh-CN

drwxr-xr-x 2 root root 4.0K May 27 20:34 vsphere-client

drwxr-xr-x 2 root root 4.0K May 27 20:34 sdk

drwxr-xr-x 4 root root 4.0K May 27 20:36 vSphere-HA-depot

drwxr-xr-x 2 root root 4.0K May 27 21:59 certs


1. Create diagnostics folder by:

mkdir /etc/vmware-vpx/docRoot/diagnostics

2. Start all the services.

Comments

Post a Comment

Popular posts from this blog

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

  Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI   In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...
Post a Comment
Read more

Cloning and converting virtual machine disks with vmkfstools

 Purpose This article provides information and instructions on the use of the vmkfstools command to convert virtual machine disks from one type to another. Resolution The vmkfstools command offers the ability to clone virtual machine content and also convert from one virtual machine disk ( .vmdk ) format into another. Note : The host operating system chosen to perform the conversion may not necessarily support running of virtual machines via the output format defined. vmkfstools maintains the possibility of exporting virtual disks for use in other VMware products which support alternative disk formats. To convert a virtual machine disk from one type to another: Shut down the virtual machine. Virtual machine disk files are locked while in-use by a running virtual machine. Log in to the VMware vSphere Management Assistant (v...
Post a Comment
Read more

Troubleshooting vpxd service on Windows vCenter Server

  Symptoms You cannot connect to VMware vCenter Server with the vSphere Client. You cannot see the VMware vCenter Server in the inventory in the vSphere Web Client. You see a Microsoft Windows Event error associated with IIS similar to: Event properties - Event 7024, Service Control Manager The VMware VirtualCenter Server service terminated with service-specific error The system cannot find the file specified.. Log Name: System Source: Service Control Event ID: 7024 Level: Error Note : A windows Event ID 1000 may also be reported in relation to this issue.   Connecting to vCenter Server fails with the error: Cannot connect to host server_name : No connection could be made because the target machine actively refused it.   Attempting to start the VMware VirtualCenter Server service fails. You see this error: Windows could not start the VMware VirtualCenter Server service on...
Post a Comment
Read more