Re: [Gluster-users] Odd "Transport endpoint is not connected" when trying to gunzip a file

2022-06-15 Thread Yaniv Kaul 
On Wed, Jun 15, 2022 at 6:28 PM Pat Haley  wrote:

>
> Hi,
>
> We have a cluster whose common storage is a gluster volume consisting of 5
> bricks residing on 3 servers.
>
>- Gluster volume machines
>   - mseas-data2:  CentOS release 6.8 (Final)
>   - mseas-data3:  CentOS release 6.10 (Final)
>   - mseas-data4:  CentOS Linux release 7.9.2009 (Core)
>- Client machines
>   - CentOS Linux release 7.9.2009 (Core)
>
> More details on the gluster volume are included below.
>
> We were recently trying to gunzip a file on the gluster volume and got  a
> "Transport endpoint is not connected" even though every test we try shows
> that gluster is fully up and running fine.  We traced the file to brick 3
> in the server mseas-data3.  We have included the relevant portions of the
> various log files on the client (mseas) where we were running the gunzip
> command and the server hosting the file (mseas-data3) below the gluster
> information
>
> What can you suggest we do to further debug and/or solve this issue?
>
> Thanks
> Pat
>
> 
> Gluster volume information
> 
>
> ---
> gluster volume info
> -
>
> Volume Name: data-volume
> Type: Distribute
> Volume ID: c162161e-2a2d-4dac-b015-f31fd89ceb18
> Status: Started
> Number of Bricks: 5
> Transport-type: tcp
> Bricks:
> Brick1: mseas-data2:/mnt/brick1
> Brick2: mseas-data2:/mnt/brick2
> Brick3: mseas-data3:/export/sda/brick3
> Brick4: mseas-data3:/export/sdc/brick4
> Brick5: mseas-data4:/export/brick5
> Options Reconfigured:
> diagnostics.client-log-level: ERROR
> network.inode-lru-limit: 5
> performance.md-cache-timeout: 60
> performance.open-behind: off
> disperse.eager-lock: off
> auth.allow: *
> server.allow-insecure: on
> nfs.exports-auth-enable: on
> diagnostics.brick-sys-log-level: WARNING
> performance.readdir-ahead: on
> nfs.disable: on
> nfs.export-volumes: off
> cluster.min-free-disk: 1%
>
> ---
> gluster volume status
> 
>
> Status of volume: data-volume
> Gluster process TCP Port  RDMA Port  Online
> Pid
>
> --
> Brick mseas-data2:/mnt/brick1   49154 0  Y
> 15978
> Brick mseas-data2:/mnt/brick2   49155 0  Y
> 15997
> Brick mseas-data3:/export/sda/brick349153 0  Y
> 14221
> Brick mseas-data3:/export/sdc/brick449154 0  Y
> 14240
> Brick mseas-data4:/export/brick549152 0  Y
> 50569
>
>
> ---
> gluster peer status
> -
>
> Number of Peers: 2
>
> Hostname: mseas-data3
> Uuid: b39d4deb-c291-437e-8013-09050c1fa9e3
> State: Peer in Cluster (Connected)
>
> Hostname: mseas-data4
> Uuid: 5c4d06eb-df89-4e5c-92e4-441fb401a9ef
> State: Peer in Cluster (Connected)
>
> ---
> glusterfs --version
> 
>
> glusterfs 3.7.11 built on Apr 18 2016 13:20:46
>

This is somewhat of an outdated version, I think it's best to upgrade (or
better - migrate?) to a newer version.
Y.

> Repository revision: git://git.gluster.com/glusterfs.git
> Copyright (c) 2006-2013 Red Hat, Inc. 
> 
> 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.
>
> 
> Relevant sections from log files
> 
>
> ---
> mseas: gdata.log
> -
>
> [2022-06-15 14:51:17.263858] C
> [rpc-clnt-ping.c:165:rpc_clnt_ping_timer_expired] 0-data-volume-client-2:
> server 172.16.1.113:49153 has not responded in the last 42 seconds,
> disconnecting.
> [2022-06-15 14:51:17.264522] E [rpc-clnt.c:362:saved_frames_unwind] (-->
> /usr/local/lib/libglusterfs.so.0(_gf_log_callingfn+0x172)[0x7f84886a0202]
> (-->
> /usr/local/lib/libgfrpc.so.0(saved_frames_unwind+0x1c2)[0x7f848846c3e2]
> (--> /usr/local/lib/libgfrpc.so.0(saved_frames_destroy+0xe)[0x7f848846c4de]
> (-->
> /usr/local/lib/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x7a)[0x7f848846dd2a]
> (--> /usr/local/lib/libgfrpc.so.0(rpc_clnt_notify+0x88)[0x7f848846e538]
> ) 0-data-volume-client-2: forced unwinding frame type(GlusterFS 3.3)
> op(READ(12)) called at 2022-06-15 14:49:52.113795

[Gluster-users] Odd "Transport endpoint is not connected" when trying to gunzip a file

2022-06-15 Thread Pat Haley 


Hi,

We have a cluster whose common storage is a gluster volume consisting of 
5 bricks residing on 3 servers.


 * Gluster volume machines
 o mseas-data2:  CentOS release 6.8 (Final)
 o mseas-data3:  CentOS release 6.10 (Final)
 o mseas-data4:  CentOS Linux release 7.9.2009 (Core)
 * Client machines
 o CentOS Linux release 7.9.2009 (Core)

More details on the gluster volume are included below.

We were recently trying to gunzip a file on the gluster volume and got  
a "Transport endpoint is not connected" even though every test we try 
shows that gluster is fully up and running fine.  We traced the file to 
brick 3 in the server mseas-data3.  We have included the relevant 
portions of the various log files on the client (mseas) where we were 
running the gunzip command and the server hosting the file (mseas-data3) 
below the gluster information


What can you suggest we do to further debug and/or solve this issue?

Thanks
Pat


Gluster volume information


---
gluster volume info
-

Volume Name: data-volume
Type: Distribute
Volume ID: c162161e-2a2d-4dac-b015-f31fd89ceb18
Status: Started
Number of Bricks: 5
Transport-type: tcp
Bricks:
Brick1: mseas-data2:/mnt/brick1
Brick2: mseas-data2:/mnt/brick2
Brick3: mseas-data3:/export/sda/brick3
Brick4: mseas-data3:/export/sdc/brick4
Brick5: mseas-data4:/export/brick5
Options Reconfigured:
diagnostics.client-log-level: ERROR
network.inode-lru-limit: 5
performance.md-cache-timeout: 60
performance.open-behind: off
disperse.eager-lock: off
auth.allow: *
server.allow-insecure: on
nfs.exports-auth-enable: on
diagnostics.brick-sys-log-level: WARNING
performance.readdir-ahead: on
nfs.disable: on
nfs.export-volumes: off
cluster.min-free-disk: 1%

---
gluster volume status


Status of volume: data-volume
Gluster process TCP Port  RDMA Port Online  Pid
--
Brick mseas-data2:/mnt/brick1   49154 0 Y   15978
Brick mseas-data2:/mnt/brick2   49155 0 Y   15997
Brick mseas-data3:/export/sda/brick3    49153 0 Y   14221
Brick mseas-data3:/export/sdc/brick4    49154 0 Y   14240
Brick mseas-data4:/export/brick5    49152 0 Y   50569


---
gluster peer status
-

Number of Peers: 2

Hostname: mseas-data3
Uuid: b39d4deb-c291-437e-8013-09050c1fa9e3
State: Peer in Cluster (Connected)

Hostname: mseas-data4
Uuid: 5c4d06eb-df89-4e5c-92e4-441fb401a9ef
State: Peer in Cluster (Connected)

---
glusterfs --version


glusterfs 3.7.11 built on Apr 18 2016 13:20:46
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2013 Red Hat, Inc. 
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.


Relevant sections from log files


---
mseas: gdata.log
-

[2022-06-15 14:51:17.263858] C 
[rpc-clnt-ping.c:165:rpc_clnt_ping_timer_expired] 
0-data-volume-client-2: server 172.16.1.113:49153 has not responded in 
the last 42 seconds, disconnecting.
[2022-06-15 14:51:17.264522] E [rpc-clnt.c:362:saved_frames_unwind] (--> 
/usr/local/lib/libglusterfs.so.0(_gf_log_callingfn+0x172)[0x7f84886a0202] 
(--> 
/usr/local/lib/libgfrpc.so.0(saved_frames_unwind+0x1c2)[0x7f848846c3e2] 
(--> 
/usr/local/lib/libgfrpc.so.0(saved_frames_destroy+0xe)[0x7f848846c4de] 
(--> 
/usr/local/lib/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x7a)[0x7f848846dd2a] 
(--> /usr/local/lib/libgfrpc.so.0(rpc_clnt_notify+0x88)[0x7f848846e538] 
) 0-data-volume-client-2: forced unwinding frame type(GlusterFS 3.3) 
op(READ(12)) called at 2022-06-15 14:49:52.113795 (xid=0xb4f49b)
[2022-06-15 14:51:17.264859] E [rpc-clnt.c:362:saved_frames_unwind] (--> 
/usr/local/lib/libglusterfs.so.0(_gf_log_callingfn+0x172)[0x7f84886a0202] 
(--> 
/usr/local/lib/libgfrpc.so.0(saved_frames_unwind+0x1c2)[0x7f848846c3e2] 
(--> 
/usr/local/lib/libgfrpc.so.0(saved_frames_destroy+0xe)[0x7f848846c4de] 
(--> 
/usr/local/lib/libgfrpc.so.0(rpc_clnt_connection_cleanup+0x7a)[0x7f848846dd2a] 
(-->