Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
An ESXi/ESX host's status is Not Responding or Disconnected in vCenter Server. The host stops accepting connections from the vSphere Client. The /var/log/vmkernel log file contains errors similar to: Feb 22 19:01:30 vm10 vmkernel: 142:04:13:17.468 cpu7:4212)ata_scsi_abort: ap 0x41000b870e88, cmd 0x41000e03b4c0, FAILEDFeb 22 19:01:30 vm10 vmkernel: 142:04:13:17.468 cpu7:4212)WARNING: SCSILinuxAbortCommands Failed, Driver ata_piix, for vmhba3Feb 22 19:01:30 vm10 vmkernel: 142:04:13:17.468 cpu7:4212)WARNING: ScsiPath: 4969: Set retry timeout for failed TaskMgmt abort for CmdSN 0x0, status Failure, path vmhba3:C0:T0:L0Feb 22 19:01:32 vm10 vmkernel: 142:04:13:19.468 cpu7:4212)ata_scsi_abort: ap 0x41000b870e88, qc 0x41000b871958, cmd 0x41000e03b4c0, tag 0, flags 1, waiting for completionOrJul 28 21:24:05 vmkernel: 1:23:46:13.014 cpu18:4698)<6>ata1.00: configured for UDMA/100Jul 28 21:24:05 vmkernel: 1:23:46:13.014 cpu18:4698)<6>ata1: EH completeJul 28 21:24:05 vmkernel: 1:23:46:13.023 cpu18:4698)<3>ata1.00: exception Emask 0x40 SAct 0x0 SErr 0x800 action 0x2Jul 28 21:24:05 vmkernel: 1:23:46:13.024 cpu18:4698)<3>ata1.00: (irq_stat 0x40000001)Jul 28 21:24:05 vmkernel: 1:23:46:13.024 cpu18:4698)<3>ata1.00: tag 0 cmd 0xa0 Emask 0x40 stat 0x51 err 0x24 (internal error)Jul 28 21:24:05 vmkernel: 1:23:46:13.343 cpu20:4698)<6>ata1: soft resetting portJul 28 21:24:05 vmkernel: 1:23:46:13.549 cpu20:4698)<6>ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)Or[2009-12-22 11:18:47.129 F66956D0 panic 'HttpNfcSvc'] Another process is listening on port 12001.[2009-12-22 11:18:47.129 F66956D0 panic 'HttpNfcSvc'] Please make sure other instances of hostd are not running.[2009-12-22 11:18:47.129 F66956D0 panic 'HttpNfcSvc'] Failed to initialize http nfc service. The /var/log/vmware/hostd log file contains errors similar to: [2009-12-22 11:18:47.096 F66956D0 info 'HostsvcPlugin'] Plugin initialized[2009-12-22 11:18:47.096 F66956D0 info 'App'] Trying httpnfcsvc[2009-12-22 11:18:47.096 F66956D0 verbose 'App'] Plugin 4 statically linked[2009-12-22 11:18:47.096 F66956D0 verbose 'App'] [DiskLibWrapperLoader_Init] Trying to load disk lib: diskLibWrapper.so,[2009-12-22 11:18:47.110 F66956D0 verbose 'App'] [DiskLibWrapperLoader_Init] Successfully loaded disk lib.[2009-12-22 11:18:47.129 F66956D0 panic 'HttpNfcSvc'] Another process is listening on port 12001.[2009-12-22 11:18:47.129 F66956D0 panic 'HttpNfcSvc'] Please make sure other instances of hostd are not running.[2009-12-22 11:18:47.129 F66956D0 panic 'HttpNfcSvc'] Failed to initialize http nfc service. If you execute the command esxcfg-scsidevs -l, depending on your CD/DVD-ROM drive's model or revision, you see output similar to:mpx.vmhba1:C0:T0:L0Device Type: CD-ROMSize: 0 MBDisplay Name: Local TEAC CD-ROM (mpx.vmhba1:C0:T0:L0)Plugin: NMPConsole Device: /dev/sr0Devfs Path: /vmfs/devices/genscsi/mpx.vmhba1:C0:T0:L0Vendor: TEAC Model: DV-28E-V Revis: C.ABSCSI Level: 5 Is Pseudo: false Status: onIs RDM Capable: false Is Removable: trueIs Local: trueOther Names:vml.0005000000766d686261313a303a30 After restarting hostd via the services.sh restart command, you see errors in the hostd.log file similar to:[2012-08-31 14:31:47.159 FFBAAEF0 info 'HostsvcPlugin'] Plugin initialized[2012-08-31 14:31:47.159 FFBAAEF0 info 'App'] Trying httpnfcsvc[2012-08-31 14:31:47.160 FFBAAEF0 verbose 'App'] Plugin 4 statically linked[2012-08-31 14:31:47.160 FFBAAEF0 verbose 'App'] Initializing in-process DiskLibWrapperLoader[2012-08-31 14:31:47.161 FFBAAEF0 panic 'HttpNfcSvc'] Another process is listening on port 12001.[2012-08-31 14:31:47.161 FFBAAEF0 panic 'HttpNfcSvc'] Please make sure other instances of hostd are not running.[2012-08-31 14:31:47.161 FFBAAEF0 panic 'HttpNfcSvc'] Failed to initialize http nfc service.
In ESXi/ESX 4.x, this issue can occasionally occur if the ESXi/ESX host is physically connected to a TEAC DV-28 series CD/DVD-ROM drive. For more information, see Known Issues in the VMware ESX or ESXi 4.0 Release Notes. To work around this issue, use one of these options: Upgrade the CD/DVD-ROM drive firmware to the latest version available Replace the CD/DVD-ROM drive with a different model Disable the CD/DVD-ROM drive within the BIOS of the ESXi/ESX host
Notes: If the two workarounds above are not successful, place a CD/DVD disk in the device, and verify if the log spew and host disconnection issues are addressed. This issue has been seen when hostd is not running on the ESXi/ESX host, therefore ensure that this service is running. For more information on checking this service, see Troubleshooting vmware-hostd service if it fails or stops responding on an ESX/ESXi host (1002849). For translated versions of this article, see: Español: ESX o ESXi aparece en estado: Not Responding, para vCenter Server debido a problemas de firmware de la unidad CD/DVD-ROM (2000468)Troubleshooting vmware-hostd service if it fails or stops responding on an ESX/ESXi hostESX o ESXi aparece en estado: Not Responding, para vCenter Server debido a problemas de firmware de la unidad CD/DVD-ROMCD/DVD-ROM ドライブのファームウェア問題のために vCenter Server に ESXi/ESX ホストが「Not Responding」として表示される由于 CD/DVD-ROM 驱动器固件问题，ESXi/ESX 主机在 vCenter Server 中显示为“无响应”