Dig test as the only service monitored
I did a bit more testing, and found that the ³dig² test cannot be the only service that is monitored for a host, or it will fail. As I wanted to check my anycast dns address to verify that it responds to DNS for various zones (and we generally don¹t respond to echo requests on load-balanced virtual addresses), the only test I needed to run was ³dig². I have added the ³conn² test and now the dig test becomes active.
I did replicate the issue with another virtual DNS server anycast address. The failure message is ³service unavailable². That appears to be coming from line 1528 of xymonnet.c. I¹m not handy enough in C to determine where the precise coding is that blocks testing services when there are no ping or tcp tests first.
Is that expected behavior?
-- Daniel J McDonald, CISSP # 78281
Daniel
On 14 January 2014 05:06, Daniel McDonald <dan.mcdonald at austinenergy.com>wrote:
I did a bit more testing, and found that the “dig” test cannot be the only service that is monitored for a host, or it will fail.
This configuration works for me. I have two hosts that I cannot ping, nor do I have any other tests. My hosts.cfg entries look like:
203.52.0.222 dns1.example.com # testip delayred=dns:15 delayyellow=dns:10 dns=SOA:zone.example.com,A:host1.zone.example.com,A: host2.zone.example.com,SOA:au noping 203.52.1.221 dns2.example.com # testip delayred=dns:15 delayyellow=dns:10 dns=SOA:zone.example.com,A:host1.zone.example.com,A: host2.zone.example.com,SOA:au noping
I wonder if it's the "testip" that I have here. I generally have "testip" on servers I test. If there's a transient DNS problem, I only want my DNS server to show a fault in Xymon.
J
participants (2)
-
dan.mcdonald＠austinenergy.com
-
jlaidman＠rebel-it.com.au