Forum Discussion
NimbostratusHealth monitor for 10.2 does not work
I have a send string of
GET /lsta/general/forgetPassword.htm HTTP/1.0\r\n\r\n
and receive string as 200 OK . When i use this health monitor it marks the pool down.
Any ideas?
6 Replies
natheCirrocumulus
Kirit,
What happens if you test to the pool member from the bigip with curl? (-0 is HTTP 1.0)
This might identify an issue.
e.g. curl -0
Hope this helps,
N
Kirit_Patel_521This is what i get
[root@edmz-t1ltm12-3:Active] log curl 302 Moved Temporarily
This document you requested has moved temporarily.
It's now at https://172.28.0.197/cusipaccess/contact.htm.
[root@edmz-t1ltm12-3:Active] log curl http://172.28.0.197:22410/cusipaccess/contact.htm 302 Moved Temporarily
This document you requested has moved temporarily.
It's now at https://172.28.0.197/cusipaccess/contact.htm.
[root@edmz-t1ltm12-3:Active] log curl http://172.28.0.197:22210/lsta/general/forgetPassword.htm
Error 404--Not FoundFrom RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1: 10.4.5 404 Not Found The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.[root@edmz-t1ltm12-3:Active] log- nathesorry, should've asked you to check the headers too as you're referencing a response header. try -I as part of the curl command
- Kirit_Patel_521
see below
[root@edmz-t1ltm12-3:Active] log curl -l http://172.28.0.197:22210/lsta/general/forgetPassword.htm
Error 404--Not FoundFrom RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1: 10.4.5 404 Not Found The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.[root@edmz-t1ltm12-3:Active] log- nathelooks like you're getting a 404 not a 200 status code. remove the receive string, i.e. make it blank to ensure it comes up as green. you'll then need to revisit what page/receive string you're checking.
- Kirit_Patel_521
Ok will do that. or maybe the application on the server is not deployed properly?
