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

VUM scan fails with error "VMware vSphere Update Manager had an unknown error. Check the events and log files for details" (76357)

Last Updated: 4/16/2020Categories: TroubleshootingTotal Views: 18503Language:
Chinese (Simplified)English

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Scanning an ESXi host  fails with error "VMware vSphere Update Manager had an unknown error. Check the events and log files for details"

vmware-vum-server-log4cpp.log on the VUM server  shows the below errors:

[2019-11-26 23:38:27:794 'SingleHostUpgradeScanTask.SingleHostUpgradeScanTask{321}' 139906224486144 ERROR] [singleHostUpgradeScanTask, 277] Error while scanning: Connection refused: The remote service is not running, OR is overloaded, OR a firewall is rejecting connections.

vmware-vum-server.log on the VUM server  shows the below errors:

2019-11-27T01:40:47.875Z warning vmware-vum-server[23811] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x00007f3e20026fd0, h:25, <TCP '<IP of VUM server> : 37082'>, <TCP '<IP of ESXi host> : 80'>>, e: 111(Connection refused)

Running nc (netcat) command on the ESXi host port 80 fails with connection refused error:

nc -tv <IP of ESXi Host> 80

<FQDN of ESXi host> [<IP of ESXi Host>] 80 (http): Connection refused

Cause

VUM requires port 80 to be open between the VUM/vCenter server and the ESXi host. If a Firewall is blocking port 80, then you see these errors.

Resolution

Open port 80 on the Network Firewall between VUM/vCenter and ESXi hosts

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

KB
•
从 vSphere 导入虚拟机时出现报错：无法查找属性 'vcloud.HardwareVersion.Hw4.MaxNics' (78582)

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

Related Versions:

VMware vSphere Update Manager 6.7.x

Take Our Survey

Support Assistant