cargex
asked on
Can't connect to VMware vCenter
Hi Guys,
I was connected to the vCenter using the vSphere Client working in one of the new VMs configuration a moment ago and everything looked fine. Just adding some configuration parameters to disable time synchronization between esxi host and vm, then I closed the vSphere Client. I also enabled the ESX Shell in one of the hosts.
Now when I try to connect to the vCenter using the vShpere client all I get is the following error:
vSphere Client could not connect to "x.x.x.x"
The Server took too long to respond. The command timed out.
The network connection is fine, I can ping all the 3 ESXi hosts, and the vCenter.
Any Ideas as to what might be happening?
I was connected to the vCenter using the vSphere Client working in one of the new VMs configuration a moment ago and everything looked fine. Just adding some configuration parameters to disable time synchronization between esxi host and vm, then I closed the vSphere Client. I also enabled the ESX Shell in one of the hosts.
Now when I try to connect to the vCenter using the vShpere client all I get is the following error:
vSphere Client could not connect to "x.x.x.x"
The Server took too long to respond. The command timed out.
The network connection is fine, I can ping all the 3 ESXi hosts, and the vCenter.
Any Ideas as to what might be happening?
This sounds a lot like your last issue. Can you please provide us what version of vCenter you are running?
Also, are you using the vSphere client or the Web Interface? Have you tried connected to both?
ASKER
vSphere 6.0
I was trying to connect using the vSphere Client
I had to log in to the ESXi host using the vSphere Client and power off the vCenter Appliance VM.
After I powered on the vCenter Appliance VM again everything began to work.
Isn't this supposed to be Linux?
I've never seen a Linux Server to die like that.
Any ideas as to what might have happened or how can I dig into the issue?
I was trying to connect using the vSphere Client
I had to log in to the ESXi host using the vSphere Client and power off the vCenter Appliance VM.
After I powered on the vCenter Appliance VM again everything began to work.
Isn't this supposed to be Linux?
I've never seen a Linux Server to die like that.
Any ideas as to what might have happened or how can I dig into the issue?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What build of the vcenter 6.0 appliance are you using? May be more current build out with fixes that may be applicable to your environment.
ASKER
Andrew,
I'm very interested on your point about the services running.
I read your article but it specifically talks about upgrading from 5.5 to 6.0
Can you please tell me specifically how to check if the services are running in the vCenter appliance?
I'm very interested on your point about the services running.
I read your article but it specifically talks about upgrading from 5.5 to 6.0
Can you please tell me specifically how to check if the services are running in the vCenter appliance?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Andrew,
Really important information.
Thank you very much.
Really important information.
Thank you very much.
ASKER
command>
I tried to run Linux commands ("ls /etc/init.d") but it doesn't seem to recognize any.
Help please!