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

2012-11-27 Thread intrigeri
Michael Renner wrote (26 Nov 2012 23:56:46 GMT) : Just verified with munin 2.0.6-1 on wheezy, still broken: [...] Just hacked MultiHomed in myself, this works fine when having dual stack munin-nodes only listening on v4 addresses. Thanks a lot! As Kenyon Ralph then indicated, this was fixed

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

2012-11-27 Thread intrigeri
tags 678662 + patch thanks Hi, intrigeri wrote (27 Nov 2012 10:19:15 GMT) : As Kenyon Ralph then indicated, this was fixed upstream accordingly. The relevant commit is a18229c522e1df5468a7dcb3a2f4c96aca56a761. Attached is a Git patch, against current debian branch, that imports this commit as

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

2012-11-27 Thread Holger Levsen
Hi intrigeri, On Dienstag, 27. November 2012, intrigeri wrote: As Kenyon Ralph then indicated, this was fixed upstream accordingly. The relevant commit is a18229c522e1df5468a7dcb3a2f4c96aca56a761. I'd love you to prepare debian/patches/ for me to pull ;-) Even more awesome if you'd accompany

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

2012-11-27 Thread intrigeri
Holger Levsen wrote (27 Nov 2012 10:55:50 GMT) : attachment missing :-D oops. here it is! commit b2393fcaeae01cfd815da5585084efb8da2f51cf Author: intrigeri intrig...@debian.org Date: Tue Nov 27 11:23:44 2012 +0100 Have master support multi-homed nodes that only listen on IPv4. (Closes:

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

2012-11-27 Thread intrigeri
Holger Levsen wrote (27 Nov 2012 10:34:39 GMT) : I'd love you to prepare debian/patches/ for me to pull ;-) Even more awesome if you'd accompany this with the commands to do it...) OK. Previous one was a bit harder to apply, but here is a real Git patch, prepared with git format-patch,

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

2012-11-26 Thread Michael Renner
On Nov 21, 2012, at 11:40 , intrigeri intrig...@debian.org wrote: Kenyon Ralph wrote (23 Jun 2012 20:17:28 GMT) : 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

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

2012-11-21 Thread intrigeri
Hi Michael, Kenyon Ralph wrote (23 Jun 2012 20:17:28 GMT) : 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.

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

2012-06-23 Thread Michael Renner
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

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

2012-06-23 Thread Kenyon Ralph
severity 678662 wishlist thanks On 2012-06-23T15:11:52+, Michael Renner r...@amd.co.at 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