Bug 825562
Summary: | [glusterfs-3.3.0q43]: clear-locks attempts to connect using privileged port | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Joe Julian <joe> | ||||||||||
Component: | cli | Assignee: | krishnan parthasarathi <kparthas> | ||||||||||
Status: | CLOSED WORKSFORME | QA Contact: | |||||||||||
Severity: | high | Docs Contact: | |||||||||||
Priority: | medium | ||||||||||||
Version: | pre-release | CC: | amarts, gluster-bugs, nsathyan | ||||||||||
Target Milestone: | --- | Keywords: | Triaged | ||||||||||
Target Release: | --- | ||||||||||||
Hardware: | Unspecified | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | |||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | |||||||||||||
: | 849291 (view as bug list) | Environment: | |||||||||||
Last Closed: | 2012-12-27 06:11:22 UTC | Type: | Bug | ||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||
Documentation: | DP | CRM: | |||||||||||
Verified Versions: | Category: | --- | |||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
Embargoed: | |||||||||||||
Bug Depends On: | |||||||||||||
Bug Blocks: | 849291 | ||||||||||||
Attachments: |
|
Description
Joe Julian
2012-05-27 19:57:54 UTC
Did it again. Sorry, it's qa43 not 34. Created attachment 587189 [details]
mysql1-clearlocks-mnt.log
Created attachment 587198 [details]
ewcs2:var-spool-glusterfs-a_mysql1.log
Created attachment 587200 [details]
ewcs2: b,c,d
Created attachment 587203 [details]
ewcs4: var-spool-glusterfs-{a,b,c,d}_mysql1.log
Each of these logs are for just the minutes that were in the clearlocks log. Let me know if that's not what you needed.
one of the work around is to make sure everything works by adding "rpc-auth-allow-insecure yes" in volume files (both glusterd.vol and glusterfsd.vol, for which one can do 'gluster volume set <VOL> server.allow-insecure yes'). as the work around exists, would like to move the priority to medium. ---------- amar@supernova:~/work/glusterfs$ git diff diff --git a/doc/glusterd.vol b/doc/glusterd.vol index de17d8f..8268c3d 100644 --- a/doc/glusterd.vol +++ b/doc/glusterd.vol @@ -4,5 +4,12 @@ volume management option transport-type socket,rdma option transport.socket.keepalive-time 10 option transport.socket.keepalive-interval 2 + + # enable below option only if there are not many ports free below 1024 + # to bind() the client process. In this case, you would have to run : + # 'gluster volume set <VOL> server.allow-insecure yes' + # on all the volumes to the proper functioning. + # +# option rpc-auth-allow-insecure yes option transport.socket.read-fail-log off end-volume ---------- The above patch is the only way at the moment to fix these things. Also, Would like to close the bug with D(ocumentation)P(ending) flag set, once we have more better way of handling security (SSL/Kerberos etc), this issue will go away. as per comment #7 (WORKSFORME always when we have the above two options set). WONTFIX the part of not having these options set for now. |