munged does not work on IPv6-only hosts - unable to resolve host

[GoogleCodeExporter]

What steps will reproduce the problem?

Configure host to be IPv6-only and start munged.

What is the expected output? What do you see instead?

munged should work on hosts configured for IPv4 and/or IPv6. But on IPv6-only hosts, munged is unable to resolve its hostname:

# /etc/init.d/munge start
Starting MUNGE: mungedmunged: Error: Unable to resolve host "foo"
                                                           [FAILED]

What version of the software are you using? On what operating system?

munge-0.5.10

Please provide any additional information below.

All of the MUNGE communications are over a local Unix domain socket, and as such, are unaffected by IPv6.

But when munged starts, it calls gethostname() to obtain the hostname, and gethostbyname() to resolve its IPv4 address. This IPv4 address is embedded into the metadata when encoding credentials.

Since the IP address here is not strictly required for authentication, munged should treat a hostname resolution failure as a warning and continue its execution using an IPv4 address of 0.0.0.0.

Reported by Tomas Kouba on 2013-02-08.

Original issue reported on code.google.com by chris.m.dunlap on 11 Feb 2013 at 8:01

[GoogleCodeExporter]

This issue was closed by da3c7ff.

Original comment by chris.m.dunlap on 2 May 2013 at 8:25

• Changed state: Fixed