ESXi

 View Only
  • 1.  Freezing vm, possible connection to datastore lost.

    Posted Mar 09, 2017 11:56 AM

    While investigating why a VM freezes on a regular bases I couldn't fine anything wrong except that on esxi host in hostd.log I got frequent and irregular messages like the one below.

    Could this be the cause ? an error in communicating with the storage ?

    2017-02-28T07:07:18.640Z error hostd[4DDB0B70] [Originator@6876 sub=SoapAdapter.HTTPService.HttpConnection] Failed to read header on stream <io_obj p:0x4d9d5214, h:36, <TCP '0.0.0.0:0'>, <TCP '0.0.0.0:0'>>: N7Vmacore15SystemExceptionE(Connection reset by peer)

    [LikewiseGetDomainJoinInfo:355] QueryInformation(): ERROR_FILE_NOT_FOUND (2/0):

    2017-02-28T07:08:40.772Z info hostd[4F044B70] [Originator@6876 sub=Solo.Vmomi opID=FCEE8A2E-0002131E-ed14 user=root] Activation [N5Vmomi10ActivationE:0x4f806418] : Invoke done [waitForUpdates] on [vmodl.query.PropertyCollector:ha-property-collector]

    2017-02-28T07:08:40.772Z verbose hostd[4F044B70] [Originator@6876 sub=Solo.Vmomi opID=FCEE8A2E-0002131E-ed14 user=root] Arg version:

    --> "683"

    2017-02-28T07:08:40.772Z info hostd[4F044B70] [Originator@6876 sub=Solo.Vmomi opID=FCEE8A2E-0002131E-ed14 user=root] Throw vmodl.fault.RequestCanceled

    2017-02-28T07:08:40.772Z info hostd[4F044B70] [Originator@6876 sub=Solo.Vmomi opID=FCEE8A2E-0002131E-ed14 user=root] Result:

    --> (vmodl.fault.RequestCanceled) {

    -->    faultCause = (vmodl.MethodFault) null,

    -->    msg = ""

    --> }



  • 2.  RE: Freezing vm, possible connection to datastore lost.

    Posted Mar 10, 2017 07:13 AM

    For VM freeze , required vmware.log

    According hostd logs N7Vmacore15SystemExceptionE(Connection reset by peer)

    This issue is due to the TCP stream between the rhttpproxy and hostd. The rhttpproxy process resets the connection and RetrieveProperties code is called every 5 minutes, causing a log entry to appear every 5 minutes.

    When a call is made to hostd to invoke cancelWaitForUpdates, the PendingRequest is not cleanly removed. When the next PendingRequest occurs after cancelWaitForUpdates, this results in a Connection reset by peer error. You can ignore this error.