HTTPMonitor_cURL_ProbeTimeout

Now you are missing the POOL variable from your monitor definition.

The basic external monitor troubleshooting process is:

1) Verify the script is functioning as expected.

From the command line, export the 5 variables and run the script with the 2 expected arguments (IP & port of a healthy pool member).

  export POOL="cwmp.stage.80"
  export CAUCHOPORT="4004"
  export P_TIMEOUT="5"
  export RECV="w50-`echo $IP | cut -d. -f4`.c50.domain.com:6802 (ok)"
  export URI="/caucho-status"
  /usr/bin/monitors/curlcaucho 10.50.1.1 5004

If the script output is UP, the script is functioning as expected.

If there is no output or some other output, run under sh -x and correct all errors until expected output results.

  sh -x /usr/bin/monitors/curlcaucho 10.50.1.1 5004

tcpdump may come in handy to verify the expected request & response on the wire. Filter on the IP and port to which the monitor traffic will be sent. (Note that in this case the port to which the monitor traffic is sent is different from the port defined for the pool member.)

tcpdump -nni internal -Xs 0 host 10.50.1.1 and port 5004

You can further filter to include both the internal self-IP and the pool member's IP to eliminate load balanced traffic:

tcpdump -nni internal -Xs 0 host 10.50.1.1 and host 10.50.0.246 and port 5004

2) Define the monitor in the LTM configuration and apply to a single healthy pool member.

monitor curlcaucho {
  defaults from external
  run "curlcaucho"
  POOL "cwmp.stage.80"
  CAUCHOPORT "4004"
  P_TIMEOUT "5"
  RECV "w50-`echo $IP | cut -d. -f4`.c50.domain.com:6802 (ok)"
  URI "/caucho-status"
}

If the pool member doesn't appear as UP within the timeout period, use the same tcpdump command you used before to see whether the expected request and/or response is seen. It may be helpful to compare output from step 1 with output from step 2 to figure out what is different.

HTH

/deb