Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

\uD83E\uDD14 Problem

VM start protection fails with timed out error

...

...

This article applies to all JSDR software versions.

Problem

The VM Start Protection task fails with a time out error. Status details indicate disks are not visible on the DRVA.

...

Solution

The above error can happen occur if there is a communication issue between the DRVA and ESXi CIM daemon.

Verify if you see any CIM related error in protected domains tab and from MSA logs.

...

MSA logs - /var/log/vme2/logs/jss-cimclient.log

Code Block
2022-03-31 06:19:43,226 ERROR [Thread-10] (CimClient.java:642) getHostRequestInfo: CIM remote method call failure: 10.40.3.104
javax.wbem.WBEMException: Unable to connect
at org.sblim.cimclient.internal.wbem.WBEMClientCIMXML.transmitRequestWorker(WBEMClientCIMXML.java:1756)
at org.sblim.cimclient.internal.wbem.WBEMClientCIMXML.transmitRequest(WBEMClientCIMXML.java:1687)
at org.sblim.cimclient.internal.wbem.WBEMClientCIMXML.enumerateInstances(WBEMClientCIMXML.java:1004)
at com.jetstream.jss.platform.client.cim.CimClient.cimEnumerateInstances(CimClient.java:468)
at com.jetstream.jss.platform.client.cim.CimClient.cimEnumerateInstances(CimClient.java:447)
at com.jetstream.jss.platform.client.cim.CimClient.getHostRequestInfo(CimClient.java:601)
at com.jetstream.jss.task.systemtask.HostServiceRequestCollectionTask.collectHostRequestsAndUpdateCache(HostServiceRequestCollectionTask.java:150)
at com.jetstream.jss.task.systemtask.HostServiceRequestCollectionTask.fetchHostServiceRequests(HostServiceRequestCollectionTask.java:109)
at com.jetstream.jss.task.systemtask.HostServiceRequestCollectionTask.processNextStep(HostServiceRequestCollectionTask.java:68)
at com.jetstream.jss.task.Executor$TransientTaskRunnable.run(Executor.java:419)
Caused by: java.net.ConnectException: Connection refused (Connection refused)

...

  • Check under the Protected Domains tab and within the MSA logs to see if there are any CIM-related errors.

    • Fix any discovered errors then retry VM start protection again.

...

Info

In the above example of the MSA log, a communication failure is identified which needs to be corrected by restarting CIM services on ESXi hosts.

...

  • In the AVS environment, this can be accomplishing by executing the Run-Command Resolve-ClusterIssue.

  • Start VM protection again and the task should proceed without the error.

Infonote

ESXi 6.7 has is known to have CIM-related issues and most of these are that can cause the above issue. This type of problem is typically not seen in ESXi 7.0 & later.

...