[Bugs] [Bug 1160900] cli segmentation fault with remote ssl (3.6.0)

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1160900

Jeff Darcy <jdarcy at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jdarcy at redhat.com



--- Comment #3 from Jeff Darcy <jdarcy at redhat.com> ---
As far as I can tell, this problem has to do with sending requests on
connections that failed - either CLI to glusterd, or glusterd to glusterd in
the case of a "peer probe" operation.  That's a bug somewhere above the
transport layer - probably a new one, which would explain why this wasn't seen
before.  Still, it shouldn't cause a segfault.  I've written a patch to address
that part, so it doesn't segfault, but there are other "infelicities" involved
that I'm still looking into.

Also, it's not advisable to change the transport.socket.ssl option directly in
the glusterd volfile.  It shouldn't be harmful, because that should only affect
the I/O path and thus be irrelevant for glusterd, but it's also possible that
it could interfere with the way we make decisions about when to use SSL and
when not to (because in the portmapper case we need to switch based on two
different settings).  The correct way to enable SSL for the management layer is
via the secure-access file.  See this doc (unfortunately still in review) for
more details.

http://review.gluster.org/#/c/8961/2/doc/admin-guide/en-US/markdown/admin_ssl.md

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.