lethargos
Enthusiast
Enthusiast

VMware vSphere Update Manager had an unknown error. Check the events and log files for details.

Jump to solution

I'm having trouble scanning for updates on vsphere 6.5. I get the message in the thread subject each time I try to scan for updates. I've also taken a look at /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server-log4cpp.log:

[CODE]

[2018-08-27 13:10:50:011 'HostUpdateDepotManager' 140487137134336 ERROR]  [patchDepotManager, 663] Error in download and parse metadata: Failed to download file: https://hostupdate.vmware.com/software/VUM/PRODUCTION/csco-main/esx/csco/csco-VEM-5.5.0-notification... when downloading metadata: Failed to download metadata zip file: https://hostupdate.vmware.com/software/VUM/PRODUCTION/csco-main/esx/csco/csco-VEM-5.5.0-notification...

[2018-08-27 13:10:50:011 'VciCheckNotificationTask.CheckNotificationTask{11382}' 140487137134336 ERROR]  [vciCheckNotificationTask, 524] There was an error downloading ESX notification from: https://hostupdate.vmware.com/software/VUM/PRODUCTION/csco-main/csco-depot-index.xml, error: Failed to download file: https://hostupdate.vmware.com/software/VUM/PRODUCTION/csco-main/esx/csco/csco-VEM-5.5.0-notification... when downloading metadata: Failed to download metadata zip file: https://hostupdate.vmware.com/software/VUM/PRODUCTION/csco-main/

[/CODE]

or this:

[CODE]

[2018-08-27 13:10:02:244 'VciScanTask.ScanTask{11383}' 140487130212096 INFO]  [vciTaskBase, 1349] SerializeToVimFault fault: (integrity.fault.VcIntegrityFault) {    faultCause = (vmodl.MethodFault) null,     faultMessage =    msg = "" } Converted fault: (vim.fault.ExtendedFault) {    faultCause = (vmodl.MethodFault) null,     faultMessage =,     faultTypeId = "com.vmware.vcIntegrity.VcIntegrityFault",     data = (vim.KeyValue) [       (vim.KeyValue) {          key = "faultCause",           value = ""       },        (vim.KeyValue) {          key = "faultMessage",           value = ""       }    ]    msg = "" } [2018-08-27 13:10:02:244 'VciScanTask.ScanTask{11383}' 140487130212096 INFO]  [vciTaskBase, 1621] Description updated [2018-08-27 13:10:02:247 'VciScanTask.ScanTask{11383}' 140487130212096 INFO]  [vciTaskBase, 1362] VciTask { id: ScanTask{11383}, type: com.vmware.vcIntegrity.ScanTask }: Setting VC task state to: error [2018-08-27 13:10:02:252 'VciScanTask.ScanTask{11383}' 140487130212096 INFO]  [vciTaskBase, 190] Delete VC task from database: task-11207

[2018-08-27 13:10:02:244 'VciScanTask.ScanTask{11383}' 140487130212096 INFO]  [vciTaskBase, 1621] Description updated

[2018-08-27 13:10:02:247 'VciScanTask.ScanTask{11383}' 140487130212096 INFO]  [vciTaskBase, 1362] VciTask { id: ScanTask{11383}, type: com.vmware.vcIntegrity.ScanTask }: Setting VC task state to: error

[2018-08-27 13:10:02:252 'VciScanTask.ScanTask{11383}' 140487130212096 INFO]  [vciTaskBase, 190] Delete VC task from database: task-11207

[/CODE]

I'm not sure what I'm supposed to be looking for.

Any ideas what's going on? What other info should I be searching for?

0 Kudos
1 Solution

Accepted Solutions
a_p_
Leadership
Leadership

Welcome to the Community,

unless you are using the Cisco Virtual Ethernet Module (VEM) you can try to disable/delete the specific Download Source in the Update Manager settings (Update Manager -> Manage -> Settings-> Download Settings, then click Edit).

If this doesn't help you may consider resetting the Update manager Datastore (see https://kb.vmware.com/s/article/2147284)

André

View solution in original post

0 Kudos
8 Replies
RishiRajKumar
VMware Employee
VMware Employee

