Health monitor issue

Hi JoeBlogs,

 

 

I'll have to source a version of wget foir the BigIP as it doesn't seem to have wget as part of it's distro. The monitor also needs to connect over SSL. I just re-iterate, all of the monitors are mis behaving. I'm also a little confused as to what I should be using in the GET string now. This is the situation, I need to check for some specific test being returned when a URI is accessed. For example,

 

 

The URI is /new-services

 

The expected text is "xyzzy"

 

 

At the moment I just have as the SEND string GET /new-services and the RECEIVE STRING as xyzzy

 

 

On some other examples in the forums and wiki I see some variations, some specify the use of \r\n and HTTP\1.1 which I have tried adding to the SEND string

 

 

GET /new-servies \r\n HTTP\1.1

 

 

but it still doesn't work. What is confusing is that the monitor status says unkown, and it just stays as a BLUE box.

 

 

I have even tried removing the SSL cert details from the settings (the remote server uses it's own self signed SSL certificate) as Aaron suggested the monitor might not require it, but still no go. In desperation I even created a bog standard TCP monitor and even that fails, yet I can ping the remote server fine from the BigIP units.

 

 

Even enabling debugging doesn't seem to work, the logfile it is meant to create in /var/log/biglog ins't created. I'm just begining to wonder if their is something fundementally wrong with the pair of units, perhaps a something went wrong during the upgrade from 9.4 to 9.6 or 9.6 to 10. It more or less worked as expected under 9.4.

 

 

I've also just noticed that when I add new monitors they are not appearing is the list of available monitors to add to a pool. There isn't a licensing restriction on how many health monitors you can have running is there?

 

Craig