Tags Tags

Bug#678662: munin-update: Doesn't fall back to v4 when v6 address causes a connect error

June 23rd, 2012 - 11:20 am ET by Michael Renner | Report spam
Help Create a new topic
Package: munin
Version: 2.0.0-1
Severity: important
Tags: ipv6 upstream

When you specify a target via hostname which has both a v6 and v4
address munin tries to connect to the v6 address first and if this fails
bails out completely. This skips data collection for this host,
resulting in lost data points.

This is a regression compared to munin-update 1.4 which
doesn't have v6 support.

In a plain munin 2.0 environment one could argue that this is a
configuration error but since mixed version environments are quite
common the 2.0 munin-update should allow for dualstack clients specified
via hostname and 1.4 munin-nodes. This would require to either connect
in v4/v6 order or try to connect to all returned addresses instead of
bailing out after the first failed connect.

See also http://munin-monitoring.org/wiki/IPv6

all the best,
Michael



To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 1 replyReplies Make a reply

Replies

#1 Kenyon Ralph
June 23rd, 2012 - 04:30 pm ET | Report spam

severity 678662 wishlist
thanks

On 2012-06-23T15:11:52+0000, Michael Renner wrote:
Package: munin
Version: 2.0.0-1
Severity: important
Tags: ipv6 upstream

When you specify a target via hostname which has both a v6 and v4
address munin tries to connect to the v6 address first and if this fails
bails out completely. This skips data collection for this host,
resulting in lost data points.

This is a regression compared to munin-update 1.4 which
doesn't have v6 support.

In a plain munin 2.0 environment one could argue that this is a
configuration error but since mixed version environments are quite
common the 2.0 munin-update should allow for dualstack clients specified
via hostname and 1.4 munin-nodes. This would require to either connect
in v4/v6 order or try to connect to all returned addresses instead of
bailing out after the first failed connect.



Munin 1.4 nodes actually do have IPv6 support, provided you have the
necessary support in Perl's Net::Server. I have a munin-node 1.4.7 on
FreeBSD which is IPv6-only, polled by a 2.0 master. I also have an
Ubuntu munin-node 1.4.6 polled over IPv6. This is possible on Debian
squeeze too, if you use the squeeze-backports version of
libnet-server-perl. I think this is a reasonable fix, so I'm marking
this as "wishlist" severity.

See also http://munin-monitoring.org/wiki/IPv6



Kenyon Ralph






To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Similar topics

Make your own search :