3.0.1 to 3.0.2 upgrade problem

[Digitus]

Hi

I'm just testing the upgrade of ESX 3.0.1 to ESX 3.0.2 and I'm getting an error when running the ESX update.

\[root@esx1 52542]# esxupdate -n update

INFO: No repository URL specified, going with file:/root/52542

INFO: Configuring...

INFO: Preparing to install VMware ESX Server 3.0.2-52542...

INFO: Pre-install packages up-to-date

INFO: Running yum upgrade...

INFO: | Gathering header information file(s) from server(s)

INFO: | Server: Esxupdate-compatible repository for VMware ESX Server 3.0.2-52542

INFO: | Finding updated packages

INFO: | Downloading needed headers

INFO: | Finding obsoleted packages

INFO: | Resolving dependencies

INFO: | .Package kernel-module-cifs-2.4.21-37.0.2.ELvmnix needs /boot/vmlinux-2.4.21-37.0.2.ELvmnix, this is not available.

INFO: yum upgrade failed for \['VMware-esx-drivers-scsi-qla4022.i386', 'VMware-esx-drivers-net-e1000.i386', 'VMware-esx-drivers-net-e100.i386', 'util-linux.i386', 'VMware-esx-drivers-scsi-adp94xx.i386', 'zlib.i386', 'mount.i386', 'glibc-common.i386', 'VMware-esx-lnxcfg.i386', 'vmware-hwdata.noarch', 'VMware-esx-drivers-scsi-aic79xx.i386', 'VMware-esx-docs.i386', 'info.i386', 'VMware-esx-drivers-scsi-qla2300-v7.07.i386', 'iputils.i386', 'tzdata.noarch', 'krb5-libs.i386', 'net-snmp-utils.i386', 'kernel-source.i386', 'net-snmp.i386', 'gcc.i386', 'groff.i386', 'VMware-esx-drivers-scsi-mptscsi_2xx.i386', 'openssh-clients.i386', 'VMware-webCenter-esx.i386', 'VMware-esx-drivers-net-3c90x.i386', 'VMware-esx-drivers-net-tg3.i386', 'tar.i386', 'psmisc.i386', 'VMware-esx-drivers-scsi-vmkiscsi.i386', 'perl.i386', 'VMware-esx-drivers-net-bcm5700.i386', 'glibc-devel.i386', 'VMware-cim-esx.i386', 'VMware-esx-drivers-scsi-aacraid_esx30.i386', 'libgcc.i386', 'VMware-esx-drivers-net-bnx2.i386', 'VMware-esx-drivers-scsi-ips.i386', 'VMware-esx-drivers-scsi-megaraid2.i386', 'glibc-headers.i386', 'samba-common.i386', 'initscripts.i386', 'VMware-esx-drivers-block-DAC960.i386', 'compat-db.i386', 'VMware-esx-iscsi.i386', 'libstdc++.i386', 'VMware-esx-drivers-scsi-qla2200-v7.07.i386', 'pciutils.i386', 'glibc.i686', 'man-pages.noarch', 'gzip.i386', 'coreutils.i386', 'vixie-cron.i386', 'logrotate.i386', 'tcl.i386', 'VMware-esx-vmx.i386', 'VMware-esx-backuptools.i386', 'perl-XML-Parser.i386', 'VMware-esx-drivers-scsi-qla4010.i386', 'VMware-esx-vmkctl.i386', 'findutils.i386', 'kernel-vmnix.i686', 'VMware-esx-drivers-scsi-aic7xxx.i386', 'sed.i386', 'VMware-esx-uwlibs.i386', 'VMware-hostd-esx.i386', 'VMware-esx-drivers-block-cciss.i386', 'openldap.i386', 'openssl.i686', 'openssh-server.i386', 'VMware-esx-drivers-scsi-lpfcdd-v732.i386', 'VMware-esx-drivers-scsi-megaraid_sas.i386', 'ftp.i386', 'VMware-esx-apps.i386', 'python.i386', 'bash.i386', 'nscd.i386', 'e2fsprogs.i386', 'VMware-esx-tools.i386', 'yum.noarch', 'VMware-esx-perftools.i386', 'openssh.i386', 'chkconfig.i386', 'openldap-clients.i386', 'kudzu.i386', 'losetup.i386', 'file.i386', 'net-snmp-libs.i386', 'VMware-esx-srvrmgmt.i386', 'bind-libs.i386', 'bind-utils.i386', 'ypbind.i386', 'VMware-esx-drivers-net-pcnet32.i386', 'kernel-utils.i386', 'cpp.i386', 'pam_passwdqc.i386', 'gdb.i386', 'shadow-utils.i386', 'parted.i386', 'samba-client.i386', 'man.i386', 'procps.i386', 'popt.i386', 'VMware-esx-vmkernel.i386', 'pam.i386', 'grep.i386', 'binutils.i386']

