No clue? It seems it fails because it prefers an IPv6 resolution on a machine that does not have it.
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