Try the workaround provided in this article:

VMware Knowledge Base

0 Kudos
lethargos
Enthusiast
Enthusiast

"

To workaround this issue:

  1. Open downloadConfig.xml file from /usr/local/vmware-umds/bin.
  2. Update the urls from https to http in HostConfig."

I've sshed into the cluster and there's no such thing as /usr/local/vmware-umds. (The cluster consists of three blades, each with their own vmware interface).

[Later edit:]

What I found instead was /usr/local/lib64/vmware-updatemgr/bin, but no "downloadConfig.xml"

0 Kudos
a_p_
Leadership
Leadership

Welcome to the Community,

unless you are using the Cisco Virtual Ethernet Module (VEM) you can try to disable/delete the specific Download Source in the Update Manager settings (Update Manager -> Manage -> Settings-> Download Settings, then click Edit).

If this doesn't help you may consider resetting the Update manager Datastore (see https://kb.vmware.com/s/article/2147284)

André

View solution in original post

0 Kudos
lethargos
Enthusiast
Enthusiast

Hi,

Thanks for the answer. What happens exactly if I delete them? I have three sources. Would they be automatically regenerated afterwards?

[later edit:]

Actually I'm unable to delete any source. I can only disable them. The point is I seem to be able to scan for upgrades (it says complete under Recent Tasks), but if I also tick "patches and extensions", I end up with the same error.

Another question: in the update manager section, there weren't any Baselines. Are they necessary in order to get the upgrade done? I saw that if I attach these two baselines (critical host patches and non-critical host patches), I can remediate the nodes. Are those updates taking into consideration what updates have already been applied to each node?

0 Kudos
a_p_
Leadership
Leadership

Just a quick question. The only time I came across such an issue myself was after a migration from a vCenter Server instance that had Update Manager installed. Is your environment a new setup, or did you migrate/upgrade from a previous version?

Actually I'm unable to delete any source. I can only disable them. ...

You are right. the default download sources can only be disabled.

Another question: in the update manager section, there weren't any Baselines. Are they necessary in order to get the upgrade done? I saw that if I attach these two baselines (critical host patches and non-critical host patches), I can remediate the nodes. Are those updates taking into consideration what updates have already been applied to each node?

There are baselines for Host-Upgrades, Patches, etc. In order to e.g. patch a host, you will either need to attach one of the default Patch baselines to the hosts, or - that's my preferred option - create a fixed Patch baseline, and attach this one to the hosts. Each host maintains a list of components that are installed. Update Manager will basically compare the components in the baseline with those already installed on a host.

Note: I just ran the reset from the KB article in my lab environment and it did reset Update Manager to its defaults. The download sources are still there after the reset.


André

0 Kudos
lethargos
Enthusiast
Enthusiast
Indeed, after resetting the update manager, there were no more errors. It simply said "completed". However, not until I attached the baselines did the actual updates show up.
I was given this setup as it as, and I'm still struggling to understand all sorts of stuff. Why would the baselines be missing? Could that have been modified automatically or did someone do it?:)
I understand you might not be able to answer this question, but I want to understand how vmware behaves.
0 Kudos
a_p_
Leadership
Leadership

Why would the baselines be missing? Could that have been modified automatically or did someone do it?:)

I understand you might not be able to answer this question, but I want to understand how vmware behaves.

Indeed, only the one who managed this environment before may be able to answer the question.

My guess is that the current vCenter has been upgraded/migrated from an earlier version.

Update Manager itself is basically easy to manage. There are a few settings including the Download Sources, and a couple of default Baselines which are ready to use. You will only need to add additional Download Sources for e.g. vendor specific downloads (drivers, tools, etc.) if required.

The only thing you actually need to do, is to attach the Baslines to your hosts to be able to Scan and/or Remediate them. As mentioned earlier, I usually create own Baselines with fixed components. I'm doing this to ensure that all hosts will be patched to the exact same state, no matter whether VMware releases new patches while I'm still busy with remediating the hosts (which may take some time, depending on the size of the environment).


André

0 Kudos
lethargos
Enthusiast
Enthusiast

Great. Thanks for the answers. Really helpful!

0 Kudos