On Wed, Sep 28, 2011 at 03:23:34PM +0300, Damyan Ivanov wrote: > I did read what you wrote :)
ok, sorry. i assumed you skipped that bit :) > Thing is, my munin-node accepts ipv4 connections with exact same > LISTEN line as yours above. hmmm... are you making real use of ipv6 as well as ipv4? or just have inet6 addresses on your NICs because (like me) you haven't bothered disabling ipv6? and do you have allow lines in munin-node.conf for ipv6 addresses? > This makes me think there is something > else different on your system. i'd think the same if it was just my main home workstation (which has been messed about with since i started using debian in '94 - both hardware and software continuously upgraded, so there's a LOT of cruft)...but the error is consistent on every system i upgraded libnet-server-perl and restarted munin-node. even clean new VMs with hardly anything installed, untinkered with, just plain out-of-the-box stock debian sid. > Can you try tcpdump and/or strace and see what exactly is happening? i could but then i'd break my running munin config :-( i already lost half a day's stats before i noticed the problem so i'm not keen to do that right now. i'll fire up a new VM at work tomorrow and do some more testing. sleep first :) craig -- craig sanders <c...@taz.net.au> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org