NSX Manager UI displays notification "Failed to fetch System details. Please contact the administrator. Error: null (Error code: 513002)"
search cancel

NSX Manager UI displays notification "Failed to fetch System details. Please contact the administrator. Error: null (Error code: 513002)"

book

Article ID: 415291

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • In the NSX UI we see below alarm/notification.
     "Error: Failed to fetch System details. Please contact the administrator. Error: Re-creating indexes, this may take some time. (Error code: 513002)"
  • Customer had run the below command on the NSX Manager recently after which they started noticing the issue.
    start search resync policy
    start search resync manager
    start search resync all
  • In the /var/log/syslog we see similar error as below
    #012Cause: com.vmware.nsx.management.search.common.exceptions.SearchException: Re-creating indexes, this may take some time
  • In the /var/log/proton/nsxapi.log below error will be seen.
    Cannot fetch system details: Re-creating indexes, this may take some time.
  • In the /var/log/search/search-manager.log below are the log entries with the sequence of events which would cause the UI issue
    • After initial resync was triggered for policy
      2025-10-15T20:13:49.170Z  INFO http-nio-127.0.0.1-7440-exec-2320 UfoReIndexingManager 95###5 - [nsx@6876 comp="nsx-manager" level="INFO" reqId="34######-####-####-####-#########514" subcomp="manager" username="<user_name>"] [Indexing: Reindexing] ReIndexing Started
    • reindexing for policy was  in progress
      2025-10-15T20:13:49.203Z  INFO UfoReIndexingManager-Reindexing-0 SearchResyncStatusPersistenceServiceImpl 95###5 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated the resync status for node 2c######-####-####c-####-########30ea, stream tags search_policy and version 4.2.2.1.0.#######7 at 17#########70 to IN_PROGRESS
      2025-10-15T20:13:49.308Z  INFO UfoReIndexingManager-Reindexing-0 UfoReIndexingManager 95###5 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] [Indexing: Reindexing] Complete Indexing Initiated for stream tags: search_policy
      2025-10-15T20:13:49.319Z  INFO UfoReIndexingManager-Reindexing-0 SearchResyncStatusPersistenceServiceImpl 958165 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated the resync status for node 2c######-####-####c-####-########30ea, stream tags search_policy and version 4.2.2.1.0.#######7 at 17#########70 to IN_PROGRESS
    • New resync request came for only manager while reindexing for policy was already in progress:
      2025-10-15T20:14:01.854Z  INFO http-nio-127.0.0.1-7440-exec-2329 UfoReIndexingManager 95###5 - [nsx@6876 comp="nsx-manager" level="INFO" reqId="05######-####-####-####-########c1f3" subcomp="manager" username="node-mgmt"] [Indexing: Reindexing] ReIndexing Started
      and it interrupted currently running reindexing process for policy:
      2025-10-15T20:14:01.854Z ERROR UfoReIndexingManager-Reindexing-0 UfoReIndexingManager 95###5 - [nsx@6876 comp="nsx-manager" errorCode="MP60503" level="ERROR" subcomp="manager"] [Indexing:ProcessTable] Exception during indexing table GenericPolicyRealizedResource
      java.util.concurrent.RejectedExecutionException: Interrupted
    • which left policy part of reindexing in IN_PROGRESS state when manager finished its part:
      2025-10-15T20:14:01.869Z  INFO UfoReIndexingManager-Reindexing-0 SearchResyncStatusPersistenceServiceImpl 95###5 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated the resync status for node 2c######-####-####c-####-########30ea, stream tags search_manager and version 4.2.2.1.0.#######7 at 17#########56 to IN_PROGRESS
      2025-10-15T20:14:02.296Z  INFO UfoReIndexingManager-Reindexing-0 SearchResyncStatusPersistenceServiceImpl 95###5 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated the resync status for node 2c######-####-####c-####-########30ea, stream tags search_manager and version 4.2.2.1.0.#######7 at 17#########56 to IN_PROGRESS
      2025-10-15T20:14:02.284Z  INFO UfoReIndexingManager-Reindexing-0 UfoReIndexingManager 958165 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] [Indexing: Reindexing] Complete Indexing Initiated for stream tags: search_manager
      2025-10-15T20:14:15.404Z  INFO UfoReIndexingManager-Reindexing-0 SearchResyncStatusPersistenceServiceImpl 95###5 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated the resync status for node 2c######-####-####c-####-########30ea, stream tags search_manager and version 4.2.2.1.0.#######7 at 17#########93 to IN_PROGRESS
      2025-10-15T20:14:16.680Z  INFO UfoReIndexingManager-Reindexing-0 SearchResyncStatusPersistenceServiceImpl 95###5 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated the resync status for node 2c######-####-####c-####-########30ea, stream tags search_manager and version 4.2.2.1.0.#######7 at 17#########56 to DONE
      2025-10-15T20:14:15.415Z  INFO UfoReIndexingManager-Reindexing-0 UfoReIndexingManager 95###5 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] [Indexing: Reindexing] Complete Indexing finished, took 1###1 ms
      2025-10-15T20:14:16.720Z  INFO SearchResyncStatusPersistenceServiceImpl-1-1 SearchResyncStatusPersistenceServiceImpl 958165 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Resync status is changed to 'value: "DONE"
      ' for value: "search_manager" 

 

Environment

VMWare NSX

Cause

Before the actual completion of resync for policy stream tag (triggered by running the command "start search resync policy") invoking resync of manager stream tag(by running the command "start search resync manager") will interrupted the resync of policy ("start search resync policy") that was triggered before. The NSX Manager UI will have issue where the inventory will not be display and the error "Cannot fetch system details: Re-creating indexes, this may take some time." will be seen.

Resolution

  1. Issue is resolved in VCF 9.0
  2. To prevent the issue from happening. Kindly make sure the resync or re-indexing is completed before running the resync/re-indexing for the other NSX components.
    • Check the /var/log/search/search-manager.log log for below entries (Complete Indexing finished and Resync status is changed to 'value: "DONE"') for the start and the completion of the re-indexing before starting the resync/re-indexing of other NSX components.
      ReIndexing Started
      Complete Indexing Initiated  for stream tags: search_policy
      Updated the resync status for node 2c######-####-####c-####-########30ea, stream tags search_policy and version 4.2.2.1.0.#######7 at 17#########70 to IN_PROGRESS
      Complete Indexing finished, took 3###5 ms
      Resync status is changed to 'value: "DONE"
      ' for value: "search_policy"
  3. If the issue is already encountered. Kindly reboot the NSX Manager and check if the re-indexing/resync is completed for all the component using the above step 2 ("Complete Indexing finished" and Resync status is changed to 'value: "DONE"') if the re-indexing/resync is IN_PROGRESS for any of the component then kindly run the anyone of the below resync command to re-initiate the resync of that particular component.
    start search resync policy
    start search resync manager
    start search resync all

Note: Above is example log snippets for the Indexing completion after running the resync command for Policy

Additional Information

If you have experienced the issue without running the below commands kindly refer the below KB.
start search resync policy
start search resync manager
start search resync all

KB 410402 - NSX Manager UI displays notification "Failed to fetch System details. Please contact the administrator. Error: null (Error code: 513002)"
KB 410776 - NSX System Overview Not Loading
KB 405971- Search cancel Search "Failed to fetch System details" error 513002 when searching in NSX Manager UI