On Mon, Mar 5, 2012 at 2:32 PM, Brad Alexander <stor...@gmail.com> wrote: > On Mon, Mar 5, 2012 at 1:30 AM, Wolfgang Karall <li...@karall-edv.at> wrote: >> On Sun, Mar 04, 2012 at 06:44:47PM -0500, Brad Alexander wrote: >>> >>> Yes. Non-working: >>> >>> echo -e 'list\nquit' | nc 192.168.4.9 4949 >>> (UNKNOWN) [192.168.4.9] 4949 (munin) : Connection refused >> >> Hmm, since Bob suggest a bug in recent versions (I don't know, not >> running wheezy or sid on any munin-node installations at the moment), >> could you try disabling IPv6 and try again? >> >> And if this is really a bug with munin-node not working with IPv6 >> enabled this needs to be reported to the BTS. > > Disabled ipv6 both through /etc/modprobe.d/aliases and through /proc, > and it didn't make a difference. Connection still refused on port 4949 > when telnetting to localhost. > > I'm beginning to wonder if it is a missing or interfering package.
On sid, ipv6 is compiled in to the kernel so it can only be disabled via "ipv6.disable=1" on the "linux" line in "grub.cfg". If you've compiled your own kernel with ipv6 as a module, have you tried disabling ipv6 with "install ipv6 /bin/true" in "/etc/modprobe.d/ipv6.conf" and rebuilt the initrd after running "depmod -a"? Is "cat /proc/sys/net/ipv6/bindv6only" the same on working and non-working nodes? This setting restricts the ipv6 socket to ipv6 (or not) and had created problems in the past for some apps. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=sznpu4+biw2v-jak4ttgqmzrpnv6xui83hctjbc0vv...@mail.gmail.com
