I have encountered this error after a clean installation of ESX 4 server on a new HP DL 380 G6. When you access your ESX server through web interface and you try to log in by clicking on the “Log in to Web Access” link, you get the “503 Service Unavailable” error in your web browser. Here is how I solved this issue:
- Log in to the console of the affected ESX server (or through puTTY) and check the status of the vmware-webAccess service by typing: #service vmware-webAccess status
- If the service is not running, start it with: #service vmwware-webAccess start
- If you want to start this service automatically when your ESX server starts, type: #chkconfig – – level 3 vmware-webAccess on
- Now, try again to log in to the Web Access of you ESX server and the issue schould be solved.
Cheers! 🙂
– Marek.Z
Hello everyone! 🙂
My name is Eloise and it made some weeks that I read regularly defaultreasoning.wordpress.com, I found lots of help and I say that as of today is for me to contribute as well.
This is the first time that I post on a forum so I hope this is the right section to post my presentation if I’m wrong I thank in advance a moderator move the topic.
I am 24 years old and live in your country for only eight months, I apologize for the mistakes of language that I do, feel free to correct me.
Otherwise, in life I’m brown and the head I am a true blonde, I have a beautiful 2 year old child and I love football, big cars and playing video games and I own a small website dedicated the seotons.
http://fr-fr.facebook.com/profile/pic.php?oid=AQB52pio4Hxp-LOf8YjjfoY84PYN1VBtDgYCb6_s88wjY1A6fiZAALfG5EMnyKHhOKs&size=normal&usedef=1
my facebook: http://fr-fr.facebook.com/people/Eloise-Baes/100000574781263
That is me in a nutshell.
Hi there,
Thanks for visiting!
Cheers!
– Marek.Z
Helly everyone!
I’m trying to get this to work on ESXi v5 🙂
~ # service vmware-webAccess status
-ash: service: not found
🙁
Can someone help me out? Checked google for solution but couldn’t find one thusfar. Thanks in advance,
Dennis
Hi Dennis,
If I’m correct on this, this service is not a part of the ESXi architecture. It was a part on the ESX classic.
Cheers!
then what is the solution for Esxi architecture if we getting same error
Hi,
It depends. Please refer to KB 2033822 for possible solution.
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2033822
Cheers!