Loading

×Sorry to interrupt
CSS Error

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

"Num handlers exceed max allowed" error when connecting to ESXi/ESX host using vSphere Client (1038478)

Last Updated: 1/4/2017Categories: TroubleshootingTotal Views: 22794Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Connecting to the ESXi/ESX host directly using the vSphere Client fails.

The host goes into the Not Responding state within vCenter Server.

In the hostd.log file on a ESXi 5.x host, you see entries similar to:

[2010-10-24 13:47:37.482 22083B90 warning 'Proxysvc'] Num handlers (128) exceed max allowed (128). Throttling accept

In the hostd.log file on a ESX 4.x host, you see entries similar to:

[2010-10-24 13:47:37.482 F63B3900 warning 'Proxysvc'] Num handlers (320) exceed max allowed (320). Throttling accept
[2010-10-24 13:47:37.499 F63B3900 verbose 'Proxysvc Req00440'] New proxy client SSL(TCP(local=192.168.10.230:58661, peer=192.168.10.231:443))
[2010-10-24 13:49:37.525 F566EB90 warning 'Proxysvc'] Num handlers (320) exceed max allowed (320). Throttling accept

Cause

This issue occurs when there are too many connections to the host and the host agent runs out of connection handlers.

Note: The maximum number of connection handlers is for ESXi 5.x is 128. The maximum number of connection handlers for ESX/ESXi 4.x is 320.

The host agent may run out of connection handlers if the firewall that implements SSL timeouts silently discards/drops connections. Any connection closure by the firewall must forward the connection state to both endpoints. If it does not forward the connection state to both endpoints, the connection handle remains open (TCP/ESTABLISHED), but is unusable.

Resolution

This issue is resolved in ESXi 6.5, available at VMware Downloads.

To work around this issue if you do not want to upgrade:

Run one of these commands to see the number of active sessions to the hostd agent:

For ESXi 5.x, run the command:

esxcli network ip connection list | grep ":443" | wc -l

Note: If you run the command without | wc -l, the output provides information about the sessions. For example:

tcp 0 0 127.0.0.1:443 127.0.0.1:52680 ESTABLISHED 5474098 rhttpproxy-work
tcp 0 0 10.131.0.125:443 10.131.10.204:58591 ESTABLISHED 5474099 rhttpproxy-work
tcp 0 0 10.131.0.125:443 10.131.10.204:49588 ESTABLISHED 5474099 rhttpproxy-work
tcp 0 0 0.0.0.0:443 0.0.0.0:0 LISTEN 9234 rhttpproxy-work

For ESXi 4.1, run the command:

esxcli network connection list | grep ":443" | wc -l

Note: If you run the command without | wc -l, the output provides information about the sessions. For example:

tcp 0 0 10.16.224.66:443 10.16.224.167:60226 ESTABLISHED 8353
tcp 0 0 10.16.224.66:443 10.16.224.167:60225 ESTABLISHED 8350
tcp 0 0 10.16.224.66:443 10.16.224.167:60224 ESTABLISHED 5736
tcp 0 0 0.0.0.0:443 0.0.0.0:0 LISTEN 4957

For ESX 4.1, run the command:

# netstat -anp | grep ":443" | wc -l

Note: If you run the command without | wc -l, the output provides information about the sessions. For example:

tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 3146/vmware-hostd
tcp 0 0 10.16.224.64:443 10.16.224.167:59982 ESTABLISHED 3146/vmware-hostd
tcp 0 0 10.16.224.64:443 10.16.224.167:59980 FIN_WAIT2 -
tcp 0 0 10.16.224.64:443 10.16.224.167:59990 ESTABLISHED 3146/vmware-hostd
tcp 0 0 10.16.224.64:443 10.16.224.167:59991 ESTABLISHED 3146/vmware-hostd
tcp 0 0 10.16.224.64:443 10.16.224.167:59989 ESTABLISHED 3146/vmware-hostd

If the output of the command in step 1 is close to 128 for ESXi 5.x or 320 for ESX/ESXi 4.x, restart management agents to close these connections. For more information, see Restarting the Management agents on an ESX or ESXi Server (1003490).

Note: To prevent this issue from recurring, you must also ensure that the firewall products used do not discard or drop idle connections silently.

Related Information

vSphere Client を使用して ESXi/ESX ホストに接続すると「Num ハンドラが最大許容数を超えました (Num handlers exceed max allowed)」エラーが発生する
使用 vSphere Client 连接至 ESXi/ESX 主机时出现“处理程序的数量超过最大允许数量 (Num handlers exceed max allowed)”错误

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)

KB
•
在 VMware vRealize Operations Manager 6.1.x EndPoint 中更改 epops-agent 的服务帐户 (2142246)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant