Forum Discussion
redirect IIS 500 error to another host in pool
here is the output:
[root@f5:Active:Standalone] config curl -s -v 172.16.5.76 1> /dev/null
* About to connect() to 172.16.5.76 port 80 (0)
* Trying 172.16.5.76... connected
* Connected to 172.16.5.76 (172.16.5.76) port 80 (0)
> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 OpenSSL/1.0.1l zlib/1.2.3 libidn/1.18
> Host: 172.16.5.76
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: text/html
< Last-Modified: Thu, 13 Apr 2017 19:11:24 GMT
< Accept-Ranges: bytes
< ETag: "31cc9dbe89b4d21:0"
< Server: Microsoft-IIS/10.0
< X-Powered-By: ASP.NET
< Date: Wed, 15 Nov 2017 20:15:47 GMT
< Content-Length: 703
<
{ [data not shown]
* Connection 0 to host 172.16.5.76 left intact
- Lee_SutcliffeNov 15, 2017
Nacreous
That looks fine. Try just putting
in the receive string. Any issues please output the tmsh/cli monitor config:200 OK - Shamsul_Alam_34Nov 16, 2017
Nimbostratus
Still failed. No clue what going wrong here.
My monitor setting as below:
Node setting
Pool setting
- Lee_SutcliffeNov 16, 2017
Nacreous
Could you change your node monitor to gateway_icmp and remove https_443 from the pool so you're only using the Check_header_200-OK monitor
- Shamsul_Alam_34Nov 16, 2017
Nimbostratus
Still same after changed the setting as you requested
Monitor setting
POOL setting
- Lee_SutcliffeNov 16, 2017
Nacreous
Just noticed the Curl command you ran earlier is using TCP/80.
Could you create an HTTP (parent profile http) health monitor, first without a receive string. Then with the receive string.
Thanks
- Shamsul_Alam_34Nov 16, 2017
Nimbostratus
Still same. Monitor for HTTP
Pool
- Lee_SutcliffeNov 16, 2017
Nacreous
please remove https from the active health monitors
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com