Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vSAN Health service fails to start after performing vCenter upgrade (76065)

Last Updated: 8/19/2022Categories: TroubleshootingTotal Views: 16095Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

vSAN Health service fails to start in a VCHA configuration after performing a vCenter upgrade.

In /var/log/vmware/vsan-health/vsanvp.log on vCenter Server you can see errors similar to:

2020-05-07T12:18:31.108Z INFO vsanvp[thread-140087258990336] [ServiceInstance::RegisterVsanVP opID=vsan-PC-5a50db754a83e-W446]
Register VSAN VP to SMS service.
2020-05-07T12:18:36.256Z ERROR vsanvp[thread-140087258990336] [ServiceInstance::RegisterVsanVP opID=vsan-PC-5a50db754a83e-W446]
Failed to register VSAN VP to sms service
Traceback (most recent call last):
File "/usr/lib/vmware-vpx/vsan-health/pyMoVsan/ServiceInstance.py", line 81, in RegisterVsanVP
raise info.error
VsanVmomiPatcher.sms.fault.ProviderRegistrationFault: (sms.fault.ProviderRegistrationFault) {
msg = 'Validation of VMOMI server version got from provider failedCould not find version class for: null',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) []
}

In /var/log/vmware/vsan-health/vmware-vsan-health-service.log on vCenter Server you see errors similar to:

2020-05-07T12:18:31.108Z CRITICAL vsan-mgmt[MainThread] [VsanMgmtServer::UncaughtExcpetionHandler opID=noOpId] Traceback (most recent call last):
File "/usr/lib/vmware-vpx/vsan-health/VsanMgmtServer.py", line 436, in <module>
_VsanMgmtServer.Start()
pyVmomi.VmomiSupport.vmodl.RuntimeFault: (vmodl.RuntimeFault) {
msg = 'N7Vmacore23FileIONotFoundExceptionE: Could not find file  : /etc/vmware-vsan-health/.cns_pgpass',
faultCause = <unset>,
faultMessage = (vmodl.LocalizableMessage) []
}

One may observe the following error when trying to add a VM Disk:

"PBM error occurred during PreReconfigureCallback: Fault cause: vmodl.fault.SystemError"

Cause

The issue observed on the SPBM side is occurring due to vSAN VP inability to register itself with the SMS, service since vmware-vsan-health service is failing to start due to missing /etc/vmware-vsan-health/.cns_pgpass file.

Resolution

This is a known issue affecting vCenter upgrade - e.g., when upgrading from any 6.7 to 6.7 U3 or when upgrading from 6.7 U3 to any 6.7 U3 patch release (e.g. 6.7 U3g).

Fix due in a future release, subscribe to this KB to be updated when the fixed in version is released.

Workaround

To work around this issue, you must regenerate the missing file via the following procedure:

Login via SSH to the vCenter Appliance which failed to start vsan-health service after upgrade to 6.7 U3.

Run the following command to re-generate the missing file .cns_pgpass:

# PYTHONPATH=/usr/lib/vmware-vpx/pyJack/:/usr/lib/vmware/site-packages/  python /usr/lib/vmware-vpx/firstboot/CnsVcConfigure.py

You should see the following output in the terminal:

2020-05-07T12:18:31.108Z  Configuring DB for CNS service
2020-05-07T12:18:41.108Z  Getting value for install-parameter: vpostgres.int.server_port
2020-05-07T12:18:51.108Z  CNS DB configured successfully.

Start vsan-health service by running command:

# service-control --start vmware-vsan-health

Verify the vsan-health service has started.

# service-control --status vsan-health

6. If step 4 doesn't work then reboot vCenter

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant