NSX-T Data Center Edge service crashes when enable and disable Edge Health poll based alarm
book
Article ID: 322615
calendar_today
Updated On:
Products
VMware NSX Networking
Show More
Show Less
Issue/Introduction
Symptoms:
You have disabled and enabled a poll based alarm for Edge Health in NSX-T Data Center UI, Home, Alarms, Alarm Definitions . On the NSX-T Data Center log file, you see the following alerts: get log-file node-mgmt.log
2021-03-19T11:25:59.801Z nsx_monitoring.clientlibrary.event_source INFO The service edge-agent changed from STARTED to CRASHED. 2021-03-19T11:27:00.651Z nsx_monitoring.clientlibrary.event_source INFO The service edge-agent changed from CRASHED to STARTED .
In the NSX-T Data Center syslog we see a core dump being generated:
syslog:<180>1 2021-03-19T09:27:08.840Z edge-15.local NSX 30405 - [nsx@6876 comp="nsx-edge" subcomp="node-mgmt" username="root" level="WARNING"] Core file generated: /var/log/core/core.datapathd.1616146028.2979.0.11.gz
Environment
VMware NSX-T Data Center 3.x VMware NSX-T Data Center
Cause
The action of re-enabling the alarm causes the container service to crash, the edge will restart the service automatically.
Resolution
This issue is resolved in
NSX-T Data Center 3.1.3 .
Workaround:
The edge will restart the crashed container service automatically without generating cores, as long as the poll-based alarms are not disabled and enabled again.
Feedback
thumb_up
Yes
thumb_down
No