[Gluster-users] Gluster 3.5 problems with libgfapi/qemu

[Niels de Vos]

On Fri, Jun 13, 2014 at 09:56:46AM +0200, Ivano Talamo wrote:
> I had done it only on one of the two :(
> But even after I've done it on the other server and I've restarted
> the gluster daemon I see no change

Can you confirm that the issue is still occurring after you stopped and 
restarted the volume? A restart of the volume is needed to activate the 
server.allow-insecure volume option. When that option is not active, the 
glusterfs-client (libgfapi) will not be able to connect to the bricks.  
The bricks will detect that the client uses a port > 1024 an does not 
allow access.

With a stop and start of the volume, the .vol files that are used by the 
brick processes get regenerated. With this regeneration, the 
server.allow-insecure option gets activated correctly. You only have to 
execute these commands on one storage server:

  # gluster volume stop <volname>
  # gluster volume start <volname>

This is one of the most common issues when using libgfapi. If this 
indeed was not done in your environment, we may need to explain it 
better, or make it more obvious in the documentation.

Niels

> 
> Ivano
> 
> On 6/12/14 8:18 PM, Jae Park wrote:
> >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 at roma1.infn.it> 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
> >>
> >
> 
>