<div dir="ltr"><div>OK, I believe I solved it by doing this by 1. setting the volume property allow-insecure with the following command:<br></div> <br><div><div>gluster volume set gv0 server.allow-insecure on<br><br></div>
<div>and 2. editing the /usr/local/etc/glusterfs/glusterd.vol file and adding the following line between 'volume-management' and 'end-volume':<br><br> option rpc-auth-allow-insecure on<br><br></div><div>
<br></div><div>Is there some mechanism for setting glusterd.vol options without manually editing a file on each host in the cluster?<br></div><div>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?<br>
</div><div><br></div><div>-K<br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 18, 2013 at 1:43 PM, Kelly Burkhart <span dir="ltr"><<a href="mailto:kelly.burkhart@gmail.com" target="_blank">kelly.burkhart@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>How does one run a gfapi app without being root?<br><br></div>I've set server.allow-insecure on on the server side (and bounced all gluster processes). Is there something else required?<br>
<br>
</div><div>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.<span class="HOEnZb"><font color="#888888"><br>
</font></span></div><span class="HOEnZb"><font color="#888888"><div><br></div>-K<br></font></span></div>
</blockquote></div><br></div>