Hi,
When I deploy a template to a VM I'm getting a random success but a majority 'Failed to connect to host' error. I've removed and re-added from inventory, converted to VM and back many times, restarted VC services on the hosts but nothing seems to make a difference.
Is this a known problem or have I got something configured incorrectly somewhere? Just wanted to see if I was alone on this - everything else is running okay.
I'm running VC 2.5 64192 and ESX 3.5.0 64607.
Cheers,
merse
I am getting the same issue trying to clone or add a new VM from the VI client connected to our VC console server. The tasks sit there queued for 15 to 20 minutes then time out with that error "Failed to connect to host".
I have seen other posts recommending a restart of the VMware services on the VC console server and/or a reboot of the VC console server. I have tried this and still have the cloning and 'create new vm' task queuing for several minutes and timing out.
I saw another mention of removing the licensing and readding it to the ESX server. I have not tried this yet but it is worth a shot.
Let me know if any of this helps.
Dan
Thanks for the response Dan, sounds like slightly different issues to me but indeed the licenses file is worth a go. Mine times out after around 10 seconds. I only have two ESX servers so I'm going to isolate each server and test to see if it's only one of them responsible... Good luck with yours!
Have you tried restarting the management agents on the ESX side of the house? They try the deployment.
DB
VMware Communities Moderator
I restarted services but now ESX server is not responding and is in disconnected state on VC server console.
The server is running but I cannot reconnect the ESX server to the console.
Other ESX servers are still connected okay.
Don't panic - it'll reconnect. One thing that I have learned with this product (and many other) is to be patient
DB
VMware Communities Moderator
Can you look in the vpxa logs (/var/log/vmware/vpx/vpxa*.log) to see why it keeps crashing?
That's probably not the root cause. Can you check out the other vpxa logs for a different errors at the end of the log?
There were 10 log files vpxa-0.g to vpxa-9.log and they are all essentially the same except for time and so other numbers. I included log 0 and log 9 .
Log for VMware VirtualCenter, pid=27939, version=2.0.2, build=build-50618, option=Release, section=2
Current working directory: /var/log/vmware/vpx
Using system libcrypto, version 90701F
Vmacore::InitSSL: doVersionCheck
= false, handshakeTimeoutUs = 120000000
running for this config file : pid=8263
Stub: Preference_GetBool called
Failed to initialize authd module
functionality. Is vpxa already running?
Failed to do early initialization
Log for VMware VirtualCenter, pid=28432, version=2.0.2, build=build-50618, option=Release, section=2
Current working directory: /var/log/vmware/vpx
Using system libcrypto, version 90701F
Vmacore::InitSSL: doVersionCheck
= false, handshakeTimeoutUs = 120000000
running for this config file : pid=8263
Stub: Preference_GetBool called
Failed to initialize authd module
functionality. Is vpxa already running?
Just to confirm - you're using VC 2.0.2, right? Can you shut down the vpxa process (service vmware-vpxa stop), check that no vpxa processes are running, and then restart it (service vmware-vpxa start). Do you see the same problem?
What's the output for "ps awx | grep vpxa"? Can you try sending those vpxa processes a kill signal (kill -9 <processid>)? Might have to try a reboot if that doesn't work.
Is that the only vpxa process? If it is a zombie it is strange that it is holding onto resources preventing other vpxa instances from running. Can you list the output from running "ps -elf | grep vpxa"
Can you also post the output from running "cat /proc/8263/status"?
2 more commands for you to get output for:
ps -eopid,tt,user,fname,tmout,f,wchan | grep vpxa
cat /proc/8263/stat