severity #307462 normal On Tue, May 03, 2005 at 02:59:30PM +0200, Tore Anderson wrote: > Crap. Hmm. But, just noticed something: > > > DEBUG: Checking plugin: apt_all...manual...autoconf... > > DEBUG: Checking plugin: cps_...manual...autoconf...suggest... > > DEBUG: Checking plugin: cpu...auto...autoconf... > > Since the cpu plugin isn't a wildcard plugin, it's not supposed to > print more on that line. So it's quite possible that the problem isn't > with the cpu plugin, but with whatever comes afterwards. But the > "DEBUG: Checking plugin.." part of the line is printed before the > plugin is executed, and standard out is autoflushed. Strange indeed.
I have more information now. It looks like the process didn't hang, it just took a looooooong time to finish (like 20 minutes for a munin-node-configure --shell --debug), with a loooong delay for _each_ plugin. I was on a foreign network which had some DNS issues, and upon returning to my home network, munin-node-configure now runs fine. So I have only one issue: If it is really a DNS timeout happening, why is it re-happening for each and every plugin being initialized? Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
