I just wanted to access my ESX 4.0 server via https. Unfortunately I received a “503 Service unavailable” error. First I checked if the service was running:
service vmware-webAccess status
It wasn’t running so I started it:
service vmware-webAccess start
But why did this happen? Well page 7 of the vSphere Web Access Guide revealed it. As of ESX 4.0 this service has been disabled by default. If you do however need it on a regular base it might be a smart thing to enable it:
chkconfig --level 345 vmware-webAccess on
Duncan,
I’ve had a few customers ask about this over the last few weeks. Now I have a post to point them at! Thanks.
Duncan,
Thanks! I’ve been poking around with Web Access and found it really crappy. Not sure if that is just my lab or if there are some serious issues with the product. It has artifacts of Blank (i.e. no named) Datacenters along with the real Datacenter. Clicking on any item in the inventory never actually shows the item it just sits there and never even times out or errors out. Will test with a new fresh install. JUst wondering if you were seeing any of the same.
Thanks,
Lane (aka @wolfbrthr)
Make that
chkconfig –level 345 vmware-webAccess on
Doh, why is your blog stripping the 2nd “-” from “–“? i.e. it’s chkconfig dashdashlevel 345 …
I don’t know why… but it’s been fixed in the post.
A little bit offtopic, but what are the hardware specs of your home esx server?
GO VIRTUAL!
VMware Workstation 6.5.2 on a Lenovo X61 with 4GB of memory 🙂
I ran into this a while back as well: http://professionalvmware.com/2009/05/28/vsphere-4-web-ui-fail-auto-starting-the-vsphere-4-web-service/
Glad to see I’m not the only one.