vCenter Server vpxd.log shows local datastore as “notAccessible"

Products

• VMware vSphere ESXi

Issue/Introduction

• The following error messages are observed in the vCenter's vpxd.log. 

YYYY-MM-DDTHH:MM:SS.762 info vpxd[09605] [Originator@6876 sub=vpxLro opID=1f058bbd] [VpxLRO] -- BEGIN session[52b55c3a-39fd-b7ee-c937-150538cd533a]5276704d-97c0-c1f8-682d-752aedd4ce27 -- CatalogSyncManager -- vim.vslm.vcenter.CatalogSyncManager.queryCatalogChange -- 52b55c3a-39fd-b7ee-c937-150538cd533a(522d8c86-4d90-1aa0-ebe8-2fa5efe780f6)
YYYY-MM-DDTHH:MM:SS.763 error vpxd[09605] [Originator@6876 sub=HostPicker opID=1f058bbd] Couldn't find any candidate host that satisfies all constraints
YYYY-MM-DDTHH:MM:SS.763 warning vpxd[09605] [Originator@6876 sub=Vmomi opID=1f058bbd] VMOMI activation LRO failed; <<52b55c3a-39fd-b7ee-c937-150538cd533a, <TCP '127.0.0.1 : 8085'>, <TCP '127.0.0.1 : 57468'>>, CatalogSyncManager, vim.vslm.vcenter.CatalogSyncManager.queryCatalogChange, <vim.version.v8_0_3_0, internal, 8.0.3.0>, (null)>, N3Vim5Fault21InaccessibleDatastore9ExceptionE(Fault cause: vim.fault.InaccessibleDatastore
--> )
--> [context]zKq7AVECAQAAAI48ewEXdnB4ZAAAQxxTbGlidm1hY29yZS5zbwAACBhCACk/QwCWmUqBpe0cAXZweGQAgfYTHgGB5zsuAYHB6S4BgQiIFAKBt18SAoLRNX0BbGlidmltLXR5cGVzLnNvAIHd7YICA011HGxpYnZtb21pLnNvAIGCxmACgVx5gQKBp4mBAoGbnIACgYpzgQIABOw3ABdFOADFD1EEsI4AbGlicHRocmVhZC5zby4wAAXf+g9saWJjLnNvLjYA[/context]
YYYY-MM-DDTHH:MM:SS.766 info vpxd[09605] [Originator@6876 sub=vpxLro opID=1f058bbd] [VpxLRO] -- FINISH session[52b55c3a-39fd-b7ee-c937-150538cd533a]5276704d-97c0-c1f8-682d-752aedd4ce27
YYYY-MM-DDTHH:MM:SS.766 error vpxd[09605] [Originator@6876 sub=Default opID=1f058bbd] [VpxLRO] -- ERROR session[52b55c3a-39fd-b7ee-c937-150538cd533a]5276704d-97c0-c1f8-682d-752aedd4ce27 -- 52b55c3a-39fd-b7ee-c937-150538cd533a(522d8c86-4d90-1aa0-ebe8-2fa5efe780f6) -- CatalogSyncManager -- vim.vslm.vcenter.CatalogSyncManager.queryCatalogChange: :vim.fault.InaccessibleDatastore
--> Result:
--> (vim.fault.InaccessibleDatastore) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = <unset>,
-->    datastore = 'vim.Datastore:<datastore-uuid>:datastore-<MOID>',
-->    name = "<datastore_name>",
-->    detail = "notAccessible"
-->    msg = ""
--> }
--> Args:
-->
--> Arg catalogChangeSpec:
--> (vim.vslm.CatalogChangeSpec) {
-->    datastore = 'vim.Datastore:datastore-<MOID>',
-->    startVClockTime = (vim.vslm.VClockInfo) {
-->       vClockTime = 0
-->    },
-->    fullSync = true
--> }

• The local datastore can be accessed normally from vCenter Server as well as ESXi host.
• No connection exception of the local datastore found in ESXi host /var/run/log/vmkernel.log.
• Cloud Native Storage(CNS) and Supervisor are not enabled in the vSphere environment.

Environment

• VMware vCenter Server 8.0

• VMware ESXi 8.0

Cause

The task triggering this notAccessible error is vim.vslm.vcenter.CatalogSyncManager.queryCatalogChange.

The CatalogSyncManager task is responsible for synchronizing the First Class Disk (FCD) directory in the datastore. Its primary function is to maintain the consistency of Cloud Native Storage (CNS) data — primarily used for Tanzu Kubernetes and other cloud-native components.

When multiple datastores are visible in the vSphere Client, the CNS synchronization mechanism assumes that vCenter Server provides a complete datastore list and automatically triggers its query process.

If any host in the environment cannot access an ESXi local datastore, the synchronization process will fail, resulting in this notAccessible message.

Since CatalogSyncManager is a built-in recurring task in vCenter, and the corresponding log entries will repeatedly appear.

Resolution

1. The messages of notAccessible for local datastore on the task 'vim.vslm.vcenter.CatalogSyncManager.queryCatalogChange' can be safely ignored in this environment.

2. Optionally disable the messages in vCenter Server /var/log/vmware/vpxd/vpxd.log：

   1. SSH into the vCenter Server

       
   2. Backup /usr/lib/vmware-vsan/VsanVcMgmtConfig.xml
       

      cp /usr/lib/vmware-vsan/VsanVcMgmtConfig.xml /usr/lib/vmware-vsan/VsanVcMgmtConfig.xml.bak

       
       
       
   3. Edit /usr/lib/vmware-vsan/VsanVcMgmtConfig.xml
       

      vim /usr/lib/vmware-vsan/VsanVcMgmtConfig.xml

      Locate the following line:

       

      <newSyncInterval>60</newSyncInterval>

      Change it to:

       

      <newSyncInterval>0</newSyncInterval>

       

   4. Save the file, then restart the vSAN health service:

       

      service-control --restart vmware-vsan-health

       

3. To re-enable synchronization later
   If plan to use Tanzu in the future, change the value back from 0 to 60 and restart the same service.