One of the the Host (running on Hp Proliant Dl 570) with ESXi4 is disconnected and refuse to connect to the vcenter. I was try to reboot the server. From now, I 'm able to ping the server, connect over ssg, but not over Http and Https. All attemps reconnect failed. From Vcenter, when I try to add the same Ip address, I got the error " Call Datacenter.queryconnection failed.
I need you assistance.
dude, is that datastore shared? if yes nice....remove those vm's from inventory and add the vms in the inventory by browsing the vmx file from the datastore where they are located. OR you can import it, but shutdown your esx host before doing this...
FYI: I am just trying to get your critical ESXi back online, where as other gentleman attempting to restore your VM's. Just to be clear.
Could you please run this for me "chkconfig --list" on the critical host.
Here is the output
~ # chkconfig --list
Thanks. If you compare /etc/opt/vmware/vpxa/vpxa.cfg between 'working' and 'critical', do you see any differences other than the hostkey ? You don't need to send me the output, but let me know the result.
Try /etc/opt/init.d/vmware-vpxa restart, and then paste latest log from /var/log/vmare/vpx/vpxa-xxx.log
All the configuration are the same on vpxa.cfg. You will find attached some log generated on the critical node. When I launch chkconfig --list , the difference is on critical node tsm -ssh and tsm are off, and those parameters are on on the good host. How can I enable tsm-ssh and tsm on the critical node.
two Windows 2003 Servers
what do you mean with status?
Now they are running, we reboot host yesteday
one detail is we dont't have ssh access to host when it disconnects from vcenter
It's as hostd and vpxa daemons on this host go down at the same time and the last solution is to reboot host
no changes on host
now we want to update hostd & vpxa config files to increase size logs so we don't have logs of the day of failure. then we will wait to a new failure and see logs