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-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
