Skip to main content

ESXi hostd log spew post VM backup: Block list: Cannot convert disk path (path to vmdk> to real path, skipping.

  Symptoms

  • After the daily VM backup, you notice that one or more ESXi hosts report the below log spew continuously in the /var/log/hostd.log
2020-05-28T01:17:20.907Z warning hostd[2100454] [Originator@6876 sub=Default opID=56ff9f3f-75-f610 user=vpxuser:testdomain\testuser] Block list: Cannot convert disk path /vmfs/volumes/2622ebd8-4b853593/TESTVM/TESTVM-000002.vmdk (/vmfs/volumes/2622ebd8-4b853593/TESTVM/TESTVM-000002.vmdk) to real path, skipping.
  •  In ESXI - /var/log/vpxa.log  reports the below errors during this issue
[context]zKq7AVICAgAAAKBJ9QAZdnB4YQAALE42bGlidm1hY29yZS5zbwAAsL4bAJCcFwHPyP5saWJ2aW0tdHlwZXMuc28AgSLWFwGBgrkTAQK6OQ1saWJ2bW9taS5zbwACbIgRAmeNEQPuQyd2cHhhAANIRicCRbATgcbEMwEDydUvBH7uCWxpYnZweGFwaS10eXBlcy5zbwADrt83A4E+JwO46TYDxvc2A2JNNwC15SgAk+koAKvENgU7fQBsaWJwdGhyZWFkLnNvLjAABn2fDmxpYmMuc28uNgA=[/context]' received while invoking acquireLeaseExt on vim.host.DiskManager:ha-blklist-service
2020-05-28T01:16:10.891Z error vpxa[2108445] [Originator@6876 sub=SoapAdapter opID=7f722a82-41] Method vpxapi.VpxaService.AcquireDiskManagerLeaseExt threw undeclared fault of type vim.fault.LeaseFault
2020-05-28T01:16:10.943Z error vpxa[2100302] [Originator@6876 sub=vpxaVmomi opID=5b1342da-f5] [VpxaClientAdapter::InvokeCommon] Re-throwing method-fault 'N3Vim5Fault10LeaseFault9ExceptionE(Fault cause: vim.fault.LeaseFault
  •  If you are logging to a remote syslog server, you might see the syslog file growing to very large size and might fill up the disk space.
  •  The vmdk referenced in the above message does not exist.
Cause
Due to a race condition in the snapshot consolidation workflow.
Impact / Risks
No impact in restarting the management agents.
Resolution
This is a known issue. Currently there is no resolution.

Workaround
Restart the "hostd" agent on the ESXi host

Comments

Post a Comment

Popular posts from this blog

Error [403] The maximum number of sessions has been exceeded in the H5 client during login or logout

  Symptoms In virgo log, you see messages similar to: [2020-05-19T07:25:45.285Z] [ERROR] http-nio-5090-exec-130 72026859 142953 501051 com.vmware.vise.security.spring.DefaultAuthenticationProvider logout failed for sessionId 142953, clientId 501051 java.lang.IllegalStateException: The specified cardinality of 1..1 for osgi:reference implementing com.vmware.vcenter.apigw.api.ApiGatewaySessionManager in bundle com.vmware.h5ngc requires that exactly one OSGI service satisfies the filtering criteria but no such service was found.         at com.vmware.o6jia.context.ExternalServiceTargetSource.getTarget(ExternalServiceTargetSource.java:99)         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:192)         at com.sun.proxy.$Proxy159.logout(Unknown Source)         at com.vmware.vise.security.spring.DefaultAuthenticationProvider.logoutInternal(DefaultAuthenticationProvider.java:548)         at c
Post a Comment
Read more

Investigating virtual machine file locks on ESXi

      Details Adding an existing virtual machine disk (VMDK) to a virtual machine that is already powered on fails.                 Failed to add disk scsi0:1. Failed to power on scsi0:1   Powering on the virtual machine results in the power on task remaining at 95% indefinitely. Cannot power on the virtual machine after deploying it from a template. Powering on a virtual machine fails with an error: Unable to open Swap File Unable to access a file since it is locked Unable to access a file <filename> since it is locked Unable to access Virtual machine configuration In the /var/log/vmkernel log file, you see entries similar to: WARNING: World: VM xxxx: xxx: Failed to open swap file <path>: Lock was not free WARNING: World: VM xxxx: xxx: Failed to initialize swap file <path>   When opening a console to the virtual machine, you may receive the error: Error connecting to <path><virtual machin
Post a Comment
Read more

"Performance data is currently not available for this entity" viewing the performance tab

  Symptoms While accessing the performance tab and navigating to Overview, you see: No data available   The data for Real time, but fails to retrieve it for past 1 day, week, month or year.  While selecting the advance parameter in performance tab, you see: Performance data is currently not available for this entity Cause This issue is caused by the vCenter Server database (Postgress) containing a stale/future time stamp reference for the ESXi host when the data was collected. For vCenter Servers using SQL, see  "Performance data is currently not available for this entity" error after updating rollup in vSphere Resolution Backup the vCenter database. For more info
Post a Comment
Read more