"Some appliance components are not functioning properly." Error displayed when attempting to log in to NSX manager

Products

• VMware NSX

Issue/Introduction

• Users are unable to access the NSX Manager GUI.. Upon checking the system, the following error message is displayed:
  Error: Some appliance components are not functioning properly. Component health: SEARCH:UNKNOWN, MANAGER:UNKNOWN, NODE_MGMT:UP, UI:UP. Error code: 101

  
  
• Log entries similar to the following are found on the NSX managers, indicating connection failures and unrecoverable errors:
  YYYY-MM-DDTHH:MM:SS.SSSZ | ERROR | Cmpt-9000-chkpter | compactor-leader | Unable to connect to server due to UnrecoverableCorfuError: org.corfudb.runtime.exceptions.unrecoverable.UnrecoverableCorfuError: java.lang.InterruptedException at org.corfudb.runtime.CorfuRuntime.connect(CorfuRuntime.java:####) ... Caused by: java.lang.InterruptedException: null

• On Checking compactor logs (e.g., zgrep 'FAILED nsx\|=====' corfu-compactor-leader.1.log.gz) reveals repeated failures for nsx$ProfileMsg:
YYYY-MM-DDTHH:MM:SS.SSSZ | INFO | Cmpt-9000-chkpter | compactor-leader | =============Initiating Distributed Compaction============ YYYY-MM-DDTHH:MM:SS.SSSZ | INFO | Cmpt-9000-chkpter | compactor-leader | ##.###.##.##: FAILED nsx$ProfileMsg in 0ms

• High disk usage (e.g., 51% or more) can be observed for the /dev/mapper/nsx-config partition, indicating data accumulation.

Environment

VMware NSX-T

Cause

The primary cause of this issue is a Compactor Out-Of-Memory error, specifically due to an excessively large nsx$ProfileMsg table. This leads to the compaction process failing, which prevents critical services from starting and impacts GUI accessibility.

Resolution

The recommended solution is to restore the NSX Manager from its latest healthy backup. This will revert the system to a state before the ProfileMsg table grew excessively.

If the user is not aware of the Backup password and not able to restore from the backup and if you believe you have encountered this issue, please open a support case with Broadcom Support and refer to this KB article.

For more information, see Creating and managing Broadcom support cases.

Additional Information

This issue is caused by Service Config related exceptions. A fix addressing this behavior is available in NSX-T Data Center version 4.2.2 and later.
Please refer to this KB for more insights: NSX Manager Data Collection Failure in AON/vRNI Due to Latency Profile Deletion Error