Error: Timed out while syncing indexes for 'Compute Manager', 'Virtual Network Interface,Virtual Machine', Failed to fetch Inventory
Article ID: 404070
Updated On:
Products
Issue/Introduction
The NSX UI failed to list Compute Managers, Host Transport nodes, and the Inventory page. The following error messages were observed from the NSX UI.Timed out while syncing indexes for 'Compute Manager'Timed out while syncing indexes for 'Virtual Network Interface,Virtual Machine'
The log file /var/log/search/search-manager.log contained the following messages during the issue:
37538:2025-06-07T08:03:10.547Z INFO pool-723-thread-1 DistributedIndexingPositionManager 76964 - [nsx@6876 comp="nsx-manager" level="INFO" reqId="c4d#####-####-4b88-####-2452db######" subcomp="manager" username="system"] [QueryExecution: ConsistencyCheck] ComputeManagerStatusModelMsg/search_inventory is out of sync. Indexing position: 6796662000. Current Corfu Address: 679666540738351:2025-06-07T08:03:44.227Z INFO http-nio-127.0.0.1-7440-exec-6549 DistributedIndexingPositionManager 76964 - [nsx@6876 comp="nsx-manager" level="INFO" reqId="e4bf####-0a07-####-a2fa-420da6####" subcomp="manager" username="admin"] [QueryExecution: ConsistencyCheck] VniMsg/search_inventory is out of sync. Indexing position: 6796660785. Current Corfu Address: 679667281157211:2025-06-07T08:13:10.795Z INFO pool-723-thread-1 DistributedIndexingPositionManager 76964 - [nsx@6876 comp="nsx-manager" level="INFO" reqId="ed35####-a7ab-####-a539-d9a########" subcomp="manager" username="system"] [QueryExecution: ConsistencyCheck] ComputeManagerStatusModelMsg/search_inventory is out of sync. Indexing position: 6796709870. Current Corfu Address: 679671731257855:2025-06-07T08:13:36.644Z INFO http-nio-127.0.0.1-7440-exec-6590 DistributedIndexingPositionManager 76964 - [nsx@6876 comp="nsx-manager" level="INFO" reqId="0dd#####-3ad9-####-8f66-1acc########" subcomp="manager" username="admin"] [QueryExecution: ConsistencyCheck] VniMsg/search_inventory is out of sync. Indexing position: 6796712898. Current Corfu Address: 679672157859059:2025-06-07T08:14:06.554Z INFO http-nio-127.0.0.1-7440-exec-6597 DistributedIndexingPositionManager 76964 - [nsx@6876 comp="nsx-manager" level="INFO" reqId="####a48d-####-4834-####-421b9########" subcomp="manager" username="admin"] [QueryExecution: ConsistencyCheck] VniMsg/search_inventory is out of sync. Indexing position: 6796721987. Current Corfu Address: 679672501774422:2025-06-07T08:23:13.341Z INFO pool-723-thread-1 DistributedIndexingPositionManager 76964 - [nsx@6876 comp="nsx-manager" level="INFO" reqId="72b2####-3db6-####-b985-2c8d########" subcomp="manager" username="system"] [QueryExecution: ConsistencyCheck] ComputeManagerStatusModelMsg/search_inventory is out of sync. Indexing position: 6796780902. Current Corfu Address: 67967862982025-06-10T05:50:11.614Z INFO UfoIndexer-BatchExecutor-search_inventory-1 UfoIndexingServiceImpl 76673 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="cm-inventory"] [Indexing: BatchProcessing] Processing batch of {VmPropertiesMsg=58, VirtualMachineContainerMsg=27, HostModelMsg=23, ComputeManagerStatusModelMsg=2, VniMsg=56} size 166 for indexing took 758672025-06-10T05:51:35.524Z INFO UfoIndexer-BatchExecutor-search_inventory-0 UfoIndexingServiceImpl 76673 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="cm-inventory"] [Indexing: BatchProcessing] Processing batch of {VmPropertiesMsg=54, VirtualMachineContainerMsg=11, HostModelMsg=25, ComputeManagerStatusModelMsg=2, VniMsg=53} size 145 for indexing took 839102025-06-10T05:48:55.746Z INFO UfoIndexer-BatchExecutor-search_inventory-0 UfoIndexingServiceImpl 76673 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="cm-inventory"] [Indexing: BatchProcessing] Processing batch of {VmPropertiesMsg=30, HostModelMsg=18, ComputeManagerStatusModelMsg=2, VniMsg=29} size 79 for indexing took 61219
Environment
VMware NSX
Cause
Due to intensive processing of indexing across multiple table the issue is being noticed.
Note: The cause of the issue varies based on each environment.
Resolution
The issue is fixed in NSX versions 4.2.3, 9.1, and 9.0.1. If this issue is still occurring and you need a workaround, please contact Broadcom Support for more information. - Contact Broadcom support
Feedback
