retitle 307462 Workaround required for Net::Domain brokenness causing timeouts 
(#275024)
quit

* Marc Haber

> Next time, better clone the bug for reassignment against the other
> package and leave the original open against your package so that the
> issue can be seen by people experiencing the same behavior. That would
> have saved me some debugging time today.

  Sorry about that, I wasn't aware that this actually would occur in a
 normal situation (#275024 only happened during installation of Debian-
 Edu, according to the submitter).  And it isn't a bug in Munin,
 strictly speaking.

* Tore Anderson

>  For some strange reason, this module makes a lot of weird DNS lookup
> even though all the information it needs sits right there in
> /etc/hosts.  So, given a DNS server which times out on requests instead
> of answering NXDOMAIN or something else right away, you'd have to wait
> for a lot of timeouts in order for the Net::Domain::hostfqdn() call to
> finish (in my testing, six (6) times!!).

* Marc Haber

> Why is the local hostname resolved that often?

  I don't know, you'd have to ask the Net::Domain author.  Seems broken
 to me, in any case - especially when "hostname --fqdn" manages to find
 the hostname without any DNS lookups.  The Sys::Hostname workaround I
 suggested mimics the behaviour of "hostname --fqdn", which seems to be
 the Proper Way.

> Thanks for working on this. You can close this bug report if you think
> that there is nothing more that munin can do.

  Now that I know that #275024 can bite us in "normal" environments, 
 I'll just keep it open and try to get a workaround in there soon.
 In light of tonight's freeze, it seems unlikely that such a fix will
 make it into Sarge - unless of course I can sneak it in alongside a fix
 for a yet-to-be-reported >=important bug.  :-)

  Oh, by the way, I forgot to tell you:  You can work around this
 yourself by adding "host_name your.fully-qualified.hostname" in
 /etc/munin/munin-node.conf.  That should prevent it from making any
 hostname lookups at all.

Regards,
-- 
Tore Anderson



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to