The testip option does not seem to be honored by the http test
I have the following in my hosts.cfg file:
10.100.2.131 fourqueens.REDACTED.com # testip ssh mgmt=10.2.6.131[http,https,ssh] https://megaagency.REDACTED.com delayred=http:10 10.100.2.132 fitzgeralds.REDACTED.com # testip ssh mgmt=10.2.6.132[http,https,ssh] https://megaagency.REDACTED.com delayred=http:10
The "mgmt" option controls a custom server-side script we wrote that verifies reachability of the out-of-band server management (Dell DRAC in this case).
I had expected the "testip" option to force the https URL test to be sent directly to the server, not the DNS address (which is a load balancer), but I can see the load balancer cookie in the response and requests in the load balancer's log.
Is there any way to get the intended behavior?
The server is running 4.3.23 with the patch to fix http response code interpretation.
Thanks, Shawn
On 3/9/2016 8:53 AM, Shawn Heisey wrote:
- snip -
I had expected the "testip" option to force the https URL test to be sent directly to the server, not the DNS address (which is a load balancer), but I can see the load balancer cookie in the response and requests in the load balancer's log.
The TESTIP controls the behavior of the CONN test. To make the HTTP test use an IP address instead of resolving the name, use the following syntax: http://www.sample.com=1.2.3.4/index.html
From the hosts.cfg man page:
Testing sites by IP-address xymonnet ignores the "testip" tag normally used to force a test to use the IP-address from the hosts.cfg file instead of the hostname, when it performs http and https tests. The reason for this is that it interacts badly with virtual hosts, especially if these are IP-based as is common with https-websites. Instead the IP-address to connect to can be overridden by specifying it as: http://www.sample.com=1.2.3.4/index.html The "=1.2.3.4" will case xymonnet to run the test against the IP-address "1.2.3.4", but still trying to access a virtual website with the name "www.sample.com". The "=ip.address.of.host" must be the last part of the hostname, so if you need to combine this with e.g. an explicit port number, it should be done as http://www.sample.com:3128=1.2.3.4/index.html
-- Do things because you should, not just because you can.
John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration State of Alaska
participants (2)
-
hobbit@elyograg.org
-
john.thurston@alaska.gov