updatemanager not working after crash and upgrade

[NielsX]

Did an upgrade to from 3.0.1 to 3.5 (latest iso build 64607) and applied al the patches with the new update manager. The new build is 77234; working perfectly.

Yesterday the server crashed due to a power failure (yes, got ups, no not configured correctly, but isn't the issue). Got a kernel panic when starting ESX so used the cd with build 64607 and did an upgrade.

System is booting again after the upgrade and working. The build is, as expected 64607. But Update manager tells me it has nothing to patch? 18 patches compliant?

vmware -v gives VMware ESX Server 3.5.0 build-64607

Why can't I use the new update manager anymore? What do I have to do to run update manager against the repaired ESX host? I believed that after a scan, update manager would recognize that the build is an older one and re-apply the patches, but It doesn't.

Someone know how to patch to build 77234, or get update manager working again?

[NielsX]

I did an esxupdate query and the output gives

ESX350-200802403-BG 14:58:33 03/25/08 Improved Data Collection for vm-support.

ESX350-200802409-BG 15:00:00 03/25/08 Fix Reset Issue with CD-ROM Controller.

ESX350-200802301-BG 15:00:55 03/25/08 Fix bnx2 issues

ESX350-200802303-SG 15:01:34 03/25/08 util-linux security update

ESX350-200802304-SG 15:02:21 03/25/08 perl security update

ESX350-200802305-SG 15:03:02 03/25/08 openssl security update

ESX350-200802306-BG 15:03:41 03/25/08 tzdata update

ESX350-200802401-BG 15:04:43 03/25/08 Updates to vmware-hostd.

ESX350-200802404-BG 15:07:31 03/25/08 Resolves DMA Issues on LSI HBAs.

ESX350-200802405-BG 15:08:15 03/25/08 Update to MegaRAID SCSI Driver.

ESX350-200802406-SG 15:08:57 03/25/08 Updated aacraid Driver.

ESX350-200802408-SG 15:09:38 03/25/08 Security Updates to the Python Package.

ESX350-200802410-BG 15:10:41 03/25/08 Updates for vmware srvrmgmt.

ESX350-200802411-BG 15:11:22 03/25/08 Fixes for Storage VMotion and Lab Manage

ESX350-200802412-BG 15:12:00 03/25/08 Updates to the VMkernel.

ESX350-200802413-BG 15:12:41 03/25/08 Updates to Emulex lpfc driver.

ESX350-200802414-BG 15:13:16 03/25/08 Discrete Sensors Report Wrong Informatio

ESX350-200802415-SG 15:14:03 03/25/08 Security Update to Samba Packages.

3.5.0-64607 17:39:15 03/31/08 Full bundle of ESX 3.5.0-64607

I've got an ESX server that did not crash and on that server the last entry (3.5.0-64607 ...) is before the ESX350 lines. So I think there is my problem? I think I have to remove the ESX350 entries? I don't think I have to remove the updates but just the entries in the view or something like that....

[RParker]

Well if you think about it logically, your ESX host is probably the same host name.

Therefore there is an entry in the database as that host. That host, according to the update manager database, has already been updated. It doesn't actually check the host, it just does a lookup in the table for that host.

I suppose you could remove the host, add it as the IP address, remediate it (at that moment it will be a different machine). Then remove it again, and add it back as the host name. That should allow you to patch it.

[NielsX]

Sounds really logical (thanks!). But before I try and get into the

database: maybe it is possible to clear the database? Delete the

specific host?

Does someone know were and what (safe) to delete?

Van: RParker

Verzonden: dinsdag 1 april 2008 16:17

Aan: servicedesk

Onderwerp: New message: "updatemanager not

working after crash and upgrade"

,

A new message was posted in the thread "updatemanager not working after

crash and upgrade":

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

Author : RParker

Profile : http://communities.vmware.com/people/RParker

Message: