Skip to main content

vsan-health service not starting : "An error occurred while starting service 'vsan-health'"

  Symptoms

  • vsan-health service not starting : "An error occurred while starting service 'vsan-health'"
  • vSAN related logs will not capture the actual error.
  • vMon log will also give any hint on the failure. 
  • Checking vmware-vsan-health-runtime.log.stderr gives the following trace
Starting service process with pid: 542.
Traceback (most recent call last):
  File "/usr/lib/vmware-vpx/vsan-health/VsanMgmtServer.py", line 382, in <module>
    SetupLogging(gCmdOptions, logdir)
  File "/usr/lib/vmware-vpx/vsan-health/VsanMgmtServer.py", line 194, in SetupLogging
    Logger.InitLogging(logDir)
  File "/usr/lib/vmware-vpx/vsan-health/logger/Logger.py", line 295, in InitLogging
    SetupLoggers(loggerConfFile, logDir)
  File "/usr/lib/vmware-vpx/vsan-health/logger/Logger.py", line 273, in SetupLoggers
    configInFile = UpdateFormatterHandlerPath(f)
  File "/usr/lib/vmware-vpx/vsan-health/logger/Logger.py", line 231, in UpdateFormatterHandlerPath
    config = json.load(configFile)
  File "/usr/lib/python3.5/json/__init__.py", line 268, in load
    parse_constant=parse_constant, object_pairs_hook=object_pairs_hook, **kw)
  File "/usr/lib/python3.5/json/__init__.py", line 319, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3.5/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.5/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
Cause
This issue can happen if the logger.conf is corrupted
Impact / Risks
  • VAMI based backups will fail since the service is stopped.
  • vSAN monitoring information would not be available.
Resolution
To resolve the issue.

1. Change Directory: cd /etc/vmware-vsan-health
2. Move the file logger.conf to another location.
mv logger.conf /var/tmp/logger.conf

3. Once done, try restarting the service : 
vmon-cli -r vsan-health

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

"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