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

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)         at com.vmware.vise.security.spring.DefaultAuthenticationProvider.logoutInternal(DefaultAuthenticationProvider.java:548)         at c

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 the error: Error connecting to <path><virtual machin

"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 database. For more info