On 06/02/2014, at 4:57 AM, Emmanuel Dreyfus wrote: > No clue? It seems it fails because it prefers an IPv6 resolution on a > machine that does not have it.
Out of curiosity, was this on a laptop with no IP addresses apart from localhost? I hit this exact same bit of code with my laptop on the way back from conferences on Thursday, when I was in an airport with no public WiFi (thus no IP address apart from localhost). _Could not get_ any volumes to start. Looked at the code briefly, found one possible bug with related headers, but fixing it doesn't solve the problem. Will think on this a bit. :) Regards and best wishes, Justin Clift > Emmanuel Dreyfus <m...@netbsd.org> wrote: > >> Was there a change regarding IPv6 and/or DNS resolution recently? >> >> I have this on 3.5beta2 client log (and quick failures using the volume) >> [2014-02-03 20:46:27.049250] E [common-utils.c:222:gf_resolve_ip6] >> 0-resolver: getaddrinfo failed (No address associated with hostname) >> [2014-02-03 20:46:27.049458] E >> [name.c:249:af_inet_client_get_remote_sockaddr] 0-gfs35b2-client-1: DNS >> resolution failed on host hangar > > > -- > Emmanuel Dreyfus > http://hcpnet.free.fr/pubz > m...@netbsd.org > > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@nongnu.org > https://lists.nongnu.org/mailman/listinfo/gluster-devel -- Open Source and Standards @ Red Hat twitter.com/realjustinclift _______________________________________________ Gluster-devel mailing list Gluster-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/gluster-devel
