search for: 24007

...system polling thread [2017-08-20 20:30:40.382343] D [rpc-clnt.c:1581:rpcclnt_cbk_program_register] 0-glusterfs: New program registered: GlusterFS Callback, Num: 52743234, Ver: 1 [2017-08-20 20:30:40.466338] D [MSGID: 0] [common-utils.c:327:gf_resolve_ip6] 0-resolver: returning ip-192.168.1.8 (port-24007) for hostname: web1.dasilva.network and port: 24007 [2017-08-20 20:30:40.466364] D [MSGID: 0] [common-utils.c:327:gf_resolve_ip6] 0-resolver: returning ip-192.168.1.8 (port-24007) for hostname: web1.dasilva.network and port: 24007 [2017-08-20 20:30:40.466470] D [MSGID: 0] [common-utils.c:348:gf_res...

...; [2017-08-20 20:30:40.382343] D [rpc-clnt.c:1581:rpcclnt_cbk_program_register] > 0-glusterfs: New program registered: GlusterFS Callback, Num: 52743234, > Ver: 1 > [2017-08-20 20:30:40.466338] D [MSGID: 0] [common-utils.c:327:gf_resolve_ip6] > 0-resolver: returning ip-192.168.1.8 (port-24007) for hostname: > web1.dasilva.network and port: 24007 > [2017-08-20 20:30:40.466364] D [MSGID: 0] [common-utils.c:327:gf_resolve_ip6] > 0-resolver: returning ip-192.168.1.8 (port-24007) for hostname: > web1.dasilva.network and port: 24007 > [2017-08-20 20:30:40.466470] D [MSGID: 0] [...

...:30:40.382343] D [rpc-clnt.c:1581:rpcclnt_cbk_program_register] >> 0-glusterfs: New program registered: GlusterFS Callback, Num: 52743234, >> Ver: 1 >> [2017-08-20 20:30:40.466338] D [MSGID: 0] [common-utils.c:327:gf_resolve_ip6] >> 0-resolver: returning ip-192.168.1.8 (port-24007) for hostname: >> web1.dasilva.network and port: 24007 >> [2017-08-20 20:30:40.466364] D [MSGID: 0] [common-utils.c:327:gf_resolve_ip6] >> 0-resolver: returning ip-192.168.1.8 (port-24007) for hostname: >> web1.dasilva.network and port: 24007 >> [2017-08-20 20:30:40.46...

...on ubuntu 16.04 and everything is working ok so far, but I experience a weird problem with glustershd. On all servers I get following error: Aug 18 22:13:55 ws1 glustershd[16078]: [2017-08-18 20:13:55.604910] E [socket.c:3287:socket_connect] 0-igrepo-client-3: connection attempt on 94.xxx.xxx.xxx:24007 failed, (Cannot assign requested address) This error is reported for all volumes on all servers. Interesting is that netstat shows that port 24007 is actually already listening and there are established connections: tcp 0 0 0.0.0.0:24007 0.0.0.0:* LISTEN Glust...

That makes for an interesting problem. I cannot open port 24007 to allow RPC access. On 02/07/2018 11:29 PM, Kotresh Hiremath Ravishankar wrote: > Hi Alvin, > > Yes, geo-replication sync happens via SSH. Ther server port 24007 is > of glusterd. > glusterd will be listening in this port and all volume management > communication > happens...

Reading the documentation there is conflicting information: According to https://wiki.centos.org/HowTos/GlusterFSonCentOS we only need port TCP open between 2 GlusterFS servers: Ports TCP:24007-24008 are required for communication between GlusterFS nodes and each brick requires another TCP port starting at 24009. According to https://gluster.readthedocs.io/en/latest/Administrator%20Guide/Setting%20Up%20Clients/ we also need to open UPD: Ensure that TCP and UDP ports 24007 and 24008 are o...

...PT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -s 172.22.0.0/16 -p tcp -m tcp --dport 49152:49664 -m conntrack --ctstate NEW -j ACCEPT -A INPUT -s 10.3.3.0/25 -p tcp -m tcp --dport 49152:49664 -m conntrack --ctstate NEW -j ACCEPT -A INPUT -s 172.22.0.0/16 -p tcp -m tcp --dport 24007 -m conntrack --ctstate NEW -j ACCEPT -A INPUT -s 10.3.3.0/25 -p tcp -m tcp --dport 24007 -m conntrack --ctstate NEW -j ACCEPT -A INPUT -s 10.3.3.0/25 -p tcp -m tcp --dport 22 -m conntrack --ctstate NEW -j ACCEPT -A INPUT -s 10.3.7.0/25 -p tcp -m tcp --dport 22 -m conntrack --ctstate NEW -j ACCEP...

I am running gluster 3.8.9 and trying to setup a geo-replicated volume over ssh, It looks like the volume create command is trying to directly access the server over port 24007. The docs imply that all communications are over ssh. What am I missing? -- Alvin Starr || land: (905)513-7688 Netvel Inc. || Cell: (416)806-0133 alvin at netvel.net || -------------- next part -------------- An HTML attachment was scrubbe...

Ccing glusterd team for information On Thu, Feb 8, 2018 at 10:02 AM, Alvin Starr <alvin at netvel.net> wrote: > That makes for an interesting problem. > > I cannot open port 24007 to allow RPC access. > > On 02/07/2018 11:29 PM, Kotresh Hiremath Ravishankar wrote: > > Hi Alvin, > > Yes, geo-replication sync happens via SSH. Ther server port 24007 is of > glusterd. > glusterd will be listening in this port and all volume management > communication &...

Hi Alvin, Yes, geo-replication sync happens via SSH. Ther server port 24007 is of glusterd. glusterd will be listening in this port and all volume management communication happens via RPC. Thanks, Kotresh HR On Wed, Feb 7, 2018 at 8:29 PM, Alvin Starr <alvin at netvel.net> wrote: > I am running gluster 3.8.9 and trying to setup a geo-replicated volume > over...

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." And Glusterd.log shows: [2017-06-14 14:46:09.927510] I [MSGID: 106487] [glusterd-ha...

Hi, Unable to do peer probe... and unable to figure out whats the reason from the gluster log. can someone help ? 1) This is what i was trying... gluster> peer probe llm19.in.ibm.com Probe unsuccessful Probe returned with unknown errno 107 gluster> peer probe 9.124.111.25 Probe unsuccessful Probe returned with unknown errno 107 gluster> peer status Number of Peers: 1 Hostname:

...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 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 ope...

...th=/var/lib/libvirt/qemu/test.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot order=dc,menu=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=gluster:// 127.0.0.1:24007/gv1/test.img,if=none,id=drive-virtio-disk0,cache=none-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:cf:d2:62,bus=pci.0,addr=0x3 -chardev pty,id=...

...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 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.? > > > > And Glusterd.log...

...net.ipv4.ip_local_reserved_ports: > > net.ipv4.ip_local_reserved_ports = 30000-32767 > > > > > > glusterd.log: > > [2017-06-18 07:04:17.853162] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe] > 0-glusterd: Received CLI probe req 192.168.1.17 24007 > > [2017-06-18 07:04:17.853237] D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr] > 0-management: 192.168.1.17 > > [2017-06-18 07:04:17.854093] D [logging.c:1952:_gf_msg_internal] > 0-logging-infra: Buffer overflow of a buffer whose size limit is 5. About > to flush least re...

...ease 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] I [MSGID: 106487] [glusterd-handler.c:1242:__glusterd_handle_cli_probe] 0-glusterd: Received CLI probe req 192.168.1.17 24007 [2017-06-18 07:04:17.853237] D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr] 0-management: 192.168.1.17 [2017-06-18 07:04:17.854093] D [logging.c:1952:_gf_msg_internal] 0-logging-infra: Buffer overflow of a buffer whose size limit is 5. About to flush least recently used log message to disk The...

...g? On Wed, Jun 14, 2017 at 8:32 PM, Guy Cukierman <guyc at elminda.com<mailto: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 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.? And Glusterd.log shows: [2017-06-14 14:46:09.927510] I [MSGID: 106487] [glusterd-handler.c:12...

...T -i lo -j ACCEPT > > -A INPUT -s 172.22.0.0/16 -p tcp -m tcp --dport 49152:49664 -m > conntrack --ctstate NEW -j ACCEPT > > -A INPUT -s 10.3.3.0/25 -p tcp -m tcp --dport 49152:49664 -m conntrack > --ctstate NEW -j ACCEPT > > -A INPUT -s 172.22.0.0/16 -p tcp -m tcp --dport 24007 -m conntrack > --ctstate NEW -j ACCEPT > > -A INPUT -s 10.3.3.0/25 -p tcp -m tcp --dport 24007 -m conntrack > --ctstate NEW -j ACCEPT > > -A INPUT -s 10.3.3.0/25 -p tcp -m tcp --dport 22 -m conntrack > --ctstate NEW -j ACCEPT > > -A INPUT -s 10.3.7.0/25 -p tcp -m tcp -...

...net.ipv4.ip_local_reserved_ports = 30000-32767 >> >> >> >> >> >> glusterd.log: >> >> [2017-06-18 07:04:17.853162] I [MSGID: 106487] >> [glusterd-handler.c:1242:__glusterd_handle_cli_probe] 0-glusterd: >> Received CLI probe req 192.168.1.17 24007 >> >> [2017-06-18 07:04:17.853237] D [MSGID: 0] [common-utils.c:3361:gf_is_local_addr] >> 0-management: 192.168.1.17 >> >> [2017-06-18 07:04:17.854093] D [logging.c:1952:_gf_msg_internal] >> 0-logging-infra: Buffer overflow of a buffer whose size limit is 5. Abou...