search for: 24008

...45.231099] W [MSGID: 114031] [client-rpc-fops.c:855:client3_3_writev_cbk] 2-scratch-client-0: remote operation failed [Transport endpoint is not connected] [2018-02-22 18:07:45.231112] W [MSGID: 103037] [rdma.c:3016:gf_rdma_submit_request] 2-rpc-transport/rdma: sending request to peer (172.17.2.255:24008) failed [2018-02-22 18:07:45.231123] W [rpc-clnt.c:1694:rpc_clnt_submit] 2-scratch-client-1: failed to submit rpc-request (XID: 0x5438e Program: GlusterFS 3.3, ProgVers: 330, Proc: 13) to rpc-transport (scratch-client-1) [2018-02-22 18:07:45.231130] W [MSGID: 103026] [rdma.c:2843:gf_rdma_writev] 2-...

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 open on...

...file??????????????? file=/etc/glusterd2/glusterd2.toml source="[config.go:163:main.initConfig]" DEBU[2018-04-04 09:28:16.946343] running with configuration??????????????????? cert-file= clientaddress="192.168.222.24:24007" config=/etc/glusterd2/glusterd2.toml defaultpeerport=24008 etcdcurls="http://192.168.222.24:2379" etcdendpoints="[]" etcdpurls="http://192.168.222.24:2380" key-file= localstatedir=/var/lib/glusterd2 logdir=/var/log/glusterd2 logfile=glusterd2.log loglevel=debug noembed=false peeraddress="192.168.222.24:24008" ru...

...file=/etc/glusterd2/glusterd2.toml > source="[config.go:163:main.initConfig]" > DEBU[2018-04-04 09:28:16.946343] running with > configuration cert-file= clientaddress="192.168.222.24: > 24007" config=/etc/glusterd2/glusterd2.toml defaultpeerport=24008 > etcdcurls="http://192.168.222.24:2379" etcdendpoints="[]" etcdpurls=" > http://192.168.222.24:2380" key-file= localstatedir=/var/lib/glusterd2 > logdir=/var/log/glusterd2 logfile=glusterd2.log loglevel=debug > noembed=false peeraddress="192.168.222.2...

