Forum Discussion
Health monitor for BIG-IP 11.1.0 Build 2027.0 Hotfix HF2 not working
Hello All, The below health monitor keeps failing. Any thoughts on why this is happening?
ex) 1 Virtual Server, pool of 3 members.
A server B server C server
Below health monitor C server. It contains a absolute URL and if fails C server should be flagged down. GET /web/community HTTP/1.1\r\nHost: www12-qa.qad.com\r\nConnection: Close\r\n
I appreciate any input.
TRX
11 Replies
- JRahm
Admin
At the end of your monitor string you need a double \r\n, so it should look like this:
GET /web/community HTTP/1.1\r\nHost: www12-qa.qad.com\r\nConnection: Close\r\n\r\n Thanks. I'll give it a try.
- afedden_1985
Cirrus
don't for get to add 200 in the receive string
we use something like this for the monitor and just enter 200 in the receive string HEAD /serverhealth/status.asp HTTP/1.1\r\nHost: healthcheck.my.place.com\r\nConnection: close\r\n\r\n
The below syntax still fails. Any other ideas?
GET /web/community HTTP/1.1\r\nHost: www12-qa.qad.com\r\nConnection: Close\r\n\r\n
- JRahm
Admin
turn on debug so you can see what's going on:
tmsh modify sys db bigd.debug value Enable
Just make sure you turn it off afterward.
I'll go ahead and do that, and see what errors it gives out.
It seems like the URL has to be hitting the member the health monitor is applied to or it always fails. Seems like a config or a syntax error.
ex) exnt29.qad.com (IP: 167.....29) Health monitor:
Does not work: GET /erp HTTP/1.1\r\nHost: exnt30.qad.com\r\nConnection: Close\r\n\r\n
Works: GET /erp HTTP/1.1\r\nHost: exnt29.qad.com\r\nConnection: Close\r\n\r\n
Thoughts?
- JG
Cumulonimbus
It looks like it is a problem of the configuration of your backend Web servers. You can set up a default Web server that will accept any request with any hostname from the client.
- JG
Cumulonimbus
Or just use a relative URL, since all your app servers are supposed to serve the same content, whatever names they assume.
- marco_octavian_
Nimbostratus
Yep. To add a little more to Jie's response, the webserver is probably configured, by default install,to allow it's own hostname and localhost. That's typcially the case or at least what I have seen on occasion. Add the absolute URL to list of supported hostnames.
To validate this, create an alias in your hosts file that has the absolute url and the ACTUAL server address. Then hit the webserver using your browser and see what happens. It should be an error, just like your monitor.
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