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

Pool Members DOWN after upgrading edge to 6.4.4 or higher. HTTP/HTTPS service monitor not working with host header extension. (79469)

Last Updated: 3/18/2023Categories: TroubleshootingTotal Views: 4090Language:
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

After upgrading edge to 6.4.4 or higher, load balancer pool members are DOWN.

An HTTP or HTTPS service monitor is used.

Attempting to access the backend servers directly via browser/curl proves that the servers are working as expected however they fail when accessed via LB

Requests may fail with SSL_ERROR_SYSCALL

In the extension field of the service monitor, a host header is specified using this format:

header="Host:host.domain.xyz"

That host header is not included in the HTTP/HTTPS request as it should.

Example from an HTTP request where the host header is correctly included pre-6.4.4.

Frame 3: 213 bytes on wire (1704 bits), 213 bytes captured (1704 bits)
Ethernet II, Src: Vmware_88:6e:cb (00:50:56:88:6e:cb), Dst: Vmware_88:2d:d9 (00:50:56:88:2d:d9)
Internet Protocol Version 4, Src: 172.16.1.1, Dst: 172.16.1.100
Transmission Control Protocol, Src Port: 12348, Dst Port: 80, Seq: 1, Ack: 1, Len: 159
Hypertext Transfer Protocol
GET / HTTP/1.0\r\n
User-Agent: check_http/v2.0.3 (nagios-plugins 2.0.3)\r\n
Connection: close\r\n
Accept: */*\r\n
Host:host.domain.xyz\r\n
X-Forwarded-Proto:https\r\n
\r\n
[Full request URI: http://host.domain.xyz/]
[HTTP request 1/1]

Example from an HTTP request where the host header is skipped after upgrade to 6.4.4+.

Frame 3: 183 bytes on wire (1464 bits), 183 bytes captured (1464 bits)
Ethernet II, Src: Vmware_88:b6:33 (00:50:56:88:b6:33), Dst: Vmware_88:99:83 (00:50:56:88:99:83)
Internet Protocol Version 4, Src: 172.16.1.1, Dst: 172.16.1.100
Transmission Control Protocol, Src Port: 21920, Dst Port: 80, Seq: 1, Ack: 1, Len: 129
Hypertext Transfer Protocol
GET / HTTP/1.0\r\n
User-Agent: check_http/v2.2.1 (nagios-plugins 2.2.1)\r\n
Connection: close\r\n
Accept: */*\r\n
X-Forwarded-Proto:https\r\n
\r\n
[HTTP request 1/1]

Cause

Starting 6.4.4, nagios plugins were upgraded to 2.2.1, specifically check_http which is used by some http and https service monitors.

On this new version, check_http expects "-H <hostname>" after header=Host:<hostname> in the extension field to add Host header correctly in the request. Otherwise the host will not be included in the header and the request can fail.

Resolution

Edit the Service Monitor and update the extension to the new syntax.

Original:

header=Host:host.domain.xyz

Updated:

header=Host:host.domain.xyz -H host.domain.xyz

You should now see that the host header is correctly included in the request.

Frame 3: 214 bytes on wire (1712 bits), 214 bytes captured (1712 bits)
Ethernet II, Src: Vmware_88:b6:33 (00:50:56:88:b6:33), Dst: Vmware_88:99:83 (00:50:56:88:99:83)
Internet Protocol Version 4, Src: 172.16.1.1, Dst: 172.16.1.100
Transmission Control Protocol, Src Port: 21982, Dst Port: 80, Seq: 1, Ack: 1, Len: 160
Hypertext Transfer Protocol
GET / HTTP/1.1\r\n
User-Agent: check_http/v2.2.1 (nagios-plugins 2.2.1)\r\n
Connection: close\r\n
Host: host.domain.xyz\r\n
Accept: */*\r\n
X-Forwarded-Proto:https\r\n
\r\n
[Full request URI: http://host.domain.xyz/]
[HTTP request 1/1]

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
Android Enterprise の新しい EMM 登録が断続的に失敗する (79429)

KB
•
AET-2626：米国および LATAM SaaS 環境において、WinCE デバイス向け Workspace ONE Assist 登録が失敗する (79380)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX Data Center for vSphere

Related Versions:

Take Our Survey

Support Assistant