Bug#643654: munin-node won't listen on ipv4 addresses after upgrading to libnet-server-perl 0.99-3

Craig Sanders cas at taz.net.au
Wed Sep 28 11:18:26 UTC 2011


Package: libnet-server-perl
Version: 0.99-3

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.

All are running munin-node 1.4.6-1, and all are kept up-to-date with
debian sid. all upgraded today, but munin-node was only restarted on
some. the most likely culprit is libnet-server-perl which was upgraded
from 0.99-2 to 0.99-3 around September 20.

changelog.Debian.gz for libnet-server-perl mentions:

  * took IPv6 patch from bug report, improved and included it as 05_ipv6-support.dpatch.  (closes: Bug#523846)

ipv6 support is nice i suppose, but not at the expense of ipv4 support.


e.g.

kali:/etc/munin# netstat -tupan | grep munin
tcp        0      0 0.0.0.0:4949            0.0.0.0:*               LISTEN      2646/munin-node

kali:/etc/munin# ps aux | grep [m]unin
root      2646  0.0  0.0  44328  8624 ?        Ss   Sep19   0:55 /usr/sbin/munin-node


ganesh:/etc/munin# netstat -tupan | grep munin
tcp6       0      0 :::4949                 :::*                    LISTEN      8301/munin-node

ganesh:/etc/munin# ps aux | grep [m]unin
root      8301  0.0  0.0  49676 10300 ?        Ss   20:20   0:00 /usr/sbin/munin-node


Both systems above (in fact, all my systems) are configured with 'host
*' in munin-node.conf.  I have forced one machine to listen on ipv4 by
putting 'host ip.ip.ip.ip' in munin-node.conf - but that only allows it
to listen on ONE ipv4 address, not all of them. worse, i would have to
maintain individual munin-node.conf files for each machine rather than
just scp or pdcp the same munin-node.conf to every box.


this may be a bug in libnet-server-perl, or it may be a bug in
munin-node (might need changes to cope with lbnet-server-perl
0.99-3).  I can't tell. feel free to reassign this bug if it belongs
to munin-node. or merge this report into #523846 if that's more
appropriate.


[5 mins later]

BTW, downgrading to libnet-server-perl 0.99-2 does fix the problem, so
i'm submitting this for libnet-server-perl rather than munin-node (i was
originally going to submit it for munin-node 1.46-1)

ganesh:/# dpkg -i /export/ftp/debian/pool/main/libn/libnet-server-perl/libnet-server-perl_0.99-2_all.deb
dpkg: warning: downgrading libnet-server-perl from 0.99-3 to 0.99-2.
(Reading database ... 878378 files and directories currently installed.)
Preparing to replace libnet-server-perl 0.99-3 (using .../libnet-server-perl_0.99-2_all.deb) ...
Unpacking replacement libnet-server-perl ...
Setting up libnet-server-perl (0.99-2) ...
Processing triggers for man-db ...

ganesh:/# /etc/init.d/munin-node restart
Stopping Munin-Node: done.
Starting Munin-Node: done.

ganesh:/# netstat -tupan | grep munin
tcp        0      0 0.0.0.0:4949            0.0.0.0:*               LISTEN      14875/munin-node


craig

-- 
craig sanders <cas at taz.net.au>





More information about the pkg-perl-maintainers mailing list