jaapengel79
MIS
Hi,
Since this morning, we're receiving a "511 Error connecting to /usr/sbin/vmware-serverd process".
The vmware-serverd process is eating up my CPU's (4 of them on an IBM eServer xSeries 460 w/8Gb RAM) up to 80%, where the httpd is a good second with the remaining 20% up to 60% as well.
When I Google for the error, all I find are articles stating that killing the vmware-serverd process (which respawns automatically) and/or restarting the httpd.vmware process should suffice, alas, it doesn't make any difference..
The VMware version is 2.5.2 and has been running perfectly for quite a while now. No changes were made to the system for at least the past 2 months.
No VM's are running when this occurs; first I tried rebooting the ESX server but the problem occurs when trying to log on through the MUI.
I already raised a call with VMware but due to the fact their timezone and ours are quite different (we're in Holland,Europe and VMware support is somewhere in the USA) it may be more difficult to find a solution anytime soon.. ofcourse we're running some pretty important production servers on it which are needed right away
Since this morning, we're receiving a "511 Error connecting to /usr/sbin/vmware-serverd process".
The vmware-serverd process is eating up my CPU's (4 of them on an IBM eServer xSeries 460 w/8Gb RAM) up to 80%, where the httpd is a good second with the remaining 20% up to 60% as well.
When I Google for the error, all I find are articles stating that killing the vmware-serverd process (which respawns automatically) and/or restarting the httpd.vmware process should suffice, alas, it doesn't make any difference..
The VMware version is 2.5.2 and has been running perfectly for quite a while now. No changes were made to the system for at least the past 2 months.
No VM's are running when this occurs; first I tried rebooting the ESX server but the problem occurs when trying to log on through the MUI.
I already raised a call with VMware but due to the fact their timezone and ours are quite different (we're in Holland,Europe and VMware support is somewhere in the USA) it may be more difficult to find a solution anytime soon.. ofcourse we're running some pretty important production servers on it which are needed right away