Esxcli Error Connect To Localhost Failed

Links Notable Members Current Visitors Recent Activity New Profile Posts Search Search titles only Posted by Member: Separate names with a comma. Newer Than: Search this thread only Search this forum only Display results as threads More...

Ramdisk 'hostd' With Estimated Size Of Already Exists

Recent Posts Menu Log in or Sign up [H]ard|Forum Forums > Bits & Bytes > vobuserlib_init failed with -1 Virtualized Computing > Services Failing on ESXi 5.5 Host - Can't Restart Services Discussion in 'Virtualized Computing' started by KapsZ28, Aug esxcli connect to host 12, 2014. Aug 12, 2014 #1 KapsZ28 2[H]4U Messages: 2,090 Joined: May 29, 2009 One of our servers in a cluster experienced an issue this morning. It can't be managed through vCenter or directly to the https://kb.vmware.com/kb/1015789 server with vSphere Client. SSH is working. I ran "./sbin/services.sh restart" to restart all the services, but there are many failures and I can't get it to the point where it can be managed through vSphere Client or vCenter. Obviously HA is not working since it is no longer in the cluster. All I care about is getting it to the point where I can manage it through vCenter and perform vMotions. Otherwise https://hardforum.com/threads/services-failing-on-esxi-5-5-host-cant-restart-services.1829769/ I am stuck shutting down all the VMs in order to move them. When I run "./sbin/services.sh restart", below is what I am getting. Code: Running vmware-fdm stop Stopping vmware-fdm:success Running xorg stop Running wsman stop Stopping openwsmand Openwsmand is not running. Running sfcbd stop This operation is not supported. Please use /etc/init.d/sfcbd-watchdog stop Running snmpd stop root: snmpd is not running. Running sfcbd-watchdog stop sh: bad number sh: you need to specify whom to kill pkill: failed to kill /sbin/sfcbd (8739627): No such process pkill: Failure pkill: failed to kill /sbin/sfcbd (8739627): No such process pkill: Failure pkill: failed to kill /sbin/sfcbd (8739627): No such process pkill: Failure Connect to localhost failed: Connection failure Connect to localhost failed: Connection failure Running vpxa stop vpxa is not running Connect to localhost failed: Connection failure Running vobd stop vobd is not running Running lacp stop LACP daemon is not running Running memscrubd stop memscrubd is not running Running nscd stop nscd is not running Running smartd stop smartd is not running Running dcbd stop dcbd is not running Running cdp stop cdp is not running Running slpd stop Stopping slpd Running rhttpproxy stop rhttpproxy is not running. Running vsantraced stop watchdog-vsantraced: PID file /var/run/vmware/watchdog-vsantraced.PID does not e xist watchdog-vsantraced: Unable to terminate watchdog: No running watc

Traps One day I tried to open console on a VM and I got the MKS error: I logged into the connect to host and I tried to run an esxcli command and I saw the following: ~ # esxcli network Connect to localhost failed: Connection failure It looks like hostd wasn’t connect to localhost happy. I quickly restarted services: ~ # services.sh restart and that brought back hostd and the MKS errors went away. I didn’t have time to find out what was going on, so I grabbed a log bundle: ~ # vm-support I downloaded the log bundle from the ESXi host and put it on my laptop. Here is the file: [emailprotected]:~/es$ls *.tgz esx-prod-vmware01-2013-08-12--14.06.tgz I extracted the file: [emailprotected]