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

Troubleshooting vpxd service on Windows vCenter Server

  Symptoms You cannot connect to VMware vCenter Server with the vSphere Client. You cannot see the VMware vCenter Server in the inventory in the vSphere Web Client. You see a Microsoft Windows Event error associated with IIS similar to: Event properties - Event 7024, Service Control Manager The VMware VirtualCenter Server service terminated with service-specific error The system cannot find the file specified.. Log Name: System Source: Service Control Event ID: 7024 Level: Error Note : A windows Event ID 1000 may also be reported in relation to this issue.   Connecting to vCenter Server fails with the error: Cannot connect to host server_name : No connection could be made because the target machine actively refused it.   Attempting to start the VMware VirtualCenter Server service fails. You see this error: Windows could not start the VMware VirtualCenter Server service on...
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 ...
Post a Comment
Read more

"Failed to configure vAPI Endpoint Service at the firstboot time" while installing Windows VC 6.5

  Symptoms While configuring the vAPI EndPoint Service, you experience these symptoms: Windows vCenter Server 6.5 installation fails while configuring the vAPI EndPoint Service vCenter Server 6.5 installation on a Windows Server fails during the vAPI EndPoint Service during the firstboot time. You see the error: Error: An error occurred while starting service 'vapi-endpoint'. Failed to start the vAPI Endpoint Service. Failed to configure vAPI Endpoint Service at the firstboot time. Please file a bug against VAPI   In vapi_firstboot.py_2948_stderr.log file, you see entries similar to: No valid files with pathname: C:\ProgramData\VMware\vCenterServer\logs\vapi\endpoint* found. ERROR starting vapi-endpoint rc: 2, stdout: , stderr: Start service request failed. Error: Service crashed while starting^M vapi firstboot failed Traceback (most recent call last): File "C:\Program Files\VMware\vCenter Server\firstbo...
Post a Comment
Read more