INFO: --- TOTALS: 0 packages installed, 108 pending or failed, 0 removed, 0 excluded ---

INFO: Yum upgrade failed, correct the problem and retry the update.

I've extracted the .tar ball to a local folder under root and run the esxupate directly under there, as well as trying to run it from an FTP url. I still get the same error...

I've checked that kernel-module-cifs-2.4.21-37.0.2.ELvmnix is installed and it is.

Has anyone seen this before and know how to fix it?

Best regards,

Digitus

[mkhwc]

I got the same error when I first tried to run my upgrade. I had to copy the entire tar.gz to the esx host then to extract the compressed tar archive run:

\# tar -xvzf esx-upgrade-from-esx3-3.0.2-52542.tar.gz

Change to the directory it creates and run the esxupdate - n update command and it completed successfully.

hope this helps

[Digitus]

Thanks, for that, but I've tried that as well (that is what the print out is from).

Both methods fail with the same error...

Digitus

[einstein-a-go-g]

Something is odd here with the upgrade 3.0.2, I've just tried to upgrade our test ESX hosts before applying to production:-

I've scp-ed the tarball to the host esx server as usuaul, un-tar-ed using

checked download using md5, md5 checksums match on download, and after transfer to esx host.

un-tar tar zxvf esx-upgrade-from-esx3-3.0.2-52542.tar.gz in /tmp

run esxupdate -n update in the directory /tmp

and get this:-

\[root@esx001 /tmp]# cd 52542/

\[root@esx001 /tmp/52542]# esxupdate -n update

INFO: No repository URL specified, going with file:/tmp/52542

INFO: Configuring...

INFO: Preparing to install VMware ESX Server 3.0.2-52542...

INFO: Pre-install packages up-to-date

INFO: Running yum upgrade...

INFO: | Gathering header information file(s) from server(s)

INFO: | Server: Esxupdate-compatible repository for VMware ESX Server 3.0.2-52542

INFO: | Finding updated packages

INFO: | Downloading needed headers

INFO: | Finding obsoleted packages

INFO: | Resolving dependencies

INFO: | Dependencies resolved

INFO: | I will do the following:

INFO: | \[update: VMware-esx-drivers-scsi-aacraid_esx30 1.1.5.1vmw-52542.i386]

INFO: | \[update: VMware-hostd-esx 3.0.2-52542.i386]

INFO: | \[update: VMware-esx-tools 3.0.2-52542.i386]

INFO: | \[update: bind-utils 20:9.2.4-14_EL3.i386]

INFO: | \[update: losetup 2.11y-31.18vmw.i386]

INFO: | \[update: e2fsprogs 1.32-15.3.i386]

INFO: | \[update: VMware-esx-drivers-net-bnx2 1.4.51b-52542.i386]

INFO: | \[update: samba-client 3.0.9-1.3E.13.2vmw.i386]

INFO: | \[update: pam_passwdqc 1.0.2-1vmw.i386]

INFO: | \[update: openldap-clients 2.0.27-22.i386]

INFO: | \[update: pam 0.75-69.i386]

