Hi,
Today when i looked for server status, one of the server was in disconnected state. Tried connecting directly through vsphere client & putty - it didn't help.
When I connected physical console of the esx box and pressing Alt-F1 - it just gave the option to provide user name not for the password. It's completely in the hung state. It's not responded to switch over to other console too (Alt-f2 or f3). So rebooted the server, now it looks fine.
But now I am looking for the root cause of this issue. I found the logs from messages..
<
Apr 11 10:57:22 vu1ess13 xinetd[2984]: START: vmware-authd pid=6425 from=127.0.0.1 Apr 11 10:57:22 vu1ess13 xinetd[2984]: EXIT: vmware-authd status=0 pid=6425 duration=0(sec) Apr 11 10:57:22 vu1ess13 /usr/lib/vmware/bin/vmware-hostd[3211]: Accepted password for user root from 127.0.0.1 Apr 11 10:57:22 vu1ess13 xinetd[2984]: START: vmware-authd pid=6485 from=127.0.0.1 Apr 11 10:57:22 vu1ess13 xinetd[2984]: EXIT: vmware-authd status=0 pid=6485 duration=0(sec) Apr 11 10:57:22 vu1ess13 /usr/lib/vmware/bin/vmware-hostd[3211]: Accepted password for user root from 127.0.0.1 Apr 11 10:57:27 vu1ess13 /usr/lib/vmware/bin/vmware-hostd[3211]: Accepted password for user vpxuser from 127.0.0.1 Apr 11 10:57:38 vu1ess13 last message repeated 2 times Apr 11 11:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 11 11:01:15 vu1ess13 ntpd[3008]: synchronized to 10.67.184.2, stratum 5 Apr 11 11:01:15 vu1ess13 ntpd[3008]: kernel time sync enabled 0001 Apr 11 12:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 11 13:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 11 13:56:54 vu1ess13 sfcb[19666]: INTERNAL StorelibManager::getEnclosureConfig - StorelibManager::getEnclosureConfig:ProcessLibCommandCallfailed;rval=0x12 Apr 11 14:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 11 15:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 11 16:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 11 16:56:41 vu1ess13 sfcb[1626]: INTERNAL StorelibManager::getEnclosureConfig - StorelibManager::getEnclosureConfig:ProcessLibCommandCallfailed;rval=0x12 Apr 11 17:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 11 18:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 11 19:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 11 19:56:27 vu1ess13 sfcb[16012]: INTERNAL StorelibManager::getEnclosureConfig - StorelibManager::getEnclosureConfig:ProcessLibCommandCallfailed;rval=0x12 Apr 11 20:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 11 21:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 11 22:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 11 22:56:13 vu1ess13 sfcb[30296]: INTERNAL StorelibManager::getEnclosureConfig - StorelibManager::getEnclosureConfig:ProcessLibCommandCallfailed;rval=0x12 Apr 11 23:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 12 00:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 12 01:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 12 01:55:59 vu1ess13 sfcb[12171]: INTERNAL StorelibManager::getEnclosureConfig - StorelibManager::getEnclosureConfig:ProcessLibCommandCallfailed;rval=0x12 Apr 12 02:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 12 03:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 12 04:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 12 04:55:45 vu1ess13 sfcb[26692]: INTERNAL StorelibManager::getEnclosureConfig - StorelibManager::getEnclosureConfig:ProcessLibCommandCallfailed;rval=0x12 Apr 12 05:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 12 06:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] Apr 12 07:01:01 vu1ess13 logrotate: ALERT exited abnormally with [1] > This sfcb message continued almost for a week. Any guides & tips to get the root cause is appreciated. Thanks in advance.