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

NSX Edge lose VMCI connection to NSX Manager (56509)

Last Updated: 2/22/2019Categories: TroubleshootingTotal Views: 6661Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

When the NSX Manager is unavailable for an extended period of time, you experience these symptoms:

The NSX Edge may lose VMCI connection to the NSX Manager.

In the NSX Edge logs, you see entries similar to:

2018-04-14T13:11:29+00:00 xxx syslog-ng[837]: [default]: [syslog.notice] Configuration reload request received, reloading configuration;
2018-04-14T13:11:29+00:00 xxx MsgMgr[1075]: [daemon.info] VSM msg handler created - amqp broker host:127.0.0.1 ip:0x100007f port:10000
2018-04-14T13:11:29+00:00 xxx MsgMgr[1075]: [daemon.err] SSL_connect:: Underlying syscall error (Bad file descriptor)
2018-04-14T13:11:34+00:00 xxx MsgMgr[1075]: [daemon.info] VSM msg handler created - amqp broker host:127.0.0.1 ip:0x100007f port:10000

...
2018-04-16T11:54:17+00:00 xxx MsgMgr[1075]: [daemon.info] VSM msg handler created - amqp broker host:127.0.0.1 ip:0x100007f port:10000
2018-04-16T11:54:17+00:00 xxx MsgMgr[1075]: [daemon.err] SSL_connect:: Underlying syscall error (Bad file descriptor)
2018-04-16T11:54:22+00:00 xxx MsgMgr[1075]: [daemon.info] VSM msg handler created - amqp broker host:127.0.0.1 ip:0x100007f port:10000
2018-04-16T11:54:22+00:00 xxx MsgMgr[1075]: [daemon.err] SSL_connect:: Underlying syscall error (Bad file descriptor)

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

Cause

This issue occurs because when the NSX Manager is not available, the msgmgr process on the NSX Edge waits 30 seconds for the NSX Manager to respond. If there is no response, msgmgr will retry without properly closing the previously open files. This results in a very large number of open file descriptors if the NSX Manager is down for a long time.

Resolution

This issue is resolved in:

VMware NSX for vSphere 6.3.7, available at VMware Downloads.
VMware NSX for vSphere 6.4.2, available at VMware Downloads.

Workaround

To work around this issue:

Restart the NSX Edge appliance which should clean up the open socket connections. Once this completes, the NSX Edge should be able to re-connect back to the NSX Manager.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.3.x

Take Our Survey

Support Assistant