Bug 1131010

Summary: Invalid SSL connection on brick port make the brick disconnect
Product: [Community] GlusterFS Reporter: jdeliege
Component: glusterdAssignee: Satish Mohan <smohan>
Status: CLOSED EOL QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 3.5.2CC: bugs, mselvaga
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-17 15:56:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description jdeliege 2014-08-18 11:43:22 UTC
Description of problem:
On a SSL configured volume with :
Volume Name: data
Type: Replicate
Volume ID: 32524156-4fcb-4a3c-9103-blablabla
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: test-a.tunz.com:/export/glusterfs
Brick2: test-b.tunz.com:/export/glusterfs
Brick3: test-c.tunz.com:/export/glusterfs
Options Reconfigured:
server.ssl: on
client.ssl: on
auth.allow: 192.168.174.101,192.168.174.102,192.168.174.103

Status of volume: data
Gluster process						Port	Online	Pid
------------------------------------------------------------------------------
Brick test-a.tunz.com:/export/glusterfs		49152	Y	2188
Brick test-b.tunz.com:/export/glusterfs		49152	Y	1727
Brick test-c.tunz.com:/export/glusterfs		49152	Y	1487

A SSL connection to the brick for any host (not in the auth list, sending garbish data) on the brick port (49152) disconnect the brick and enter a loop

[2014-08-18 11:15:19.537467] W [socket.c:522:__socket_rwv] 0-data-client-0: readv on 192.168.174.54:49152 failed (No data available)
[2014-08-18 11:15:19.537513] E [socket.c:2372:socket_poller] 0-data-client-0: error in polling loop
[2014-08-18 11:15:19.537589] I [client.c:2229:client_rpc_notify] 0-data-client-0: disconnected from 192.168.174.54:49152. Client process will keep trying to connect to glusterd until brick's port is available
[2014-08-18 11:15:29.956167] I [rpc-clnt.c:1729:rpc_clnt_reconfig] 0-data-client-0: changing port to 49152 (from 0)
[2014-08-18 11:15:29.957152] E [socket.c:2820:socket_connect] 0-data-client-0: connection attempt on 192.168.174.54:24007 failed, (Connection refused)
[2014-08-18 11:15:33.957237] I [rpc-clnt.c:1729:rpc_clnt_reconfig] 0-data-client-0: changing port to 49152 (from 0)

Status of volume: data
Gluster process						Port	Online	Pid
------------------------------------------------------------------------------
Brick webdav-a.tunz.com:/export/glusterfs		N/A	N	1648
Brick webdav-b.tunz.com:/export/glusterfs		49152	Y	1727
Brick webdav-c.tunz.com:/export/glusterfs		49152	Y	1487


Version-Release number of selected component (if applicable):

glusterfs.x86_64      3.5.2-1.el6       @glusterfs-el6-x86_64                   
glusterfs-api.x86_64  3.5.2-1.el6       @glusterfs-el6-x86_64                   
glusterfs-cli.x86_64  3.5.2-1.el6       @glusterfs-el6-x86_64                   
glusterfs-fuse.x86_64 3.5.2-1.el6       @glusterfs-el6-x86_64                   
glusterfs-libs.x86_64 3.5.2-1.el6       @glusterfs-el6-x86_64                   
glusterfs-rdma.x86_64 3.5.2-1.el6       @glusterfs-el6-x86_64                   
glusterfs-server.x86_64
                      3.5.2-1.el6       @glusterfs-el6-x86_64

Comment 2 Niels de Vos 2016-06-17 15:56:26 UTC
This bug is getting closed because the 3.5 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.