I have been testing with ESX 4 U1 and noticed that you cannot connect to the host with web access or the vSphere client until the web access service is manually started. I did see that this was a known issue in the release notes for ESX 4 U1 however KB 1011921 says to set the run level for this service using chkconfig to fix the issue. I have done the following:
Started the service (service vmware-webAccess start)
Set the run level (chkconfig --level 345 vmware-webAccess on)
Verified the service status and run level settings
All is good until the host is rebooted. Then the run levels are all reset and the service has to be started manually.
Is anyone else witnessing this behavior or have any suggestions?
JAMES WOOD | SYSTEMS ADMINISTRATOR | ARIZONA DEPARTMENT OF TRANSPORTATION
Phoenix, Arizona
James Wood, VCP
Senior Systems Administrator | Arizona Department of Transportation | Phoenix, Arizona