...TCP connections I completely fail to use RDMA connections. I have 10 machines with IB NICs, and RDMA does work between them (verified using ib_write_bw -r and several other apps). When I configure a volume with RDMA I have a problem with the port at the client side. It keeps trying to get to port 24008, no matter what port the server actually listens on (in my case 24024). I've tried many options to set the ports, it doesn't seem to work either using the files under /etc/glusterd/vols/my_vol_ name/ or using gluster volume set my_vol_name transport.socket.listen-port (or any other option...

...would work since it's using the rsync over ssh for actual data push ? *?* *Port 22 (TCP):* Used by SSH for secure data communication in Geo-replication. *?* *Port 24007 (TCP):* Used by the Gluster daemon (glusterd) for management and to intercommunicate with other glusterd instances. *?* *Ports 24008 & 24009 (TCP):* Used for GlusterFS data and metadata operations. *?* *Port 49152 to 49664 (TCP):* Used by GlusterFS for client connections. I see some monitoring happening on the tcp ports for slave volume, is this communication secure ? -------------- next part -------------- An HTML attachmen...

Hi All. I am spawning gluster clusters in docker containers and in current architecture for every volume we want to spawn different set of containers possibly on the same group of servers. Ports used by glusterd/glusterfsd/glusterfs are: 24007 24008 49152 and higher There is a problem once I try to spawn a second gluster container on the same server since by default i tries to allocate the same ports as above. For ports used by bricks (49152 and higher) I found in /etc/glusterfs/glusterd.vol: option base-port 49152 But I do not see in manp...

...ecki" <radecki.rafal at gmail.com> wrote: Hi All. I am spawning gluster clusters in docker containers and in current architecture for every volume we want to spawn different set of containers possibly on the same group of servers. Ports used by glusterd/glusterfsd/glusterfs are: 24007 24008 49152 and higher There is a problem once I try to spawn a second gluster container on the same server since by default i tries to allocate the same ports as above. For ports used by bricks (49152 and higher) I found in /etc/glusterfs/glusterd.vol: option base-port 49152 But I do not see in manp...

...just 22 would work since it's using the rsync over ssh for actual data push ? ? Port 22 (TCP):?Used by SSH for secure data communication in Geo-replication. ? Port 24007 (TCP):?Used by the Gluster daemon (glusterd) for management and to intercommunicate with other glusterd instances. ? Ports 24008 & 24009 (TCP):?Used for GlusterFS data and metadata operations. ? Port 49152 to 49664 (TCP):?Used by GlusterFS for client connections. I see some monitoring happening on the tcp ports for slave volume, is this communication secure ?? ________ Community Meeting Calendar: Schedule - Ev...

...S 0:00 samba: task[wrepl] 24004 ? S 0:01 samba: task[ldapsrv] 24005 ? S 0:02 samba: task[cldapd] 24006 ? S 0:08 samba: conn[kdc_tcp] c[ipv4:192.168.0.88:40340] s[ipv4:192.168.0.6:88] server_id[24006.42] 24007 ? S 5:47 samba: task[dreplsrv] 24008 ? S 0:00 samba: task[winbindd_parent] 24009 ? S 0:00 samba: tfork waiter process 24010 ? S 0:00 samba: task[ntp_signd] 24011 ? S 0:06 samba: task[kccsrv] 24012 ? Ss 0:49 /usr/sbin/winbindd -D --option=server role check:inhibit=yes --foregro...

...or just 22 would work since it's using the rsync over ssh for actual data push ? ? Port 22 (TCP): Used by SSH for secure data communication in Geo-replication. ? Port 24007 (TCP): Used by the Gluster daemon (glusterd) for management and to intercommunicate with other glusterd instances. ? Ports 24008 & 24009 (TCP): Used for GlusterFS data and metadata operations. ? Port 49152 to 49664 (TCP): Used by GlusterFS for client connections. I see some monitoring happening on the tcp ports for slave volume, is this communication secure ? DISCLAIMER: This email and any files transmitted with it are...

On Wed, Mar 28, 2018 at 02:57:55PM +1300, Thing wrote: > Hi, > > Thanks, yes, not very familiar with Centos and hence googling took a while > to find a 4.0 version at, > > https://wiki.centos.org/SpecialInterestGroup/Storage The announcement for Gluster 4.0 in CentOS should contain all the details that you need as well:

...on=server role check:inhibit=yes --foreground 24003 ? S 0:00 samba: task[wrepl] 24004 ? S 0:01 samba: task[ldapsrv] 24005 ? S 0:02 samba: task[cldapd] 24006 ? S 0:08 samba: conn[kdc_tcp] c[ipv4:192.168.0.88:40340] s[ipv4:192.168.0.6:88] server_id[24006.42] 24007 ? S 5:47 samba: task[dreplsrv] 24008 ? S 0:00 samba: task[winbindd_parent] 24009 ? S 0:00 samba: tfork waiter process 24010 ? S 0:00 samba: task[ntp_signd] 24011 ? S 0:06 samba: task[kccsrv] 24012 ? Ss 0:49 /usr/sbin/winbindd -D --option=server role check:inhibit=yes --foreground 24013 ? S 0:16 samba: task[dnsupdate] 24020 ? S 0...

...       S      0:00 samba: task[wrepl] 24004 ?        S      0:01 samba: task[ldapsrv] 24005 ?        S      0:02 samba: task[cldapd] 24006 ?        S      0:08 samba: conn[kdc_tcp] c[ipv4:192.168.0.88:40340] s[ipv4:192.168.0.6:88] server_id[24006.42] 24007 ?        S      5:47 samba: task[dreplsrv] 24008 ?        S      0:00 samba: task[winbindd_parent] 24009 ?        S      0:00 samba: tfork waiter process 24010 ?        S      0:00 samba: task[ntp_signd] 24011 ?        S      0:06 samba: task[kccsrv] 24012 ?        Ss     0:49 /usr/sbin/winbindd -D --option=server role check:inhibit=yes --foregro...

On Wed, 13 Jun 2018 09:46:03 +0200 (CEST) Gaetan SLONGO <gslongo at it-optics.com> wrote: > Hi, > > Here is the current process list. We can see missing winbind and *mbd > processes : > > > > [root at dmzrodc ~]# netstat -plaunt | egrep "ntp|bind|named|samba|?mbd" I wouldn't worry about 'winbind' not being in the output of the above

...o an existing Kubernetes or OpenShift cluster * Access to a python interpreter 'python' Each of the nodes that will host GlusterFS must also have appropriate firewall rules for the required GlusterFS ports: * 2222 - sshd (if running GlusterFS in a pod) * 24007 - GlusterFS Management * 24008 - GlusterFS RDMA * 49152 to 49251 - Each brick for every volume on the host requires its own port. For every new brick, one new port will be used starting at 49152. We recommend a default range of 49152-49251 on each host, though you can adjust this to fit your needs. The following kerne...

centos 6.x gluster --version glusterfs 3.2.7 built on Jun 11 2012 13:22:29 The problem is that when i'm trying to probe like this: gluster peer probe [hostname] It never probe's because the firewall is blocking (when I turn it of on both sides everything works) But I want to keep the firewall running. A google search give's me serveral possible ports to open , so I

I set up a 3.3 gluster volume for another sysadmin and he has added it to his cluster via automount. It seems to work initially but after some time (days) he is now regularly seeing this warning: "Too many levels of symbolic links" $ df: `/share/gl': Too many levels of symbolic links when he tries to traverse the mounted filesystems. I've been using gluster with static mounts

...on=server role check:inhibit=yes --foreground 24003 ? S 0:00 samba: task[wrepl] 24004 ? S 0:01 samba: task[ldapsrv] 24005 ? S 0:02 samba: task[cldapd] 24006 ? S 0:08 samba: conn[kdc_tcp] c[ipv4:192.168.0.88:40340] s[ipv4:192.168.0.6:88] server_id[24006.42] 24007 ? S 5:47 samba: task[dreplsrv] 24008 ? S 0:00 samba: task[winbindd_parent] 24009 ? S 0:00 samba: tfork waiter process 24010 ? S 0:00 samba: task[ntp_signd] 24011 ? S 0:06 samba: task[kccsrv] 24012 ? Ss 0:49 /usr/sbin/winbindd -D --option=server role check:inhibit=yes --foreground 24013 ? S 0:16 samba: task[dnsupdate] 24020 ? S 0...

...168 [ 0.000000] DMA zone: 4096 pages used for memmap [ 0.000000] DMA zone: 0 pages reserved [ 0.000000] DMA zone: 262144 pages, LIFO batch:63 [ 0.000000] DMA32 zone: 4096 pages used for memmap [ 0.000000] DMA32 zone: 261632 pages, LIFO batch:63 [ 0.000000] Normal zone: 24008 pages used for memmap [ 0.000000] Normal zone: 1531392 pages, LIFO batch:63 [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.0 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: MIGRATE_INFO_TYPE not support...