The issue is that the new openssl libraries do not match the (not updated?) hash files which are older:
-r-xr-xr-x 1 root root 1685176 Jul 10 2012 /usr/lib64/libcrypto.so.0.9.8
-r-xr-xr-x 1 root root 343040 Jul 10 2012 /usr/lib64/libssl.so.0.9.8
-rw-r--r-- 1 root root 65 Jan 11 2012 /usr/lib64/.libcrypto.so.0.9.8.hmac
-rw-r--r-- 1 root root 65 Jan 11 2012 /usr/lib64/.libssl.so.0.9.8.hmac
Once you delete (or move) the .hmac files OpenSSL will work fine again, just without the FIPS stuff (I doubt anyone really needs this anyway...). Most likely it is sufficient to delete the .hmac files before running the update from the GUI.
@VMware: I consider this to be a serious bug.
If you run into this AFTER trying to update the appliance, you'll have more trouble waiting even if SSL works again.
If the update did not finish or was interrupted during the long wait time, the postinstall script was not run. Most likely the vpxd will not start with the error message
"Database version id '510' is incompatible with this release of VirtualCenter."
This will also break any attempt to re-install the update, which will result in a "Failed to install updates`(Error while running installation tests)".
Try the following:
- SSH to the appliance
- cd /usr/local/tcserver/vfabric-tc-server-standard/
- check if more than one subdirectory tomcat-6.x and tomcat-7.x exists.
- if yes, de-install the older version of vfabric-tc-server:
rpm -q vfabric-tc-server-standard
rpm -e vfabric-tc-server-standard-2.6.4-1 (in my case)
The reason is that otherwise /usr/lib/vmware-vpx/rpmpatches.sh will fail since some "ls .... | grep ..." statements do not properly check if ls returned more than one result... #bug
- cd /opt/vmware/var/lib/vami/update/data/job/
- cd into the latest subdirectory, which should have the higest number
- run the postinstall script:
./post_install '5.1.0.5300' '5.1.0.10000' 0 (the first one is the old build number, in my case for 5.1.0b)
Ignore any errors.
- update the manifest
./manifest_update
- reboot the appliance
I hope I did not forget any steps I did during the troubleshooting, otherwise let me know in which problems you run, and I'll try to remember. ;-)
This worked for me and saved the vCenter data(base) with the whole configuration.
Oh, and in case you're running the appliance in a home lab don't forget to change the config files to reduce the memory requirements. ;-) Some of them have been overwritten by the update.
http://www.vaspects.com/2013/04/24/minimizing-vcenter-memory-appliance/
Cheers,
Martin