Version: 3.3.0qa34 clear-locks commands fail if rpc-auth-allow is not set as it attempts to connect via privileged port. The CLI reports the error as: Volume clear-locks unsuccessful clear-locks getxattr command failed. Reason: Transport endpoint is not connected ### glusterd.vol.log has [2012-05-27 12:54:33.217491] E [rpcsvc.c:491:rpcsvc_handle_rpc_call] 0-glusterd: Request received from non-privileged port. Failing request
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.