I just had a blade stop responding to vCenter. I have updae manager running for the cluster. It would seem that some component of the upgrade went wrong.
***********************
# uptime
08:32:35 up 205 days, 18:49, 2 users, load average: 6.01, 6.00, 5.60
#
# vmware-webAccess
/usr/sbin/vmware-webAccess: line 1: cd: /usr/lib/vmware/webAccess/tomcat/apache-tomcat-6.0.14/bin: No such file or directory
/usr/sbin/vmware-webAccess: line 5: ./startup.sh: No such file or directory
# cd /usr/lib/vmware/webAccess/tomcat/apache-tomcat-6.0.14/
-bash: cd: /usr/lib/vmware/webAccess/tomcat/apache-tomcat-6.0.14/: No such file or directory
# cd /usr/lib/vmware/webAccess/tomcat/
# ls
apache-tomcat-6.0.16
# cd apache-tomcat-6.0.16/
#
**********************
I reboot the node, same issue.
Is their a way to fix this without evacuation of all VMs and re-install?
Has anyone else had issues where the HTTP service is upgraded and has this issue?
