Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am running a Fedora 14 server with VMware Server 2. When I initially installed VMware Server, everything was working fine. This included accessing Web Access on port 8333 (https) and 8222 (http).

I had to perform a server restart and afterwards, the Web Access is not starting when I run:

/etc/init.d/vmware-mgmt start

The VMware Server Host Agent starts [OK], but the Web Access has no [OK] or [Failed] next to it.

I also checked ports 8333 and 8222 by running a netstat, but neither are showing up.

In addition, I checked the proxy.log and client.log files in the following directory:


The proxy.log doesn't have entries in it past 9-18-2012, which is the date the server restart occurred. The client.log is empty.

I not sure what is causing this issue or what log files will be helpful in narrowing down the cause. I could re-install VMware Server, but I would like to narrow down the cause as it could occur again with the new re-installed environment.

share|improve this question
Have you looked in /etc/init.d/vmware-mgmt to find the commands that start the Web Access and run them by hand? Sometimes init scripts will run programs and redirect their output to /dev/null. Trying to start the process manually should let you see any output that it generates and which specific command is failing. –  Starfish Sep 27 '12 at 0:43
You know this software hasn't been supported for over a year right? –  Chopper3 Sep 27 '12 at 6:07
@Starfish Thanks for the suggestion. I checked vmware-mgmt for the commands that start Web Access and it starts without issue. However, it is only binding ports 8308 (http) and 8009 (ajp). Ports 8222 and 8333 are not being bound. I'm trying to find how those ports are bound, but I'm finding there isn't much documentation around this aside from running vmware-config.pl, which is no longer asking which ports to use for http and https. I've attempted to read the script to find out why this may be, but I am not familiar enough with perl syntax to see what is really going on. –  FusionHammer Sep 27 '12 at 20:13
@Chopper3 Yes, I know it is no longer supported. It's not used in a production environment, so I decided to go with it since I am more familiar with this product than other solutions. –  FusionHammer Sep 27 '12 at 20:20
I uninstalled and re-installed VMware Server and the same problem persists. Anyone familiar with how ports 8333 and 8222 are bound by VMware? –  FusionHammer Sep 28 '12 at 0:08

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.