Christos Tsalidis
2018-Jul-19 07:55 UTC
[Gluster-users] NFS tcp session cannot be established with gluster server
Hi, it seems there is a problem with rpc service. [root at gluster-workstation ~]# mount -vvv -t nfs -o rw gluster-node1:/replvol /mnt/replvol mount.nfs: timeout set for Thu Jul 19 09:53:01 2018 mount.nfs: trying text-based options 'vers=4.1,addr=192.168.70.151,clientaddr=192.168.70.153' mount.nfs: mount(2): Connection refused mount.nfs: trying text-based options 'addr=192.168.70.151' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: trying text-based options 'vers=4.1,addr=192.168.70.151,clientaddr=192.168.70.153' mount.nfs: mount(2): Connection refused mount.nfs: trying text-based options 'addr=192.168.70.151' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: trying text-based options 'vers=4.1,addr=192.168.70.151,clientaddr=192.168.70.153' mount.nfs: mount(2): Connection refused mount.nfs: trying text-based options 'addr=192.168.70.151' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered mount.nfs: trying text-based options 'vers=4.1,addr=192.168.70.151,clientaddr=192.168.70.153' mount.nfs: mount(2): Connection refused mount.nfs: trying text-based options 'addr=192.168.70.151' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered [root at gluster-node1 ~]# rpcinfo -p gluster-node1 program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 2018-07-18 12:35 GMT+02:00 John Hearns <hearnsj at googlemail.com>:> Run rpcinfo -p glusterfs1 > > My apology if that is already in your mail. > > On 18 July 2018 at 11:58, Christos Tsalidis <chtsalid at gmail.com> wrote: > >> Hi all, >> >> I am encountering the following problem, my nfs tcp session cannot be >> established with gluster server. Here are some outputs from debugging. >> >> >> [root at glusterfs1 ~]# glusterd --version >> glusterfs 3.12.11 >> Repository revision: git://git.gluster.org/glusterfs.git >> Copyright (c) 2006-2016 Red Hat, Inc. <gluster.org> >> GlusterFS comes with ABSOLUTELY NO WARRANTY. >> It is licensed to you under your choice of the GNU Lesser >> General Public License, version 3 or any later version (LGPLv3 >> or later), or the GNU General Public License, version 2 (GPLv2), >> in all cases as published by the Free Software Foundation. >> >> >> [root at glusterfs1 ~]# gluster volume info replvol >> >> Volume Name: replvol >> Type: Replicate >> Volume ID: 6d254f26-16cf-4c36-9510-0940be946a46 >> Status: Started >> Snapshot Count: 0 >> Number of Bricks: 1 x 2 = 2 >> Transport-type: tcp,rdma >> Bricks: >> Brick1: glusterfs1:/bricks/brick-a1/brick >> Brick2: glusterfs2:/bricks/brick-b1/brick >> Options Reconfigured: >> nfs.disable: off >> nfs.ports-insecure: on >> nfs.rpc-auth-allow: 192.168.70.0/24 >> performance.client-io-threads: off >> transport.address-family: inet >> nfs.transport-type: tcp >> >> >> >> [root at glusterfs-workstation ~]# ip a >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group >> default qlen 1000 >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >> inet 127.0.0.1/8 scope host lo >> valid_lft forever preferred_lft forever >> inet6 ::1/128 scope host >> valid_lft forever preferred_lft forever >> 2: ens32: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast >> state UP group default qlen 1000 >> link/ether 00:0c:29:32:35:e4 brd ff:ff:ff:ff:ff:ff >> inet 192.168.70.204/24 brd 192.168.70.255 scope global noprefixroute >> ens32 >> valid_lft forever preferred_lft forever >> inet6 fe80::20c:29ff:fe32:35e4/64 scope link noprefixroute >> valid_lft forever preferred_lft forever >> [root at glusterfs-workstation ~]# ping glusterfs1 >> PING glusterfs1.lab.local (192.168.70.200) 56(84) bytes of data. >> 64 bytes from glusterfs1.lab.local (192.168.70.200): icmp_seq=1 ttl=64 >> time=0.902 ms >> 64 bytes from glusterfs1.lab.local (192.168.70.200): icmp_seq=2 ttl=64 >> time=0.768 ms >> 64 bytes from glusterfs1.lab.local (192.168.70.200): icmp_seq=3 ttl=64 >> time=0.585 ms >> ^C >> --- glusterfs1.lab.local ping statistics --- >> 3 packets transmitted, 3 received, 0% packet loss, time 2005ms >> rtt min/avg/max/mdev = 0.585/0.751/0.902/0.133 ms >> >> >> >> [root at glusterfs-workstation ~]# cat /etc/fstab | grep nfs >> glusterfs1.lab.local:/replvol /mnt/mediadata nfs defaults,_netdev 0 0 >> [root at glusterfs-workstation ~]# mount -a >> mount.nfs: Connection refused >> >> >> I also attached a .pcap file, where you will see that server resets the >> tcp session. >> >> Any idea? >> >> Many thanks! >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> lists.gluster.org/mailman/listinfo/gluster-users >> > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <lists.gluster.org/pipermail/gluster-users/attachments/20180719/0957ddb2/attachment.html>