cannot connect to VI client

S

syn3rgyz

Gawd
Joined
Jun 14, 2005
Messages
763
I'm an intern working at a firm right now, and I'm the only person on the team with some basic knowledge on VMware. but this is what happened a few days ago.

we restarted the server hosting the VM's because of some hardware issue. After the server started up, i connected through the VI client and began to power the VM's back on. Right after i powered on the second to last VM, i attempted to power on the last VM but the VI client seemed to respond very slow, until a message popped out saying that it just timed out. I tried reconnecting but it kept saying that the server is taking too long to respond. So i went home and tried to connect again the next day but this time it just says connection failed. I am still able to ping the server. While all this was going on, other ppl were still able to remote into the images and work on it.

i looked up the problem and some people recommended that you should restart the mgmt-vmware service. but it might enable the auto poweron/shutdown of the VM's so I tried to find a way to disable that through the service console by going into vimsh. but when I type in vimsh i get a "514 error connecting to hostd-vmbd service instance".

Does anyone have any suggestions or ideas on how to fix this problem? Preferably without interrupting other ppl working on the images. And if they know what caused this problem?
 
do you mean that its not running? i checked if it was running or not and it says yes
 
Don't trust that. take a look at hostd.log - get me the output of that log, so we can see what it's actually doing. Just because the watchdog is running, doesn't mean the agent is :)
 
i don't have access to the server room so i'll have to prob wait for tomorrow or something, thanks though for the quick reply
 
Code: 
Log for VMware ESX Server, pid=1166, version=3.0.1, build=build-60875, option=Release, section=2
[2009-07-07 14:17:26.320 'App' 3076460672 info] Current working directory: /var/log/vmware
[2009-07-07 14:17:26.320 'ThreadPool' 3076460672 verbose] Thread info: Min Io, Max Io, Min Task, Max Task, Max Thread, Keepalive, thread kill, max fds: 2, 200, 2, 10, 25, 8, 600, 2048
[2009-07-07 14:17:26.320 'Handle checker' 3076460672 info] Setting system limit of 2048
[2009-07-07 14:17:26.320 'Handle checker' 3076460672 info] Set system limit to 2048

[2009-07-07 14:17:26.322 'App' 3076460672 info] Closing stdout and stderr.
[2009-07-07 14:17:26.377 'Vmsvc' 3076460672 info] VMServices Plugin initializing
[2009-07-07 14:17:26.393 'BaseLibs' 3076460672 info] System libcrypto.so.0.9.7 library is older than our library (90701F < 90709F)

[2009-07-07 14:17:28.163 'BaseLibs' 3076460672 info] vmxLoaderPath="/usr/lib/vmware/bin/vmkload_app"

[2009-07-07 14:17:28.163 'BaseLibs' 3076460672 info] vmxFilePath="/usr/lib/vmware/bin/vmware-vmx"

[2009-07-07 14:17:28.163 'BaseLibs' 3076460672 info] vmxFilePathDebug="/usr/lib/vmware/bin-debug/vmware-vmx"

