On Wed, 2006-11-29 at 13:51 +0100, Henrik Stoerner wrote:
On Wed, Nov 29, 2006 at 06:40:58AM -0600, Daniel J McDonald wrote:
I am seeing intermittent resolver failures
in /var/log/hobbit/bb-network.log.
[...]
Or is there some
local resolver caching I could set up to help mitigate this problem?
A local caching DNS server on the Hobbit box doing network tests is always
a good idea.
A new instance of bind seems to have resolved the issue.
At any other point in the MRTG polling cycle the resolver seems to work
fine. The other pieces cause the system to be network bound during the
initial poll (about 25 seconds), and disk bound (40 seconds) whilst
re-writing the ~6000 RRD files.
So another solution might be to make sure that the MRTG update and the
Hobbit network tests do not run at the same time. You can do that if you
run the mrtg update from hobbitlaunch instead of through cron; the GROUP
keyword for each section in hobbitlaunch.cfg is used to make sure there
is only one task belonging to each GROUP running at the same time.
This would not likely work. The total time that MRTG runs is about 3
minutes 40 seconds, with a fair chunk of that single-threaded (and thus
not CPU bound on my multi-processor box). To limit bb-net tests to just
that small timeslice eliminates some the the cool benefits of hobbit,
like 1-minute retries...
--
Daniel J McDonald, CCIE # 2495, CISSP # 78281, CNX
Austin Energy
http://www.austinenergy.com