INFO: | \[update: vixie-cron 4.1-19.EL3.i386]

INFO: | \[update: VMware-esx-vmkctl 3.0.2-52542.i386]

INFO: | \[update: compat-db 4.0.14-5.3.i386]

INFO: | \[update: VMware-esx-apps 3.0.2-52542.i386]

INFO: | \[update: parted 1.6.3-48vmw2.i386]

INFO: | \[update: net-snmp-utils 5.0.9-2.30E.20.i386]

INFO: | \[update: net-snmp-libs 5.0.9-2.30E.20.i386]

INFO: | \[update: VMware-esx-drivers-block-cciss 2.4.64.1vmw-52542.i386]

INFO: | \[update: VMware-esx-drivers-scsi-mptscsi_2xx 2.6.48.6vmw-52542.i386]

INFO: | \[update: grep 2.5.1-24.6.i386]

INFO: | \[update: net-snmp 5.0.9-2.30E.20.i386]

INFO: | \[update: glibc-devel 2.3.2-95.44.i386]

INFO: | \[update: VMware-esx-drivers-scsi-qla4010 3.24-52542.i386]

INFO: | \[update: VMware-esx-drivers-net-e1000 7.3.15.1vmw-52542.i386]

INFO: | \[update: util-linux 2.11y-31.18vmw.i386]

INFO: | \[update: VMware-esx-drivers-scsi-megaraid_sas 0.0.2-52542.i386]

INFO: | \[update: VMware-esx-drivers-net-tg3 3.43b.1vmw-52542.i386]

INFO: | \[update: VMware-esx-drivers-scsi-adp94xx 0.0.5-52542.i386]

INFO: | \[update: vmware-hwdata 1.00-7vmw.noarch]

INFO: | \[update: binutils 2.14.90.0.4-42.i386]

INFO: | \[update: man-pages 1.60-5.rhel3.noarch]

INFO: | \[update: VMware-esx-uwlibs 3.0.2-52542.i386]

INFO: | \[update: krb5-libs 1.2.7-61.i386]

INFO: | \[update: VMware-esx-srvrmgmt 3.0.2-52542.i386]

INFO: | \[update: VMware-esx-drivers-scsi-megaraid2 2.10.7-52542.i386]

INFO: | \[update: file 3.39-9.EL3.4.i386]

INFO: | \[update: glibc 2.3.2-95.44.i686]

INFO: | \[update: procps 2.0.17-13.10.i386]

INFO: | \[update: VMware-esx-drivers-net-e100 2.3.40-52542.i386]

INFO: | \[update: VMware-esx-drivers-scsi-qla4022 3.24-52542.i386]

INFO: | \[update: VMware-esx-drivers-net-pcnet32 1.30c-52542.i386]

INFO: | \[update: libstdc++ 3.2.3-56.i386]

INFO: | \[update: VMware-esx-drivers-block-DAC960 2.4.11-52542.i386]

INFO: | \[update: ypbind 3:1.12-5.21.9.i386]

INFO: | \[update: kernel-source 2.4.21-47.0.1.EL.52542.i386]

INFO: | \[update: logrotate 3.6.9-2.RHEL3.i386]

INFO: | \[update: VMware-esx-drivers-scsi-qla2200-v7.07 7.7.4.2vmw-52542.i386]

INFO: | \[update: perl 2:5.8.0-94.EL3.i386]

INFO: | \[update: chkconfig 1.3.13.4-0.3.i386]

INFO: | \[update: ftp 0.17-17.2.i386]

INFO: | \[update: pciutils 2.1.10-7.EL3.1.i386]

INFO: | \[update: VMware-esx-drivers-net-bcm5700 7.3.5-52542.i386]

INFO: | \[update: mount 2.11y-31.18vmw.i386]

INFO: | \[update: shadow-utils 2:4.0.3-26.RHEL3.i386]

INFO: | \[update: initscripts 7.31.31.EL-1vmw.i386]

INFO: | \[update: bind-libs 20:9.2.4-14_EL3.i386]

