VMware Cloud Community
TUMichaelF
Contributor
Contributor
Jump to solution

Upgrade Fails because of pre-upgrade step

I have read all of the other posts I could find on this subject, but I am going from ESX 4 -- 4.1 and I am following the steps on http://v-reality.info/2010/07/esx-host-upgrade-to-4-1-using-esxupdate/.

The error I get is

[root@host tmp]# esxupdate update --bundle=upgrade-from-ESX4.0-to-4.1.0-0.0.260247-release.zip
Host was not updated, no changes required.
Skipping bulletin ESX410-GA-esxupdate; it is installed or obsoleted.
Encountered error RunCommandError:
   This is an unexpected error.  Please report it as a bug.
   Error Message - Command '['/usr/bin/vim-cmd', 'hostsvc/runtimeinfo']'
                   terminated due to signal 6
I already ran the preupgrade package and from what I read http://communities.vmware.com/message/1750003, this is most likely the problem.  How I do remove the preupgrade package???

Any help would be appreciated.

Thanks,

Michael

0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal
Jump to solution

To resolve this issue, run the `ldconfig` command from the service console, and attempt to run esxupdate again.  --wt

View solution in original post

0 Kudos
5 Replies
jcwuerfl
Hot Shot
Hot Shot
Jump to solution

Are you sure you didn't have 4.1 already installed?  If all else fails you can always do a full (clean) install of 4.1 on the host.   Not sure what the issue is that upgrade.  Have you put a call into vmware support?

TUMichaelF
Contributor
Contributor
Jump to solution

vmware -v
VMware ESX 4.0.0 build-398348

no doubt I am on 4.0.0.  I have my support ticket opened now, I was stuck waiting for me to be added to our support contract, I have no entitlements until just now.

Thanks,

Michael

0 Kudos
TUMichaelF
Contributor
Contributor
Jump to solution

Spent 4 hours working with support, in the end the solution was... Re-install.

0 Kudos
admin
Immortal
Immortal
Jump to solution

To resolve this issue, run the `ldconfig` command from the service console, and attempt to run esxupdate again.  --wt

0 Kudos
TUMichaelF
Contributor
Contributor
Jump to solution

I have noted this for the future, much appreciated!

0 Kudos