Have you done the server part too? I mean adding "option rpc-auth-allow-insecure on" to /etc/glusterfs/glusterd.vol on EVERY server that participates in the volume. I saw only one scenario where it hangs after a vm start, and it was fixed with the additional option mentioned above. But you will have more problems with 3.5.0, including bug# 1103413, which is also fixed in 3.5.1beta2. Jae On 6/12/14 7:05 AM, "Ivano Talamo" <Ivano.Talamo@xxxxxxxxxxxxx> wrote: > >On 6/12/14 2:21 PM, Niels de Vos wrote: >> On Thu, Jun 12, 2014 at 10:59:23AM +0200, Ivano Talamo wrote: >>> Hi Jae, >> Have you taken care of setting the required glusterd and volume options? >> these are described here: >> - >>http://www.gluster.org/community/documentation/index.php/Libgfapi_with_qe >>mu_libvirt >> >> After setting the server.allow-insecure volume option, a stop and >> a start of the volume is needed (in 3.5). >> >Yes, this was done. > >Ivano > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
