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

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)   ...
Post a Comment
Read more

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive ...
Post a Comment
Read more

"Performance data is currently not available for this entity" viewing the performance tab

  Symptoms While accessing the performance tab and navigating to Overview, you see: No data available   The data for Real time, but fails to retrieve it for past 1 day, week, month or year.  While selecting the advance parameter in performance tab, you see: Performance data is currently not available for this entity Cause This issue is caused by the vCenter Server database (Postgress) containing a stale/future time stamp reference for the ESXi host when the data was collected. For vCenter Servers using SQL, see  "Performance data is currently not available for this entity" error after updating rollup in vSphere Resolution Backup the vCenter...
Post a Comment
Read more