vpxa log shows error message "Not a non-singleton object" during ESXi host boot
Article ID: 441970
Updated On:
Products
Issue/Introduction
After the ESXi host boots, during the synchronization phase with vCenter Server, multiple error-level logs such as "Not a non-singleton object: key <key name>" are output in the vpxa log.
YYYY-MM-DDThh:mm:ss.###Z Er(163) Vpxa[######]: [Originator@6876 sub=Libs opID=HB-host-####@###-########-##] error [ConfigStore:##########] [1046] Not a non-singleton object: key <key name>YYYY-MM-DDThh:mm:ss.###Z In(166) Vpxa[######]: [Originator@6876 sub=Libs opID=HB-host-####@###-########-##]info [ConfigStore:##########] ConfigStoreException: [context]###[/context]YYYY-MM-DDThh:mm:ss.###Z In(166) Vpxa[######]: [Originator@6876 sub=Default opID=HB-host-####@####@###-########-##] Ignoring ConfigStoreException[1046] Not a non-singleton object: key <key name>
Note: <key name> includes alarm, core, http_nfc, log, nfc, etc.
Environment
VMware vSphere ESXi 8.0
Cause
After the ESXi host boots, during the synchronization and initialization phase with vCenter Server, vpxa reads configuration parameters from the ESXi ConfigStore.
While vpxa requests data as a list of multiple objects, specific configuration keys (such as alarm, core, http_nfc, log, and nfc) are defined as singletons (single data entries) within the ConfigStore schema, resulting in a temporary data structure mismatch between the vpxa request and the data format on the ConfigStore side. This causes it to return a ConfigStoreException.
Resolution
This error message can be safely ignored.
As shown in the subsequent log entry "Ignoring ConfigStoreException[1046] Not a non-singleton object: key <key name> ", vpxa ignores this exception as an expected behavior and successfully continues the initialization. This error message has no impact on ESXi host stability, virtual machine operations, or vCenter Server management and monitoring functions.
Additional Information
Feedback
