Continuous ngnix Load Balancer Worker Process Crash observed on the edge
search cancel

Continuous ngnix Load Balancer Worker Process Crash observed on the edge

book

Article ID: 417179

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • The Load Balancer ngnix worker process on an NSX Edge node was experiencing contineous crashes, occurring approximately every minute.
  • Can be verfied under /var/log/core/ , That new core file is generated every one minute.
  • Log entries similar to the below will be observed on the Edge Node in /var/log/syslog
    2024-05-##T15## <edge-node> kernel - - - [102####.00####] grsec: Segmentation fault occurred at 0000000000008050 in /opt/vmware/nsx-edge/sbin/datapathd[dp-fp:2:271####] uid/euid:0/0 gid/egid:124/124, parent /opt/vmware/edge/dpd/entrypoint.sh[entrypoint.sh:27#####] uid/euid:0/0 gid/egid:124/124

Environment

VMware NSX

Cause

The misconfigured HTTPS active health monitor was generating malformed data which crashed the ngnix worker process.

Resolution

The misconfiguration within the problematic active health monitor  needs to be identified and corrected.

Ways to identify the Misconfigured HTTPS active health monitor:

1.The pool members will be marked down as its not responding to the LB's Monitoring probe.

2. Perfom curl towards the pool member with the active monitor URL configured in the HTTPS monitoring and check the response.

If you believe you have encountered this issue and need support , please open a support case with Broadcom Support and refer to this KB article.
For more information, see Creating and managing Broadcom support cases.