Actually, it seems I just didn't allow enough time for the caching DNS server to actually cache... That does seem to have fixed the "DNS Error" problem. But I will keep your suggestion in mind in case it comes back.
Thanks for the suggestions everyone.
On 9/5/07, Henrik Stoerner <henrik at hswn.dk> wrote:
Try increasing the timeout setting on the network tests - add a "--timeout=30" option to the bbtest-net command in hobbitlaunch.cfg .
Regards, Henrik
On Wed, Sep 05, 2007 at 01:15:50PM -0400, Gary Baluha wrote:
It seems adding a local caching DNS server did no fix this problem. I'm truely at a loss now, because nothing I test manually seems to indicate a problem. Also, when the hobbit alerts go red due to "DNS Error", as soon as I go to check, it has cleared up already.
On 9/5/07, Gary Baluha <gumby3203 at gmail.com> wrote:
On 9/5/07, Henrik Stoerner <henrik at hswn.dk> wrote:
On Wed, Sep 05, 2007 at 09:43:32AM -0400, Gary Baluha wrote:
It sounds like an obvious answer, but what does the http/https monitoring error "DNS Error" mean, exactly?
It means Hobbit could not lookup the hostname in DNS.
Okay, I thought it was pretty self explanatory, but a quick glance at
the
code wasn't obvious to me.
Specifically, I have several https checks defined in Hobbit, and a good
number of them get the "DNS Error" message multiple times a day; roughly on the order of every 1-3 hours. I have manually verified that DNS is working for these hosts. It might help me troubleshoot this if I know exactly how Hobbit comes to this determination, and if anything else other than DNS could cause it to appear.
A local caching DNS server is usually a good idea. Hobbit has been known
to knock out DNS servers, because it sends a lot of requests very quickly.
Well, two suggestions to have a local caching DNS must mean it's a pretty good idea. I set this up, and will see if that fixes the problem.
-- Henrik Storner
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk