search for: client_query_portmap_cbk

I have glusterfs 3.1.2 running on Debian, I'm able to start the volume and now mount it via mount -t gluster and I can see everything. I am still seeing the following error in /var/log/glusterfs/nfs.log [2011-02-04 13:09:16.404851] E [client-handshake.c:1079:client_query_portmap_cbk] bhl-volume-client-98: failed to get the port number for remote subvolume [2011-02-04 13:09:16.404909] I [client.c:1590:client_rpc_notify] bhl-volume-client-98: disconnected [2011-02-04 13:09:20.405843] E [client-handshake.c:1079:client_query_portmap_cbk] bhl-volume-client-98: failed to get the por...

...ailable" >> [2018-04-09 05:08:13.747372] I [MSGID: 114020] [client.c:2360:notify] >> 0-gv01-client-1: parent translators are ready, attempting connect on >> transport >> [2018-04-09 05:08:13.747883] E [MSGID: 114058] >> [client-handshake.c:1571:client_query_portmap_cbk] 0-gv01-client-0: >> failed to get the port number for remote subvolume. Please run >> 'gluster >> volume status' on server to see if brick process is running. >> [2018-04-09 05:08:13.748026] I [MSGID: 114018] >> [client.c:2285:client_rpc_notify...

...ocol not > available" > [2018-04-09 05:08:13.747372] I [MSGID: 114020] [client.c:2360:notify] > 0-gv01-client-1: parent translators are ready, attempting connect on > transport > [2018-04-09 05:08:13.747883] E [MSGID: 114058] > [client-handshake.c:1571:client_query_portmap_cbk] 0-gv01-client-0: > failed to get the port number for remote subvolume. Please run 'gluster > volume status' on server to see if brick process is running. > [2018-04-09 05:08:13.748026] I [MSGID: 114018] > [client.c:2285:client_rpc_notify] 0-gv01-client-0: discon...

...'s port is available [2018-05-03 04:32:18.009610] E [MSGID: 108006] [afr-common.c:5164:__afr_handle_child_down_event] 0-gv01-replicate-0: All subvolumes are down. Going offline until atleast one of them comes back up. [2018-05-01 22:43:06.412067] E [MSGID: 114058] [client-handshake.c:1571:client_query_portmap_cbk] 0-gv01-client-1: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running. [2018-05-01 22:43:55.554833] E [socket.c:2374:socket_connect_finish] 0-gv01-client-0: connection to 192.168.0.131:49152 failed (Connectio...

...nnect] 0-glusterfs: Error disabling sockopt IPV6_V6ONLY: "Protocollo non disponibile" [2018-02-24 15:32:00.915854] I [MSGID: 101190] [event-epoll.c:613:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1 [2018-02-24 15:32:01.925714] E [MSGID: 114058] [client-handshake.c:1571:client_query_portmap_cbk] 0-datastore_temp-client-1: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running. [2018-02-24 15:32:01.926632] E [MSGID: 114058] [client-handshake.c:1571:client_query_portmap_cbk] 0-datastore_temp-client-2: faile...

...'t even ^C it and have to kill my ssh session. I found the log file pertaining to the mount operation: /var/log/glusterfs/mnt-gtest.log which contains many repeats of the following line (with datetime incrementing by 3s up to the present): [2010-10-31 21:35:43.585271] E [client-handshake.c:773:client_query_portmap_cbk] client: failed to get the port number for remote subvolume Can anyone suggest the next step in diagnosing this problem?

...0: Error disabling sockopt IPV6_V6ONLY: "Protocol not available" [2018-04-09 05:08:13.747372] I [MSGID: 114020] [client.c:2360:notify] 0-gv01-client-1: parent translators are ready, attempting connect on transport [2018-04-09 05:08:13.747883] E [MSGID: 114058] [client-handshake.c:1571:client_query_portmap_cbk] 0-gv01-client-0: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running. [2018-04-09 05:08:13.748026] I [MSGID: 114018] [client.c:2285:client_rpc_notify] 0-gv01-client-0: disconnected from gv01-client-0. Clien...

...IPV6_V6ONLY: "Protocol not > available" > [2018-04-09 05:08:13.747372] I [MSGID: 114020] [client.c:2360:notify] > 0-gv01-client-1: parent translators are ready, attempting connect on > transport > [2018-04-09 05:08:13.747883] E [MSGID: 114058] > [client-handshake.c:1571:client_query_portmap_cbk] 0-gv01-client-0: > failed to get the port number for remote subvolume. Please run 'gluster > volume status' on server to see if brick process is running. > [2018-04-09 05:08:13.748026] I [MSGID: 114018] > [client.c:2285:client_rpc_notify] 0-gv01-client-0: disconnected from >...

...type debug/io-stats 54: option latency-measurement off 55: option count-fop-hits off 56: subvolumes gluster-vol01-stat-prefetch 57: end-volume +------------------------------------------------------------------------------+ [2011-07-11 10:19:51.870501] E [client-handshake.c:1163:client_query_portmap_cbk] 0-gluster-vol01-client-0: failed to get the port number for remote subvolume [2011-07-11 10:19:51.871344] I [client.c:1883:client_rpc_notify] 0-gluster-vol01-client-0: disconnected [2011-07-11 10:19:51.871722] E [client-handshake.c:1163:client_query_portmap_cbk] 0-gluster-vol01-client-2: failed to...

...3 04:32:18.009610] E [MSGID: 108006] > [afr-common.c:5164:__afr_handle_child_down_event] 0-gv01-replicate-0: > All subvolumes are down. Going offline until atleast one of them comes > back up. > > > [2018-05-01 22:43:06.412067] E [MSGID: 114058] > [client-handshake.c:1571:client_query_portmap_cbk] 0-gv01-client-1: > failed to get the port number for remote subvolume. Please run 'gluster > volume status' on server to see if brick process is running. > [2018-05-01 22:43:55.554833] E [socket.c:2374:socket_connect_finish] > 0-gv01-client-0: connection to 192.168.0.131:491...

On Mon, Jan 15, 2018 at 6:30 PM, ?? <chenxi at shudun.com> wrote: > Using the host name of the volume, its related gluster commands can become > very slow .For example,create,start,stop volume,nfs related commands. and > some time And in some cases, the command will return Error : Request timed > out > but If using ip address to create the volume. The volume all gluster >

Using the host name of the volume, its related gluster commands can become very slow .For example,create,start,stop volume,nfs related commands. and some time And in some cases, the command will return Error : Request timed out but If using ip address to create the volume. The volume all gluster commands are normal. I have configured /etc/hosts correctly,Because,SSH can normally use the

...fs/mnt-gluster-c1_2.log <== 82: type meta 83: subvolumes c1 84: end-volume 85: +------------------------------------------------------------------------------+ /DAEMON/ERR [2017-05-24T10:39:11.130038+02:00] [] [] [2017-05-24 08:39:11.130638] E [MSGID: 114058] [client-handshake.c:1538:client_query_portmap_cbk] 2-c1-client-1: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running. [2017-05-24 08:39:11.130693] I [MSGID: 114018] [client.c:2276:client_rpc_notify] 2-c1-client-1: disconnected from c1-client-1. Client process...

...fs/mnt-gluster-c1_2.log <== 82: type meta 83: subvolumes c1 84: end-volume 85: +------------------------------------------------------------------------------+ /DAEMON/ERR [2017-05-24T10:39:11.130038+02:00] [] [] [2017-05-24 08:39:11.130638] E [MSGID: 114058] [client-handshake.c:1538:client_query_portmap_cbk] 2-c1-client-1: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running. [2017-05-24 08:39:11.130693] I [MSGID: 114018] [client.c:2276:client_rpc_notify] 2-c1-client-1: disconnected from c1-client-1. Client process...

...82: type meta > 83: subvolumes c1 > 84: end-volume > 85: > +------------------------------------------------------------------------------+ > /DAEMON/ERR [2017-05-24T10:39:11.130038+02:00] [] [] > [2017-05-24 08:39:11.130638] E [MSGID: 114058] [client-handshake.c:1538:client_query_portmap_cbk] 2-c1-client-1: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running. > [2017-05-24 08:39:11.130693] I [MSGID: 114018] [client.c:2276:client_rpc_notify] 2-c1-client-1: disconnected from c1-client-1. Client pro...

...-scratch-client-0: remote operation failed [Transport endpoint is not connected] [2018-02-22 18:07:45.237431] W [MSGID: 103026] [rdma.c:2843:gf_rdma_writev] 2-scratch-client-0: rdma is not connected to peer (172.17.2.254:24008) [2018-02-22 18:07:45.237430] W [MSGID: 114032] [client-handshake.c:1508:client_query_portmap_cbk] 2-scratch-client-0: received RPC status error, try again later [Transport endpoint is not connected] [2018-02-22 18:07:45.237450] W [MSGID: 103037] [rdma.c:3016:gf_rdma_submit_request] 2-rpc-transport/rdma: sending request to peer (172.17.2.254:24008) failed [2018-02-22 18:07:45.237458] W [rpc-cln...

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

...[MSGID: 114031] [client-rpc-fops.c:2928:client3_3_lookup_cbk] 0-home-client-2: remote operation failed. Path: <gfid:5e59154a-c15b-4d11-a3a8-7c55c32d7f1f> (5e59154a-c15b-4d11-a3a8-7c55c32d7f1f) [No such file or directory] [2017-10-25 10:36:36.083770] E [MSGID: 114058] [client-handshake.c:1538:client_query_portmap_cbk] 0-home-client-3: failed to get the port number for remote subvolume. Please run 'gluster volume status' on server to see if brick process is running. [2017-10-25 10:36:36.083820] I [MSGID: 114018] [client.c:2276:client_rpc_notify] 0-home-client-3: disconnected from home-client-3. Client pr...