HTTP probe not working

Unanswered Question
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
Loading.
dario.didio Mon, 06/08/2009 - 05:39

Hi,

what is the error that you get in "show probe XXX detail?

ACE_module5/Admin# show probe HTTP_PROBE detail

probe : HTTP_PROBE

type : HTTP

state : ACTIVE

description :

----------------------------------------------

port : 80 address : 0.0.0.0 addr type : -

interval : 10 pass intvl : 10 pass count : 3

fail count: 3 recv timeout: 10

http method : GET

http url : /

conn termination : GRACEFUL

expect offset : 0 , open timeout : 1

expect regex : -

send data : -

------------------ probe results ------------------

associations ip-address port porttype probes failed passed health

------------ ---------------+-----+--------+--------+--------+--------+------

rserver : SERVER1

192.168.10.45 80 -- 24 15 9 SUCCESS

Socket state : CLOSED

No. Passed states : 1 No. Failed states : 1

No. Probes skipped : 0 Last status code : 200 <-----------------------------------------------

No. Out of Sockets : 0 No. Internal error: 0

Last disconnect err : - <----------------------------------------------

Last probe time : Tue Apr 7 16:21:05 2009

Last fail time : Tue Apr 7 16:17:16 2009

Last active time : Tue Apr 7 16:20:05 2009

What did you change during migration? Is an ACL/Firewall blocking HTTP traffic to the ACE - server?

Kr,

Dario

Dario,

Unfortunatley; I did not save the outputs of the show probe detail commands, but I would guess that it was very generic like the one you posted.

port : 80 address : 0.0.0.0 addr type : -

interval : 10 pass intvl : 10 pass count : 3

fail count: 3 recv timeout: 10

http method : GET

http url : /

conn termination : GRACEFUL

expect offset : 0 , open timeout : 1

expect regex : -

send data : -

There were no FW or ACL change for the migration. Load balancing is working fine once I configured the probe to ICMP. My probe is configured to probe the header of the page and not a specific URL. I wonder if this symptom only occurs when the webpage does not have a default page configured.

I do remember during the brief time period I had to troubleshoot that when I tried to view the default page via telnet "telnet 10.10.10.10 80" it would connect to port 80, but when I entered "GET /" I would get a 404 error on some servers or I would get nothing on others.

John...

dario.didio Mon, 06/08/2009 - 06:07

Hi,

If you still want to troubleshoot aside of the prod serverfarm, you can configure a dummy serverfarm, add an rserver that had those problems and define your HTTP probe under it. Logically, it would still fail but you will be able to see the error using the show probe XXX detail command.

If you want, post your config of your probe, your rserver and the output of the show probe xxx detail command.

Kr,

Dario

Actions

This Discussion