OK, I believe I solved it by doing this by 1. setting the volume property allow-insecure with the following command:
gluster volume set gv0 server.allow-insecure on
and 2. editing the /usr/local/etc/glusterfs/glusterd.vol file and adding the following line between 'volume-management' and 'end-volume':
option rpc-auth-allow-insecure on
option rpc-auth-allow-insecure on
Is there some mechanism for setting glusterd.vol options without manually editing a file on each host in the cluster?
If I add a new host to the cluster at a later point, will it slurp the glusterd.vol file from one of the already established hosts? Or do I have to manage keeping this file identical on every host?
-K
On Wed, Dec 18, 2013 at 1:43 PM, Kelly Burkhart <kelly.burkhart@xxxxxxxxx> wrote:
How does one run a gfapi app without being root?I've set server.allow-insecure on on the server side (and bounced all gluster processes). Is there something else required?
My test program just stats a file on the cluster volume. It works as root and fails as a normal user. Local log file shows a message about failing to bind a privileged port.
-K
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
