Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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 when upgrading to vCenter Server 6.7 U3 (78921)

Last Updated: 5/4/2020Categories: TroubleshootingTotal Views: 6812Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

vCenter Server upgrade may fail due to vSAN health service cannot be started.

In the /var/log/vmware/vsan-health/vmware-vsan-health-service.log, you see error message similar to:

2020-04-30T06:02:01.601Z ERROR vsan-mgmt[HclAutoUpdator] [VsanWpadUtil::getWpadProxy opID=noOpId] Fails in getting auto proxy for url:http://www.vmware.com, host:www.vmware.com with error:maximum recursion depth exceeded
Traceback (most recent call last):
File "/usr/lib/python3.5/site-packages/js2py/evaljs.py", line 173, in execute
compiled = cache[hashkey]
KeyError: b'\xbc;<\xaf\xeeI\xa9\xb8\xb8\xef_\xcd\xf9uh\xea'

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue is caused by the third party python library js2py which is used for evaluating Java script in vSAN health service.
In this library, it may cause python stack overflow to crash the whole python server when evaluating large functions of java script.

Resolution

This is a known issue.

Currently, there is no resolution.

Workaround

To workaround this issue:

SSH into vCenter Server.

Take a backup of config.conf file /etc/vmware-vsan-health/config.conf.

Edit  the config.conf file to add an invalid proxy IP into “[PhoneHome]” section as below:

[PhoneHome]
enablevsantelemetrycollectiondefault = False
vsantelemetrycollectionintervalinmindefault = 10080
proxyhost = 10.1.1.1      ----------------------------------------- Add an  invalid proxy IP
proxyport = 1000

Save the file.

Restart vSAN health service by running the command:

/usr/lib/vmware-vmon/vmon-cli -r vsan-health

Retry the Upgrade.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
「URL を確認して、やり直してください (Check the URL and try again)」- vCenter 7.0 VAMI の [アップデート] パネル (78906)

KB
•
将 Cloud Director 9.5 迁移到 10.0 的过程中，出现“无法读取或写入配置文件: 密钥库已被篡改，或密码不正确”错误 (78924)

KB
•
VMware Intelligent Hub 20.04 for iOS リリースのお知らせ (78889)

KB
•
将事件从 vRealize Log Insight 导出到 NFS 失败，并显示 "无法添加新的导出任务。错误：NFS 路径语法无效 " (78902)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

Take Our Survey

Support Assistant