The service nestdb changed from STARTED to STOPPED.

Products

• VMware NSX

Issue/Introduction

False positive alarm seen on edge nodes "The service nestdb changed from STARTED to STOPPED"

Environment

VMware NSX 3.2.3 and older.

Cause

NSX Edge was unable to fetch the process ID for nestdb-service.

Resolution

Fixed in 3.2.4, 4.1.1, 4.1.2 and in future releases.

Additional Information

Logs to validate:

 

nvpapi/api_server.log:

--------------------------

2024-06-11T23:11:01.004Z napi.root.alarms.infrastructure_service WARNING Can't get PID for service nestdb-server

2024-06-11T23:11:01.223Z nsx_monitoring.clientlibrary.event_source WARNING The service nestdb changed from STARTED to STOPPED.

2024-06-11T23:12:03.736Z nsx_monitoring.clientlibrary.event_source WARNING The service nestdb changed from STOPPED to STARTED.

 

var/log/syslog

------------------

35750:2024-06-11T23:11:01.223Z <edge-01> NSX 5662 - [nsx@6876 comp="nsx-edge" subcomp="node-mgmt" username="root" level="WARNING" eventFeatureName="infrastructure_service" eventType="edge_service_status_changed" eventSev="warning" eventState="On"] The service nestdb changed from STARTED to STOPPED.

36699:2024-06-11T23:12:03.736Z <edge-01> NSX 5662 - [nsx@6876 comp="nsx-edge" subcomp="node-mgmt" username="root" level="WARNING" eventFeatureName="infrastructure_service" eventType="edge_service_status_changed" eventSev="warning" eventState="Off"] The service nestdb changed from STOPPED to STARTED.

 

2024-06-11T23:11:01.004Z <edge-01> NSX 5662 - [nsx@6876 comp="nsx-edge" subcomp="node-mgmt" username="root" level="WARNING"] Can't get PID for service nestdb-server

 

As per processes list, nestdb service wasn't stopped/restarted, which shows its a false positive alarm.

/edge
---------

less processes | grep -i "nestdb"

nestdb 5083 1 0.0 0.0 2628 1756 0 ? Ss Feb10 00:00:00 /bin/sh /opt/vmware/nsx-nestdb/bin/watchdog.sh -s NSX-NESTDB -q 20 /opt/vmware/

nestdb 5101 5083 0.3 0.1 540548 84356 0 ? Ssl Feb10 10:49:53 /opt/vmware/nsx-nestdb/bin/nestdb-server --schema /opt/vmware/nsx-nestdb/schema

Summary:

As per processes details, we could notice that the nestdb service is up since Feb10, no restart or stop occurred on the service. False positive alarm has been created post error "Can't get PID for service nestdb-server".

 

If the above behavior is not met as false positive or if the nestdb service is actually down, please open a support request with Broadcom support to validate further.