-=| Craig Sanders, 28.09.2011 22:11:24 +1000 |=- > On Wed, Sep 28, 2011 at 02:29:38PM +0300, Damyan Ivanov wrote: > > > i've got several systems running munin-node, and those that have had > > > munin-node restarted recently are listening ONLY on ipv6. Those that > > > have been running since approx Sep 19 are listening correctly on ipv4. > > > > > > ganesh:/etc/munin# netstat -tupan | grep munin > > > tcp6 0 0 :::4949 :::* > > > LISTEN 8301/munin-node > > > > I have that too, but I am still able to connect on the regular ipv4 > > address. > > > > Are you really unable to connect to the ipv4 addresses? > > nope. i can't even telnet to 127.0.0.1:4949 or to $hostname:4949 (so the > munin server can't connect to gather data). > > as i said, i can force munin-node to listen on a single ipv4 address > with 'host ip.ip.ip.ip' in /etc/munin/munin-node.conf but if that > setting is left at the default 'host *', then it will ONLY listen on > ipv6 addresses since libnet-server-perl was upgraded to 0.99-3 > > downgrading libnet-server-perl to 0.99-2 fixes the problem.
I did read what you wrote :) Thing is, my munin-node accepts ipv4 connections with exact same LISTEN line as yours above. This makes me think there is something else different on your system. Can you try tcpdump and/or strace and see what exactly is happening?
signature.asc
Description: Digital signature
