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

"VMware vSphere Update Manager had an unknown error" while scanning host for upgrade on 6.7 U3 (76259)

Last Updated: 4/19/2023Categories: TroubleshootingTotal Views: 19455Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

"Host Upgrade" Compliance scan on 6.7U3 Update Manager fails with error "VMware vSphere Update Manager had an unknown error".

You will see similar log entries in /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server-log4cpp.log log file as mentioned below,

vmware-vum-server-log4cpp.log:
[2019-10-08 11:35:23:332 'JobDispatcher' 139791892846336 INFO]  [JobDispatcher, 1860] Scheduling task SingleHostUpgradeScanTask{16} that imposes 1 for ESX: host-7267 new load: 1 that imposes 1 for VMware vSphere Update Manager new load: 1
[2019-10-08 11:35:23:394 'SingleHostUpgradeScanTask.SingleHostUpgradeScanTask{16}' 139791892580096 INFO]  [singleHostUpgradeScanTask, 338] Scanning host esxi1.vmwarelab.com against upgrade VMware ESXi 6.7.0 Update 2 (profile name = DELL_ESXi-6.7u2-13006603_Customized-A00-NO--MLX-lsi_mr3_7.705.10)
[2019-10-08 11:35:27:559 'AgentDeploy' 139791892580096 INFO]  [agentDeploy, 247] Agent installed
[2019-10-08 11:35:27:560 'SingleHostUpgradeScanTask.SingleHostUpgradeScanTask{16}' 139791892580096 ERROR]  [singleHostUpgradeScanTask, 277] Error while scanning: Connection reset by peer: The connection is terminated by the remote end with a reset packet. Usually, this is a sign of a network problem,  timeout, or service overload.

Note:

Above VUM log shows that the VUM received a reset from the ESXi while performing the Scan.

In ESXi host esxupdate.log will not have any error.

In such scenario, Packet capture on both the VCSA and ESXi will show more data to understand the cause of failure.

Example: (ESXi packet capture sample)
3584    2019-10-22 20:25:18.924715    10.19.14.6    10.19.14.20    TCP    66    58940 → 80 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 WS=256
3392    2019-10-22 20:25:18.924729    10.19.14.20    10.19.14.6    TCP    66    80 → 58940 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 WS=512 SACK_PERM=1
3585    2019-10-22 20:25:18.924954    10.19.14.6    10.19.14.20    TCP    60    58940 → 80 [ACK] Seq=1 Ack=1 Win=29440 Len=0

3586    2019-10-22 20:25:18.925990    10.19.14.6    10.19.14.20    TCP    60    58940 → 80 [RST, ACK] Seq=1 Ack=1 Win=29440 Len=0

Packet capture on ESXi shows that vCenter connected to ESXi on TCP port 80 and after TCP 3 way handshake vCenter sent a "Reset" packet to ESXi.

Example: (vCenter Server packet capture sample)

4029    2019-10-22 20:25:18.924969    10.19.14.6    10.19.14.20    TCP    66    58940 → 80 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 WS=256
4030    2019-10-22 20:25:18.925351    10.19.14.20    10.19.14.6    TCP    66    80 → 58940 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 WS=512 SACK_PERM=1
4031    2019-10-22 20:25:18.925386    10.19.14.6    10.19.14.20    TCP    54    58940 → 80 [ACK] Seq=1 Ack=1 Win=29440 Len=0

4033    2019-10-22 20:25:18.926547    10.19.14.20    10.19.14.6    TCP    60    80 → 58940 [RST, ACK] Seq=1 Ack=140 Win=58880 Len=0

Packet capture on vCenter shows that vCenter connected to ESXi on TCP port 80 and after TCP 3 way handshake ESXi sent a "Reset" packet to vCenter.

Such behavior can be seen if there is a Firewall acting as an intermediate device closing session (Sending Reset) on both ends.

Note:

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

Above issue occurs for a specific set of ESXi which are behind Firewall.

Above issue is not seen for "Patch Scan"

Purpose

This article is to identify and resolve the "Host Upgrade" Compliance scan failure with error "VMware vSphere Update Manager had an unknown error".

Cause

Firewall between ESXi and vCenter has a specific rule to block data transfer on TCP port 80.

Resolution

To resolve this issue remove the Firewall policy between the vCenter and ESXi on Port 80.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
具有大量数据存储的主机的引导时间较长 (74583)

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-3 of 3

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 ESXi

VMware vSphere

Related Versions:

VMware vSphere Update Manager 6.7.x

VMware vSphere ESXi 6.7

Take Our Survey

Support Assistant