Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Edge Load Balancer service status is UNKNOWN or NO_STANDBY (67468)

Last Updated: 3/20/2024Categories: InformationalTotal Views: 5516Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The following symptoms are observed

Load Balancer operational status is UNKNOWN or NO_STANDBY

On the Active or Standby Edge, the load balancer service has crashed creating a core file e.g.

/var/log/core/core.nginx.1550358639.gz

Syslog contains this error

/var/log/syslog
2019-03-03T19:47:31.740097+00:00 hostname kernel - - - [370535.138924] grsec: Invalid alignment/Bus error occurred at 00006cfd318d6000 in /opt/vmware/nsx-edge/bin/nginx[nginx:26545] uid/euid:134/134 gid/egid:140/140, parent /opt/vmware/nsx-edge/bin/nsd[nsd:4807] uid/euid:0/0 gid/egid:149/149

"lb-dispatcher" process may not be running

#pidof lb-dispatcher  >return no output

Cause

This Issue is observed if there are a large number of load balancer reconfiguration tasks. Over time, due to a memory leak, the load balancer memory is exhausted and the service crashes.

The "lb-dispatcher" service may not be restarted after the crash. Root cause is that when a service is hanging and system tries to stop (SIGTERM) it and timed out. Systemd won’t try to restart it and will mark it as failed state.

<28>1 2019-04-21T23:22:16.353836+00:00 rtp-NP-nsxtedge10 systemd 1 - -  nsx-edge-dispatcher.service: State 'stop-sigterm' timed out. Killing.
<29>1 2019-04-21T23:22:18.323229+00:00 rtp-NP-nsxtedge10 systemd 1 - -  nsx-edge-dispatcher.service: Main process exited, code=killed, status=9/KILL
<30>1 2019-04-21T23:22:18.348032+00:00 rtp-NP-nsxtedge10 systemd 1 - -  Stopped Edge LB Dispatcher.
<29>1 2019-04-21T23:22:18.348352+00:00 rtp-NP-nsxtedge10 systemd 1 - -  nsx-edge-dispatcher.service: Unit entered failed state.
<28>1 2019-04-21T23:22:18.348721+00:00 rtp-NP-nsxtedge10 systemd 1 - -  nsx-edge-dispatcher.service: Failed with result 'signal'.

Resolution

This issue is resolved in VMware NSX-T Data Center 2.4, available at VMware Downloads.

Workaround

The Edge VM can be rebooted to workaround the issue . As the issue can be hit again before upgarding to NSX-T 2.4, the recommendation is to add cron job on each LB edge node to periodically kill the lb-dispatcher process to avoid hitting memory leak in future. If the edge already hits the memory leak then killing just the lb-dispatcher will not help.

Steps:

1.  check if "lb-dispatcher" process running
#pidof lb-dispatcher

2. collect edge log bundle (include core dump files) then clean up the core files (under /var/log/core)

3a:  If "lb-dispatcher" is running , then kill the lb-dispatcher PID
#kill `pidof lb-dispatcher`

3b.   If "lb-dispatcher" is NOT running , then reboot the Edge .

4.  create a cron job of killing the lb-pid every night, till you upgrade to 2.4

On each  Edge VM edit /etc/crontab
0 1 * * * /bin/sh kill `pidof lb-dispatcher` &> /dev/null
(This cron example will result in the LB service restarting every night at 1am resetting the memory usage and preventing the service crashing during business hours.)

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center 2.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant