ML mail
2015-Mar-03 11:38 UTC
[Gluster-users] /etc/hosts entry requires for gluster servers?
Well the weird thing is that my DNS resolver servers are configured correctly and working fine. Here below is the exact error message from the brick log file: [2015-03-03 11:34:21.731639] E [common-utils.c:223:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Name or service not known) [2015-03-03 11:34:21.731654] E [name.c:249:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution failed on host gfs1.intra.domain.com [2015-03-03 11:34:21.731707] E [glusterfsd-mgmt.c:1601:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: gfs1.intra.domain.com (Success) [2015-03-03 11:34:21.731724] I [glusterfsd-mgmt.c:1607:mgmt_rpc_notify] 0-glusterfsd-mgmt: Exhausted all volfile servers I checked in my /etc/hosts file and I have the following entry: 127.0.1.1 gfs1.intra.domain.com gfs1a This is Debian's default and did not touch the hosts file. I also tried to remove this 127.0.1.1 but nothing changed. On Tuesday, March 3, 2015 10:33 AM, Claudio Kuenzler <ck at claudiokuenzler.com> wrote: Hi ML, Here's what I have noted down in my personal documentation when I installed GlusterFS the first time in 2013 (also on Debian Wheezy with 3.5.2): "All cluster nodes MUST resolve each other through DNS (preferred) or /etc/hosts." An entry in /etc/hosts is probably even more safe because you don't depend on external DNS resolvers. cheers,ck On Tue, Mar 3, 2015 at 8:43 AM, ML mail <mlnospam at yahoo.com> wrote: Hello,> >Is it required to have the GlusterFS servers in /etc/hosts for the gluster servers themselves? I read many tutorials where people always add an entry in their /etc/hosts file. > >I am asking because my issue is that my volumes, or more precisely glusterfsd, are not starting at system boot. The brick log shows that the hostname of the server could not be resolved but I have an entry in my DNS server and my /etc/resolv.conf is configured correctly. > > >I am using Debian Wheezy with GlusterFS 3.5.2. > >Best regards >ML >_______________________________________________ >Gluster-users mailing list >Gluster-users at gluster.org >http://www.gluster.org/mailman/listinfo/gluster-users >
Claudio Kuenzler
2015-Mar-03 11:57 UTC
[Gluster-users] /etc/hosts entry requires for gluster servers?
Can you resolve the other gluster peers with "dig"? Are you able to "ping" the other peers, too? On Tue, Mar 3, 2015 at 12:38 PM, ML mail <mlnospam at yahoo.com> wrote:> Well the weird thing is that my DNS resolver servers are configured > correctly and working fine. Here below is the exact error message from the > brick log file: > > [2015-03-03 11:34:21.731639] E [common-utils.c:223:gf_resolve_ip6] > 0-resolver: getaddrinfo failed (Name or service not known) > [2015-03-03 11:34:21.731654] E > [name.c:249:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution > failed on host gfs1.intra.domain.com > [2015-03-03 11:34:21.731707] E [glusterfsd-mgmt.c:1601:mgmt_rpc_notify] > 0-glusterfsd-mgmt: failed to connect with remote-host: > gfs1.intra.domain.com (Success) > [2015-03-03 11:34:21.731724] I [glusterfsd-mgmt.c:1607:mgmt_rpc_notify] > 0-glusterfsd-mgmt: Exhausted all volfile servers > > I checked in my /etc/hosts file and I have the following entry: > > > 127.0.1.1 gfs1.intra.domain.com gfs1a > > This is Debian's default and did not touch the hosts file. I also tried to > remove this 127.0.1.1 but nothing changed. > > > On Tuesday, March 3, 2015 10:33 AM, Claudio Kuenzler < > ck at claudiokuenzler.com> wrote: > > > > Hi ML, > > Here's what I have noted down in my personal documentation when I > installed GlusterFS the first time in 2013 (also on Debian Wheezy with > 3.5.2): > > "All cluster nodes MUST resolve each other through DNS (preferred) or > /etc/hosts." > An entry in /etc/hosts is probably even more safe because you don't depend > on external DNS resolvers. > cheers,ck > > > On Tue, Mar 3, 2015 at 8:43 AM, ML mail <mlnospam at yahoo.com> wrote: > > Hello, > > > >Is it required to have the GlusterFS servers in /etc/hosts for the > gluster servers themselves? I read many tutorials where people always add > an entry in their /etc/hosts file. > > > >I am asking because my issue is that my volumes, or more precisely > glusterfsd, are not starting at system boot. The brick log shows that the > hostname of the server could not be resolved but I have an entry in my DNS > server and my /etc/resolv.conf is configured correctly. > > > > > >I am using Debian Wheezy with GlusterFS 3.5.2. > > > >Best regards > >ML > >_______________________________________________ > >Gluster-users mailing list > >Gluster-users at gluster.org > >http://www.gluster.org/mailman/listinfo/gluster-users > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150303/27b6470b/attachment.html>
Atin Mukherjee
2015-Mar-03 12:11 UTC
[Gluster-users] /etc/hosts entry requires for gluster servers?
While probing new nodes have you used mixed flavour of fqdn like short names, long names? Can you please paste peer status output here? ~Atin On 03/03/2015 05:08 PM, ML mail wrote:> Well the weird thing is that my DNS resolver servers are configured correctly and working fine. Here below is the exact error message from the brick log file: > > [2015-03-03 11:34:21.731639] E [common-utils.c:223:gf_resolve_ip6] 0-resolver: getaddrinfo failed (Name or service not known) > [2015-03-03 11:34:21.731654] E [name.c:249:af_inet_client_get_remote_sockaddr] 0-glusterfs: DNS resolution failed on host gfs1.intra.domain.com > [2015-03-03 11:34:21.731707] E [glusterfsd-mgmt.c:1601:mgmt_rpc_notify] 0-glusterfsd-mgmt: failed to connect with remote-host: gfs1.intra.domain.com (Success) > [2015-03-03 11:34:21.731724] I [glusterfsd-mgmt.c:1607:mgmt_rpc_notify] 0-glusterfsd-mgmt: Exhausted all volfile servers > > I checked in my /etc/hosts file and I have the following entry: > > > 127.0.1.1 gfs1.intra.domain.com gfs1a > > This is Debian's default and did not touch the hosts file. I also tried to remove this 127.0.1.1 but nothing changed. > > > On Tuesday, March 3, 2015 10:33 AM, Claudio Kuenzler <ck at claudiokuenzler.com> wrote: > > > > Hi ML, > > Here's what I have noted down in my personal documentation when I installed GlusterFS the first time in 2013 (also on Debian Wheezy with 3.5.2): > > "All cluster nodes MUST resolve each other through DNS (preferred) or /etc/hosts." > An entry in /etc/hosts is probably even more safe because you don't depend on external DNS resolvers. > cheers,ck > > > On Tue, Mar 3, 2015 at 8:43 AM, ML mail <mlnospam at yahoo.com> wrote: > > Hello, >> >> Is it required to have the GlusterFS servers in /etc/hosts for the gluster servers themselves? I read many tutorials where people always add an entry in their /etc/hosts file. >> >> I am asking because my issue is that my volumes, or more precisely glusterfsd, are not starting at system boot. The brick log shows that the hostname of the server could not be resolved but I have an entry in my DNS server and my /etc/resolv.conf is configured correctly. >> >> >> I am using Debian Wheezy with GlusterFS 3.5.2. >> >> Best regards >> ML >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> http://www.gluster.org/mailman/listinfo/gluster-users >> > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users > >-- ~Atin