[2009-07-07 14:17:28.763 'Vmsvc' 3076460672 info] VM refresh disabled
[2009-07-07 14:17:28.763 'Vmsvc' 3076460672 verbose] Vmsvc Object registered
[2009-07-07 14:17:28.763 'Vmsvc' 3076460672 info] VMServices Plugin initialized
[2009-07-07 14:17:29.208 'NetworkProvider' 3076460672 verbose] Fetch all physical NICs....
[2009-07-07 14:17:29.229 'NetworkProvider' 3076460672 verbose] Successfully fetched physical NIC: vmnic0.
[2009-07-07 14:17:29.238 'NetworkProvider' 3076460672 verbose] Successfully fetched physical NIC: vmnic1.
[2009-07-07 14:17:29.239 'NetworkProvider' 3076460672 verbose] Fetch all virtual switches....
[2009-07-07 14:17:29.396 'NetworkProvider' 3076460672 verbose] Successfully fetched virtual switch: vSwitch0.
[2009-07-07 14:17:29.396 'NetworkProvider' 3076460672 verbose] Fetch all VmKernel NICs....
[2009-07-07 14:17:29.406 'NetworkProvider' 3076460672 verbose] Fetch all Console NICs....
[2009-07-07 14:17:29.420 'NetworkProvider' 3076460672 verbose] Successfully fetched console NIC: vswif0.
[2009-07-07 14:17:29.420 'NetworkProvider' 3076460672 verbose] Obtaining DNS Configuration....
[2009-07-07 14:17:29.423 'NetworkProvider' 3076460672 verbose] Obtaining Route Configuration....
[2009-07-07 14:17:29.424 'HostsvcPlugin' 3076460672 info] Storage data synchronization policy set to invalidate_change
[2009-07-07 14:17:29.424 'Vmfs2UpgradeModeLock' 3076460672 info] [Init] undoAttempts(15), timeoutMsec(2000)
[2009-07-07 14:17:29.424 'FSVolumeProvider' 3076460672 verbose] FSVolumeVmkImplProvider::Start() called
[2009-07-07 14:17:29.424 'FSVolumeProvider' 3076460672 verbose] RefreshVMFSVolumes called
[2009-07-07 14:17:29.725 'FSVolumeProvider' 3076460672 verbose] RefreshVMFSVolumes: refreshed volume, id 4890245e-8531354f-d8fd-00142208b330, name storage1
[2009-07-07 14:17:29.753 'FSVolumeProvider' 3076460672 verbose] RefreshVMFSVolumes: refreshed volume, id 466ae6a7-d35b720c-e836-000bdbe6fd7a, name SMIS Datastore
[2009-07-07 14:17:29.848 'FSVolumeProvider' 3076460672 verbose] RefreshVMFSVolumes: refreshed volume, id 46b354ca-ac81bdfe-1de5-000bdbe6fded, name SMIS TST APP Datastore
[2009-07-07 14:17:29.871 'FSVolumeProvider' 3076460672 verbose] RefreshVMFSVolumes: refreshed volume, id 46698739-d9c90998-d594-0019b9dd7da4, name CARA Datastore
[2009-07-07 14:17:29.872 'FSVolumeProvider' 3076460672 verbose] RefreshNASVolumes called
[2009-07-07 14:17:29.882 'HostsvcPlugin' 3076460672 info] Resource pool configuration: /etc/vmware/hostd/pools.xml
[2009-07-07 14:17:29.893 'HostsvcPlugin' 3076460672 verbose] Looking up VMkernel resource group 'host/user'
[2009-07-07 14:17:30.084 'HostsvcPlugin' 3076460672 info] Datastore auto-refresh is disabled.
[2009-07-07 14:17:30.090 'Hostsvc::DatastoreSystem' 3076460672 info] Datastore alias configuration file is /etc/vmware/hostd/datastores.xml
[2009-07-07 14:17:30.090 'Hostsvc::DatastoreSystem' 3076460672 verbose] ReconcileVMFSDatastores called: refresh = false, rescan = false
[2009-07-07 14:17:30.090 'FSVolumeProvider' 3076460672 verbose] RefreshOneVmfsVolume on /vmfs/volumes/4890245e-8531354f-d8fd-00142208b330
[2009-07-07 14:17:30.107 'DatastoreBrowser' 3076460672 verbose] 4890245e-8531354f-d8fd-00142208b330-datastorebrowser::IntializeCOSDirectory: COS path: /vmimages/
[2009-07-07 14:17:30.107 'DatastoreBrowser' 3076460672 verbose] 4890245e-8531354f-d8fd-00142208b330-datastorebrowser::Constructor
[2009-07-07 14:17:30.107 'Hostsvc::DatastoreSystem' 3076460672 verbose] DiscoverNewDatastores: storage1 created.
[2009-07-07 14:17:30.107 'FSVolumeProvider' 3076460672 verbose] RefreshOneVmfsVolume on /vmfs/volumes/466ae6a7-d35b720c-e836-000bdbe6fd7a
[2009-07-07 14:17:30.115 'DatastoreBrowser' 3076460672 verbose] 466ae6a7-d35b720c-e836-000bdbe6fd7a-datastorebrowser::IntializeCOSDirectory: COS path: /vmimages/
[2009-07-07 14:17:30.115 'DatastoreBrowser' 3076460672 verbose] 466ae6a7-d35b720c-e836-000bdbe6fd7a-datastorebrowser::Constructor
[2009-07-07 14:17:30.115 'Hostsvc::DatastoreSystem' 3076460672 verbose] DiscoverNewDatastores: SMIS Datastore created.
[2009-07-07 14:17:30.115 'FSVolumeProvider' 3076460672 verbose] RefreshOneVmfsVolume on /vmfs/volumes/46b354ca-ac81bdfe-1de5-000bdbe6fded
@
"/var/log/vmware/hostd.log" [readonly] 12476L, 999648C
 
1. Get off of 3.0.1. Totally unsupported and ancient.
2. Yeah, autostart will go nuts if you restart hostd, but you're going to have to - plan a downtime!
3. Get off of 3.0.1. This is really common on that version.
4. Once you're ready -

service vmware-vpxa stop
service vmware-vmkauthd restart
service mgmt-vmware restart
sleep 30
service vmware-vpxa start
 
yea i've been telling my supervisor that we should upgrade, but i've never done an upgrade / fresh install before so i told him that i would not be sure how long the downtime is, in addition to that, it seems that they have not backed up the VM's at all yet, so i'm waiting for that first.
Thanks for the help i'll try it later on at night when everyone goes home and no ones on the VM's
 
what about reconfiguring the storage arrays and the IP addresses, user accounts etc?
 
Shouldn't take you that long. :) ESX is a fast install.

Just, pull the fiber :)
 
fresh. By far. Especially on 3.0.1. Go to 3.5 if you can. You'll have to upgrade VC first.
 
i dont think that we have vcenter, and is there a guide on how to do a fresh install? Is there a unix command that deletes everything that I have to run first?

im also having trouble getting the getstate command to work, if the VMs auto restart after i restart the service and the start command fails im pretty screwed
 
Last edited:
Nope, just throw the disk in and boot off of it :)

Hostd will come back after the restart - if it doesn't, open a support case. We even have weekend support.
 
yea =[ hopefully it does otherwise i'll have 6 ppl asking me why they cant access the VM's and the dev team will be on hold till its back up.
 
You must log in or register to reply here.
Back
Top