INFO: | \[update: cpp 3.2.3-56.i386]

INFO: | \[update: kernel-vmnix 2.4.21-47.0.1.EL.52542.i686]

INFO: | \[update: psmisc 21.3-2.1.i386]

INFO: | \[update: VMware-esx-iscsi 3.0.2-52542.i386]

INFO: | \[update: findutils 1:4.1.7-9.1.i386]

INFO: | \[update: kernel-utils 1:2.4-8.37.15.i386]

INFO: | \[update: popt 1.8.2-30_nonptl.i386]

INFO: | \[update: VMware-esx-drivers-scsi-ips 7.10.17.1vmw-52542.i386]

INFO: | \[update: VMware-webCenter-esx 2.0.2-50614.i386]

INFO: | \[update: bash 2.05b-41.7.i386]

INFO: | \[update: iputils 20020927-11.30.5vmw.i386]

INFO: | \[update: perl-XML-Parser 2.31-16.EL3.i386]

INFO: | \[update: VMware-esx-vmx 3.0.2-52542.i386]

INFO: | \[update: man 1.5k-13.rhel3.i386]

INFO: | \[update: samba-common 3.0.9-1.3E.13.2vmw.i386]

INFO: | \[update: nscd 2.3.2-95.44.i386]

INFO: | \[update: sed 4.0.7-8.EL3.i386]

INFO: | \[update: glibc-headers 2.3.2-95.44.i386]

INFO: | \[update: VMware-esx-drivers-scsi-aic79xx 6.3.9-52542.i386]

INFO: | \[update: gcc 3.2.3-56.i386]

INFO: | \[update: VMware-esx-lnxcfg 3.0.2-52542.i386]

INFO: | \[update: VMware-esx-drivers-scsi-lpfcdd-v732 7.3.2.4vmw-52542.i386]

INFO: | \[update: VMware-esx-drivers-scsi-vmkiscsi 3.4.2-52542.i386]

INFO: | \[update: zlib 1.1.4-10.EL3.i386]

INFO: | \[update: kudzu 1.1.22.15-3vmw.i386]

INFO: | \[update: coreutils 4.5.3-28.4.i386]

INFO: | \[update: VMware-esx-drivers-net-3c90x 1.0.2-52542.i386]

INFO: | \[update: VMware-esx-docs 3.0.2-52542.i386]

INFO: | \[update: VMware-esx-drivers-scsi-aic7xxx 6.3.9-52542.i386]

INFO: | \[update: openldap 2.0.27-22.i386]

INFO: | \[update: libgcc 3.2.3-56.i386]

INFO: | \[update: VMware-esx-vmkernel 3.0.2-52542.i386]

INFO: | \[update: gdb 6.3.0.0-1.132.EL3.i386]

INFO: | \[update: VMware-cim-esx 3.0.2-52542.i386]

INFO: | \[update: glibc-common 2.3.2-95.44.i386]

INFO: | \[update: VMware-esx-perftools 3.0.2-52542.i386]

INFO: | \[update: groff 1.18.1-28.EL3.3.i386]

INFO: | \[update: yum 2.0.7-4vmw.noarch]

INFO: | \[update: VMware-esx-drivers-scsi-qla2300-v7.07 7.7.4.2vmw-52542.i386]

INFO: | \[update: tcl 8.3.5-92.7.i386]

INFO: | \[update: VMware-esx-backuptools 3.0.2-52542.i386]

INFO: | Downloading Packages

INFO: | Getting VMware-esx-drivers-scsi-aacraid_esx30-1.1.5.1vmw-52542.i386.rpm

INFO: | Getting VMware-hostd-esx-3.0.2-52542.i386.rpm

INFO: | error: rpmts_HdrFromFdno: MD5 digest: BAD Expected(c375129084b4e5ac4f1d418152070d1f) != (5806098361a94a1e6abaf2e00a9b7727)

INFO: | error: rpmts_HdrFromFdno: MD5 digest: BAD Expected(c375129084b4e5ac4f1d418152070d1f) != (5806098361a94a1e6abaf2e00a9b7727)

