vSAN-Health Service fails to start on a vCenter not using vSAN
Article ID: 382127
Updated On:
Products
Issue/Introduction
Attempting to submit a backup job via vCenter Server Appliance VAMI fails with error
Invalid vCenter Server Status: All required services are not up! Stopped services: 'vsan-health'.
Operations on vSphere Replication fails with error :
Operation Failed
A generic error occurred in the vSphere Replication Management Server. Exception details: 'Unexpected status code: 503'.
Operation ID: 3be4d590-8170-40e8-b4ae-14bf8258e3de
Certain operations on VMware Site Recovery Manager fail
You may find vSAN-Health Service fails to start with stack below
> service-control --start vmware-vsan-health
Operation not cancellable. Please wait for it to finish...
Performing start operation on service vsan-health...
Error executing start on service vsan-health. Details {
"detail": [
{
"id": "install.ciscommon.service.failstart",
"translatable": "An error occurred while starting service '%(0)s'",
"args"; [
"vsan-health"
],
"localized": "An error occurred while starting service 'vsan-health'"
}
],
"componentKey": null
"problemId": null,
"resolution": null
}
Service-control failed. Error: {
"detail": [
{
"id": "install.ciscommon.service.failstart",
"translatable": "An error occurred while starting service '%(0)s'",
"args": [
"vsan-health"
],
"localized": "An error occurred while starting service 'vsan-health'"
}
],
"componentKey": null
"problemId": null,
"resolution": null,
}
> /var/log/vmware/vsan-health/vmware-vsan-health-runtime.log.stderr log
Starting service process with pid: 3138403.
Traceback (most recent call last):
File "bora/vsan/health/vpxd/VsanMgmtServer.py", line 259, in <module>
File "/lib/python3.10/configparser.py", line 698, in read
self._read(fp, filename)
File "/lib/python3.10/configparser.py", line 1086, in _read
raise MissingSectionHeaderError(fpname, lineo, line)
configparser.MissingSectionHeaderError: File contains no section headers.
file: '/etc/vmware-vsan-health/config.conf', line:1
'signature = "sIgNaTuRe"\n'
(END)
This indicates there has been a change to the config.conf file for vsan-health that is unrecognized
Cause
There has been a change to the vsan-health config.conf file
Resolution
To resolve this, take the following steps:
Verify the config.conf file is incorrectly formatted
A correct config will look similar to the below:
> cat /etc/vmware-vsan-health/config.conf
[General]
logdir = /var/log/VMware/vsan-health
rotationsizemb = 10
backupcount = 20
enabledinternetaccess= True
pyjack = /usr/lib/vmware-vpx/pyJack
httpport = 8006
rhttpproxyhttpport = 80
rhttpproxyhttpsport = 443
overallhealthalarminit = True
[PhoneHome]
enablevsantelemetrycollectiondefault = False
vsantelemetrycollectionintervalinmindefault = 10080
[CloudHealth]
phonehomedeploymentsecret =
[StretchedCluster]
vsan.stretchedcluster.upgrade = False
vsan.stretchedcluster.upgrade_67u3_70 = True
[GenericNestedFaultdomain]
vsan.genericnestedfd.upgraded = True
[VumIntegration]
enabled = True
Take a snapshot of the vCenter or offline snapshots of all vCenters in an ELM cluster
Navigate to /etc/vmware-vsan-health/
Make a backup copy of config.conf
Example: cp config.conf config.conf.old
Get a copy of the config file from another vCenter on the same version that is also not using vSAN
Edit the config.conf file
> vi config.conf
Hit I to insert and then replace any data with the data from the other vCenter
Hit ESC to exit the insert command
Type: :wq! to save the changes
Start the vmware-vsan-health service
> service-control --start vmware-vsan-health
Verify you are now able to take VAMI backups
Feedback
