Nginx core dump of L4 virtual server is generated on the standby node.

Products

• VMware NSX

Issue/Introduction

The nginx l4cp process core dump occurs on the standby node. 

Environment

VMware NSX-T Data Center

Cause

After reconfiguring and removing the pool member, the upstream pool member from the old active L4 session no longer exists.

Consequently, an object pointer referencing a parameter remains, but it is invalid and should not be accessed.

It eventually generates a nginx core dump and here is an example of an excerpt from /var/log/syslog.

<DATE_TIME> <HOSTNAME> NSX <PID> - [nsx@6876 comp="nsx-edge" subcomp="node-mgmt" username="root" level="WARNING"] Core file generated: /var/log/core/core.nginx.1716190806.1740865.134.11.gz

Script Settings

Minutes to Remind:
Hours to Remind:
Auto Refresh Interval (seconds):
Auto Refresh:
Auto Check-In:
Check-In Time:
Check-Out Time:
Template File:
Save

Open Trumbowyg

▶

Resolution

1. Disabling the access log and ha flow mirror can mitigate this issue.
2. A permanent fix will be shipped in a future release of NSX.

Script Settings

Minutes to Remind:
Hours to Remind:
Auto Refresh Interval (seconds):
Auto Refresh:
Auto Check-In:
Check-In Time:
Check-Out Time:
Template File:
Save

Open Trumbowyg

▶

Additional Information

 

Script Settings

Minutes to Remind:
Hours to Remind:
Auto Refresh Interval (seconds):
Auto Refresh:
Auto Check-In:
Check-In Time:
Check-Out Time:
Template File:
Save

Open Trumbowyg

▶