INFO: | error: rpmts_HdrFromFdno: MD5 digest: BAD Expected(c375129084b4e5ac4f1d418152070d1f) != (5806098361a94a1e6abaf2e00a9b7727)

INFO: | error: rpmts_HdrFromFdno: MD5 digest: BAD Expected(c375129084b4e5ac4f1d418152070d1f) != (5806098361a94a1e6abaf2e00a9b7727)

INFO: | error: rpmts_HdrFromFdno: MD5 digest: BAD Expected(c375129084b4e5ac4f1d418152070d1f) != (5806098361a94a1e6abaf2e00a9b7727)

INFO: | error: rpmts_HdrFromFdno: MD5 digest: BAD Expected(c375129084b4e5ac4f1d418152070d1f) != (5806098361a94a1e6abaf2e00a9b7727)

INFO: | retrygrab() failed for:

INFO: | file:/tmp/52542/VMware-hostd-esx-3.0.2-52542.i386.rpm

INFO: | Executing failover method

INFO: | failover: out of servers to try

INFO: | Error getting file file:/tmp/52542/VMware-hostd-esx-3.0.2-52542.i386.rpm

INFO: | \[Errno -1] RPM /tmp/52542/VMware-hostd-esx-3.0.2-52542.i386.rpm fails md5 check

INFO: yum upgrade failed for \['VMware-esx-drivers-scsi-qla4022.i386', 'VMware-esx-drivers-net-e1000.i386', 'VMware-esx-drivers-net-e100.i386', 'util-linux.i386', 'VMware-esx-drivers-scsi-adp94xx.i386', 'zlib.i386', 'mount.i386', 'glibc-common.i386', 'VMware-esx-lnxcfg.i386', 'vmware-hwdata.noarch', 'VMware-esx-drivers-scsi-aic79xx.i386', 'VMware-esx-docs.i386', 'VMware-esx-drivers-scsi-qla2300-v7.07.i386', 'iputils.i386', 'krb5-libs.i386', 'net-snmp-utils.i386', 'kernel-source.i386', 'net-snmp.i386', 'gcc.i386', 'groff.i386', 'VMware-esx-drivers-scsi-mptscsi_2xx.i386', 'VMware-webCenter-esx.i386', 'VMware-esx-drivers-net-3c90x.i386', 'VMware-esx-drivers-net-tg3.i386', 'psmisc.i386', 'VMware-esx-drivers-scsi-vmkiscsi.i386', 'perl.i386', 'VMware-esx-drivers-net-bcm5700.i386', 'glibc-devel.i386', 'VMware-cim-esx.i386', 'VMware-esx-drivers-scsi-aacraid_esx30.i386', 'libgcc.i386', 'VMware-esx-drivers-net-bnx2.i386', 'VMware-esx-drivers-scsi-ips.i386', 'VMware-esx-drivers-scsi-megaraid2.i386', 'glibc-headers.i386', 'samba-common.i386', 'initscripts.i386', 'VMware-esx-drivers-block-DAC960.i386', 'compat-db.i386', 'VMware-esx-iscsi.i386', 'libstdc++.i386', 'VMware-esx-drivers-scsi-qla2200-v7.07.i386', 'pciutils.i386', 'glibc.i686', 'man-pages.noarch', 'coreutils.i386', 'vixie-cron.i386', 'logrotate.i386', 'tcl.i386', 'VMware-esx-vmx.i386', 'VMware-esx-backuptools.i386', 'perl-XML-Parser.i386', 'VMware-esx-drivers-scsi-qla4010.i386', 'VMware-esx-vmkctl.i386', 'findutils.i386', 'kernel-vmnix.i686', 'VMware-esx-drivers-scsi-aic7xxx.i386', 'sed.i386', 'VMware-esx-uwlibs.i386', 'VMware-hostd-esx.i386', 'VMware-esx-drivers-block-cciss.i386', 'openldap.i386', 'VMware-esx-drivers-scsi-lpfcdd-v732.i386', 'VMware-esx-drivers-scsi-megaraid_sas.i386', 'ftp.i386', 'VMware-esx-apps.i386', 'bash.i386', 'nscd.i386', 'e2fsprogs.i386', 'VMware-esx-tools.i386', 'yum.noarch', 'VMware-esx-perftools.i386', 'chkconfig.i386', 'openldap-clients.i386', 'kudzu.i386', 'losetup.i386', 'file.i386', 'net-snmp-libs.i386', 'VMware-esx-srvrmgmt.i386', 'bind-libs.i386', 'bind-utils.i386', 'ypbind.i386', 'VMware-esx-drivers-net-pcnet32.i386', 'kernel-utils.i386', 'cpp.i386', 'pam_passwdqc.i386', 'gdb.i386', 'shadow-utils.i386', 'parted.i386', 'samba-client.i386', 'man.i386', 'procps.i386', 'popt.i386', 'VMware-esx-vmkernel.i386', 'pam.i386', 'grep.i386', 'binutils.i386']

