The service nestdb changed from STARTED to STOPPED.

Products

• VMware NSX

Issue/Introduction

• Alarm seen on NSX Edge nodes: The service nestdb changed from STARTED to STOPPED
• Log lines similar to the below are encountered in /var/log/nvpapi/api_server.log
  

  napi.root.alarms.infrastructure_service WARNING Can't get PID for service nestdb-server
  nsx_monitoring.clientlibrary.event_source WARNING The service nestdb changed from STARTED to STOPPED.
  nsx_monitoring.clientlibrary.event_source WARNING The service nestdb changed from STOPPED to STARTED.

• Log lines similar to the below are encountered in /var/log/syslog
  

  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.
  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.
  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, the nestdb service wasn't stopped/restarted:
  

  ps -ef | grep nestdb-server
  nestdb 5083 1 0.0 0.0 2628 1756 0 ? Ss <Timestamp> /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 <Timestamp> /opt/vmware/nsx-nestdb/bin/nestdb-server --schema /opt/vmware/nsx-nestdb/schema

  As per processes details, the nestdb service is up since the boot time of the NSX Edge node, no restart or stop occurred on the service. A false positive alarm has been created post error "Can't get PID for service nestdb-server".

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware NSX-T Data Center 3.2.3 and above.

Cause

The NSX Edge node was unable to fetch the process ID for nestdb-service.
This creates a false positive alarm seen on NSX Edge nodes: The service nestdb changed from STARTED to STOPPED

Resolution

This issue is resolved in VMware NSX-T Data Center 3.2.4 and VMware NSX 4.1.1, available at Broadcom downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.