Skip to main content
NetApp Knowledge Base

VMware hostd service become unresponsive with ESXi 6.7 update 3

Views:
3,397
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
san
Last Updated:

Applies to

VMware 6.7 update 3

Issue

  • ESXI host show unresponsive in vCenter
  • hostd service intermittently becomes unresponsive
  • VMkernel log will see alerts the following:

2020-11-03T22:05:00.557Z cpu2:2179102)ALERT: hostd detected to be non-responsive

  • You may observe the following entries preceding the hostd detected to be non-responsive.

 2020-11-03T21:30:38.333Z cpu7:2098766 opID=b3d57165)FS3J: 3146: Aborting txn (0x430aa50d2890) callerID: 0xc1d00002 due to failure pre-committing: Optimistic lock acquired by another host.  
  2020-11-03T21:33:40.220Z cpu7:2097782)DVFilter: 6054: Checking disconnected filters for timeouts
  2020-11-03T21:34:53.733Z cpu6:2202506)DLX: 4330: vol 'datastore', lock at 188628992: [Req mode 1] Checking liveness:
  2020-11-03T21:34:53.733Z cpu6:2202506)[type 10c00002 offset 188628992 v 4266, hb offset 3346432 gen 7313, mode 1, owner 5fa01ff9-a25c7506-a069-00108682abde mtime 544318 num 0 gblnum 0 gblgen 0 gblbrk 0]

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.