Highlighted
Contributor
Contributor

Update Manager 4.1 can't scan host after 4.1 upgrade

I have upgraded my vCenter server to 4.1, then installed Update Manager 4.1, which was able to scan and remediate my ESX 4.0u1 hosts.

I remediated with the Upgrade Baseline to 4.1, the update went smoothly and all hosts are compliant.

I went to re-scan the hosts, just to ensure they are compliant and I noticed the 'Scan Entity' job was hanging for a few minutes, then it told me to review my Tasks & Events which states:

VMware vCenter Update Manager had an unknown error. Check the Tasks and Events tab and log files for details.

This is all it says, it gives no other details. I have looked at the log files, but there is a lot of data in there and I have no idea what I am looking for.

Has anyone else run in to this and if so, any idea on how to fix it?

Thanks!

1parkplace

0 Kudos
11 Replies
Highlighted
Contributor
Contributor

Based on reading another post, I searched for a particular log entry and found:

vmware-vum-server-log4cpp.log(401447): Task started...

vmware-vum-server-log4cpp.log(401455): SingleHostScan caught exception: No metadata found for the platform: esx, 4.1.0, INTL with code: -1

vmware-vum-server-log4cpp.log(401456): Task execution has failed: No metadata found for the platform: esx, 4.1.0, INTL

vmware-vum-server-log4cpp.log(401457): A subTask finished: SingleHostScanTask

vmware-vum-server-log4cpp.log(401639): Task finished, state: 3

Maybe this will help some figure out what the problem may be.

Thanks!

0 Kudos
Highlighted
Contributor
Contributor

Refer to this post for more details on the topic.

http://communities.vmware.com/message/1576349

It appears either the new update manager is defective when scanning newly upgraded 4.1 hosts... or VMWare hasn't released the metadata for 4.1.0 yet.

0 Kudos
Highlighted
Expert
Expert

Did Update Manager 4.1 download the esx 4.1 release ?

DO use a proxy?

When using a Proxy with Update Manager, you must set trusted sites within the browser

0 Kudos
Highlighted
Expert
Expert

pfuller wrote:

I put in a case with VMware and since they are have release no patches,

hence met-data for patches for VUM to look at you will get the error.

This will continue until VMware come out with patches.

http://communities.vmware.com/thread/276563

0 Kudos
Highlighted
Hot Shot
Hot Shot

I was able to resolve this issue. Here's what my issue was and how I fixed it.

I went from ESX 4.0 to ESX 4.1. I also upgraded vCenter from 4.0 to 4.1.

The host/vCenter upgrade went fine, however once I was all done I tried

to scan my hosts to see if any new patches were available.

That's when it would fail.

I had to uninstall the update manager component on my vCenter server.

When I did a reinstall I made sure it did an override of the old

database data (only for update manager NOT vCenter DB). After that

update manager can now scan my ESX 4.1 hosts with no issues.

Hope this helps someone out there.

0 Kudos
Highlighted
Enthusiast
Enthusiast

I was able to resolve this issue. Here's what my issue was and how I fixed it.

I went from ESX 4.0 to ESX 4.1. I also upgraded vCenter from 4.0 to 4.1.

The host/vCenter upgrade went fine, however once I was all done I tried

to scan my hosts to see if any new patches were available.

That's when it would fail.

I had to uninstall the update manager component on my vCenter server.

When I did a reinstall I made sure it did an override of the old

database data (only for update manager NOT vCenter DB). After that

update manager can now scan my ESX 4.1 hosts with no issues.

Hope this helps someone out there.

So what you're saying is that there is no point to migrating/upgrading the update manager database to 4.1? Has anyone had success after upgrading update manager to 4.1 with scanning ESX(i) 4.1 hosts?

0 Kudos
Highlighted
Enthusiast
Enthusiast

We had a different source problem, I believe.

Our resolution was to remove the ESX 4.0U1 hosts from the cluster and then re-add them to the cluster. I believe the a sympton of our problem was that we retained the same computer name but changed the IP address.

I am not sure if it was a name resolution issue or a SSL certificate issue, but one of the two or both seem to have been fixed by re-adding the host to the cluster.

Kevin

0 Kudos
Highlighted
Contributor
Contributor

Make sure you can ping from the VM host to the vCenter server (windows firewall)

0 Kudos
Highlighted
Contributor
Contributor

I ran into the same issue a few days ago and the only thing that fixed it was to uninstall and reinstall (overwriting the database) Update Manager Server.

I had tried everything....nothing had worked ...(I was able to scan VMs but not hosts) ) until I found your post here.....you saved me ..:).....I even opened a SR with vmware support and the guy was clueless......

THANK YOU !!!

0 Kudos
Highlighted
Contributor
Contributor

I second the motion. Somehow this caused:

1. Cannot sacn the hosts.

2. Cannot remediate the hosts.

3. Java.exe goes to 100% and brings the vCenter server to a crawl. Stopping the VMware Update Manager service temporarily helps this.

Order was:

Updated VCenter and Update Manager with ESXi 4.1 U1 .

Went to update the hosts and ran into this problem.

On 3 different clusters i updated the hosts first and did not have this issue.

I thought i would try the 'most approved' method of doing vCenter first. Ooops!

So re-installing update manager and specifying initializing the database helped.

Note: I chose to use a seperate database for Update Manager Originally so had no worries about inadvertently destroying my vCenter database.

So re-install Update manager.

Specify to intialize my database (always take database backups first just in case).

After install reset the service account so Update Manager can connect to the database. Even specifying the account during the install and being logged on with the account during the install didn't keep me from having to reset the service account for the Update Manager service.

I would also recommend to set the proxy incorrectly so it cannot download the new patches yet. Set the source to just ESX from Vmware. And then reset the proxy and re-download the patches. This will be less patches and just the ESX patches.

Thanks again for the post. I also thought something was strange with the way it was behaving with its patch repository.

Ron

0 Kudos
Highlighted
Contributor
Contributor

My issue with update manager not scanning hosts seems to be limited to build 82664 hosts ( 3.5 u1).  If I rebuild the server and make it 3.5 u5 then it works just fine.

Has anyone fixed this yet?  I have around 50 servers to upgrade and a destructive build is not an option!

0 Kudos