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

"Host cannot download files from VMware vSphere Update Manager patch store. Check the network connectivity and firewall setup, and check esxupdate logs for details." (67705)

Last Updated: 3/16/2021Categories: TroubleshootingTotal Views: 52831Language:
Chinese (Simplified)JapaneseEnglish

20 like this article

Subscribe to get an email
newsletter with new updates

20 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

You are using Windows vCenter 6.x with Windows VMware Update Manager installed on the same or separate box

You encounter error while running "Scan for updates":

Host cannot download files from VMware vSphere Update Manager patch store.  Check the network connectivity and firewall setup, and check esxupdate logs for details.
- VUM logs also show bellow error stack:
'HostUpdateDepotManager' 14168 ERROR]  [scanHost20, 371] result for host: esxihost2.domain.local (entity: host-9895) shows error :
-----Result Begin (esxihost2.domain.local)-----
<esxupdate-response>
<version>1.50</version>
<error errorClass="MetadataDownloadError">
<errorCode>4</errorCode>
<errorDesc>Failed to download metadata.</errorDesc>
<url>http://192.168.1.123:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.0.0-metadata.zip</url>
<localfile>None</localfile>
<msg>('http://192.168.1.123:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.0.0-metadata.zip', '/tmp/tmptVJYa1', '[Errno 12] Timeout: &lt;urlopen error timed out&gt;')</msg>
</error>
</esxupdate-response>

You will see similar entries in vum-server.log as mentioned below,

vum-server.log
2019-04-17T18:39:26.421Z warning vmware-vum-server[7F1897F5D700] [Originator@6876 sub=Libs] SSL_Connect: SECURITY WARNING: Should use SSL_ConnectAndVerify instead
2019-04-17T18:39:26.573Z warning vmware-vum-server[7F188936E700] [Originator@6876 sub=Libs] SSL_Connect: SECURITY WARNING: Should use SSL_ConnectAndVerify instead
2019-04-17T18:39:26.593Z warning vmware-vum-server[7F188926A700] [Originator@6876 sub=Libs] SSL_Connect: SECURITY WARNING: Should use SSL_ConnectAndVerify instead

You will see similar entries in esxupdate.log as mentioned below,

Host cannot download files from VMware vSphere Update Manager patch store. Check the network connectivity and firewall setup, and check esxupdate logs for details.
[Errno 4] IOError: <urlopen error [Errno -3] Temporary failure in name resolution>'

Cause

ESXi host is unable to communicate with Update Manager through port 9084.

Resolution

The port 9084 is required for VMware Update Manager.

To resolve the issue make sure from ESXi to Update Manager Server or vCenter Server Port 9084 is open. Also check Update Manager port requirements

Update Manager Server is installed on a different node from the vCenter Server 6.x

Example: To test the connectivity between ESXi and vCenter Server or Update Manager Server if the port 9084 is port. From ESXi putty session run the below command,

nc -z [VCSA_IP] 9084
Connection to VCSA_IP 9084 port [tcp/*] succeeded!

If the above command is not succeeded, please check the 9084 port as mentioned in Step2 and get this port open between ESXi and VC/VUM.

Note: Make sure the forward lookup and reverse lookup for vCenter Server is working as expected using nslookup command.

If this article didn’t solve your issue:

Ask for help here : Click for VMware Communities

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
TCP and UDP ports required to access VMware vSphere Update Manager (52962)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere Update Manager

VMware vSphere

VMware vCenter Server

Related Versions:

VMware vSphere Update Manager 6.7.x

VMware vSphere Update Manager 6.5.x

VMware vSphere Update Manager 6.0.x

VMware vCenter Server 7.0.x

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

Take Our Survey

Support Assistant