VMware VSphere Client cannot connect to ESXi virtual host Solutions inexplicably VMware vSphere Client does not connect to an Esxi Virtual host
Workaround:
1, connect the monitor to the ESXi virtual machine, use the account login
2, follow the open those two options to use ssh login , and then the same way as the Linux system Operation
The first step:
650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/53/97/wKioL1RsCVjz-uuvAAH9s0XRSf4865.jpg "title=" 004. PNG "alt=" wkiol1rscvjz-uuvaah9s0xrsf4865.jpg "/>
Step Two:
650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M00/53/99/wKiom1RsCP7iUB72AAEiC2l4ncc393.jpg "title=" 005. PNG "alt=" wkiom1rscp7iub72aaeic2l4ncc393.jpg "/>
3. Use SSH after landing:
Cd/sbin will see service.sh.
Restart in the general case services.sh can be resolved (or the graphical interface Restart Management Agent )
services.sh restart
4. If you restart services.sh error and still cannot connect
Watchdog-hostd:pid FILE/VAR/RUN/VMWARE/WATCHDOG-HOSTD. PID not foundwatchdog-hostd:unable to terminate Watchdog:can ' t find process/etc/init.d/hostd:kill:48: (84046924)-No Such process
/ close hostd hostd process not kill to. (Cause to run the
PS | grep hostd you'll see
123456233 789789789 hostd456123358 789789789 hostd123 789789789 hostd123458985 789789789 hos Td
Indicates that there is a hostd process in the run
/ETC/INIT.D/HOSTD stop
Review the process again
ps | grep hostd 123456233 789789789 hostd456123358 789789789 hostd123 789789789 hostd123458985 789789789 hostd ...
If it still exists, it means that hostd did not kill at all , so manual kill, select any one of the child process ID kill 'll be
Such as:
Kill-9 123458985
And then run
PS | grep hostd
The discovery has not been entered, indicating that hostd has killed
Start the hostd process to
/ETC/INIT.D/HOSTD start
This article is from the "Crazy_sir" blog, make sure to keep this source http://douya.blog.51cto.com/6173221/1579428
VMware VSphere client cannot connect to ESXi virtual host Solutions