INFO: --- TOTALS: 0 packages installed, 99 pending or failed, 0 removed, 0 excluded ---

INFO: Yum upgrade failed, correct the problem and retry the update.

any ideas?

It was only when I was typing this post, I remembered!

why was I copying the update to /tmp and not /var/updates as recommended by VMware!

Copied to /var/updates and re-ran upgrade it's currently on 57/196 updates.

So I think it's fixed!

Message was edited by:

einstein-a-go-go

[einstein-a-go-g]

this was the issue copy to /var/updates

esx 3.0.1 successfully upgraded to esx 3.0.2.

[Digitus]

The error you have is different to the one I posted, and thus it's not the same issue. However I tried to copy the install to /var/updates and then re-run it, but I still get the same error as I did before.

Digitus

[EdDotCom]

We have also run into the exact same problem upgrading a lab ESX 3.01 server using the 3.02 tarball copied to /var/updates using the esxupdate update command. Has anyone made any headway on a resolution to this?

[conradsia]

I got the same error and instead of trying to solve it I just used the CD and ran the upgrade.

[acr]

Just did a load of these and figured these sort of issues would occur so removed 8 esx from VC, blew VC away and reinstalled, then introduced ESX to VC used VMotion to move guests arround and did each ESX from scratch, VMotioned back, worked like a charm.... never liked upgrades...

[lholling]

I had the same problem but it was because we put a 3rd Party CIFS driver on the Test ESX server that we had.

All I did to correct was to upgrade the server to v3.0.2 using the CD in upgrade mode. Once we did this worked like a charm.

Leonard...

[TiBoReR]

I had the same problem.

I was unzipping the .tar.gz file with winzip in windows and then transferring it to ESX and executing esxupdate - n update.

To resolve the issue, I copy the .tar.gz file into the ESX and then do a tar -xvzf filename.tar.gz and execute esxupdate -n update in the folder created.

[RParker]

This happened to me, just use the CD instead.

Nice thing about the CD, the server doesn't need to be maintenance mode before hand, and when the machine is done, it reboots, and all the VM's come up (provided you have them set to Auto).

I think I like the CD better than the esxupdate for this anyway...

[Digitus]

Thanks for all contributions to this. In the end we never found out how to fix the actuall issue, but an upgrade using the CD did work as suggested by a lot of you. I've also upgraded a number of other hosts (18 in tota) and none of them had the issue.

It's possible that one of the other admins used an RPM package manager (instead of esxupdate) to install a patch some time ago and that this is the cause. However that is not verified...

Best regards,

Digitus

[skinnieh]

Did this host ever had any host faults?

Host disconnected from Virtual Center, no means to get onto the console or a ssh telnet session etc etc? Or, using VMWare Convertor to this host resulted in previously mentioned problems?

I have the same issue and i am suspecting hardware problems with my host.

In the mean time i will use the CD as well.

Message was edited by:

skinnieh