search for: guyc

Thanks Gaurav! 1. Any time estimation on to when this fix would be released? 2. Any recommended workaround? Best, Guy. From: Gaurav Yadav [mailto:gyadav at redhat.com] Sent: Tuesday, June 20, 2017 9:46 AM To: Guy Cukierman <guyc at elminda.com> Cc: Atin Mukherjee <amukherj at redhat.com>; gluster-users at gluster.org Subject: Re: [Gluster-users] gluster peer probe failing Hi, I am able to recreate the issue and here is my RCA. Maximum value i.e 32767 is being overflowed while doing manipulation on it and it was p...

...> However with the logs you have sent it is prety much clear issue is > related to ports only. > > I will trying to reproduce on some other machine. Will update you as s0on > as possible. > > > Thanks > Gaurav > > On Sun, Jun 18, 2017 at 12:37 PM, Guy Cukierman <guyc at elminda.com> wrote: > >> Hi, >> >> Below please find the reserved ports and log, thanks. >> >> >> >> sysctl net.ipv4.ip_local_reserved_ports: >> >> net.ipv4.ip_local_reserved_ports = 30000-32767 >> >> >> >> >&...

...t I didn't see the issue on my machine locally. However with the logs you have sent it is prety much clear issue is related to ports only. I will trying to reproduce on some other machine. Will update you as s0on as possible. Thanks Gaurav On Sun, Jun 18, 2017 at 12:37 PM, Guy Cukierman <guyc at elminda.com> wrote: > Hi, > > Below please find the reserved ports and log, thanks. > > > > sysctl net.ipv4.ip_local_reserved_ports: > > net.ipv4.ip_local_reserved_ports = 30000-32767 > > > > > > glusterd.log: > > [2017-06-18 07:04:17.853162...

...30000-32767 net.ipv4.ip_local_port_range = 32768 60999 meaning the reserved ports are already in the short int range, so maybe I misunderstood something? or is it a different issue? From: Atin Mukherjee [mailto:amukherj at redhat.com] Sent: Thursday, June 15, 2017 10:56 AM To: Guy Cukierman <guyc at elminda.com> Cc: gluster-users at gluster.org Subject: Re: [Gluster-users] gluster peer probe failing https://review.gluster.org/#/c/17494/ will it and the next update of 3.10 should have this fix. If sysctl net.ipv4.ip_local_reserved_ports has any value > short int range then this woul...

...command please send the logs to look into the issue. Thanks Gaurav On Thu, Jun 15, 2017 at 4:28 PM, Atin Mukherjee <amukherj at redhat.com> wrote: > +Gaurav, he is the author of the patch, can you please comment here? > > > On Thu, Jun 15, 2017 at 3:28 PM, Guy Cukierman <guyc at elminda.com> wrote: > >> Thanks, but my current settings are: >> >> net.ipv4.ip_local_reserved_ports = 30000-32767 >> >> net.ipv4.ip_local_port_range = 32768 60999 >> >> meaning the reserved ports are already in the short int range, so maybe I &...

...o(+0x20f5e)[0x7fbdec7b1f5e] /lib64/libglusterfs.so.0(synctask_wrap+0x10)[0x7fbdf7ccd750] /lib64/libc.so.6(+0x46cf0)[0x7fbdf638bcf0] --------- From: Gaurav Yadav [mailto:gyadav at redhat.com] Sent: Friday, June 16, 2017 5:47 AM To: Atin Mukherjee <amukherj at redhat.com> Cc: Guy Cukierman <guyc at elminda.com>; gluster-users at gluster.org Subject: Re: [Gluster-users] gluster peer probe failing Could you please send me the output of command "sysctl net.ipv4.ip_local_reserved_ports". Apart from output of command please send the logs to look into the issue. Thanks Gaurav O...

+Gaurav, he is the author of the patch, can you please comment here? On Thu, Jun 15, 2017 at 3:28 PM, Guy Cukierman <guyc at elminda.com> wrote: > Thanks, but my current settings are: > > net.ipv4.ip_local_reserved_ports = 30000-32767 > > net.ipv4.ip_local_port_range = 32768 60999 > > meaning the reserved ports are already in the short int range, so maybe I > misunderstood something? or...

...date of 3.10 should have this fix. If sysctl net.ipv4.ip_local_reserved_ports has any value > short int range then this would be a problem with the current version. Would you be able to reset the reserved ports temporarily to get this going? On Wed, Jun 14, 2017 at 8:32 PM, Guy Cukierman <guyc at elminda.com> wrote: > Hi, > > I have a gluster (version 3.10.2) server running on a 3 node (centos7) > cluster. > > Firewalld and SELinux are disabled, and I see I can telnet from each node > to the other on port 24007. > > > > When I try to create the first...

Hi, I have a gluster (version 3.10.2) server running on a 3 node (centos7) cluster. Firewalld and SELinux are disabled, and I see I can telnet from each node to the other on port 24007. When I try to create the first peering by running on node1 the command: gluster peer probe <node2 ip address> I get the error: "Connection failed. Please check if gluster daemon is operational."

Hi, I'm having a similar issue, were you able to solve it? Thanks. Hey all, I've got a strange problem going on here. I've installed glusterfs-server on ubuntu 16.04: glusterfs-client/xenial,now 3.7.6-1ubuntu1 amd64 [installed,automatic] glusterfs-common/xenial,now 3.7.6-1ubuntu1 amd64 [installed,automatic] glusterfs-server/xenial,now 3.7.6-1ubuntu1 amd64 [installed] I can