[Gluster-users] qemu remote insecure connections

[Joe Topjian]

Hello,

I apologize for the delayed reply.

I've collected some logs and posted them here:
https://gist.github.com/jtopjian/7981763

I stopped the Gluster service on 192.168.1.11, moved /var/log/glusterfs to
a backup, then started Gluster so that the log files were more succinct.

I then used the qemu-img command as mentioned before as root, which was
successful. Then I ran the command as libvirt-qemu and let the command hang
for 2 minutes before I killed it.

It might also be helpful to note that this is on an Ubuntu 12.04 server
using the packages found here:
https://launchpad.net/~semiosis/+archive/ubuntu-glusterfs-3.4

Thanks,
Joe


On Sat, Dec 14, 2013 at 12:41 AM, Vijay Bellur <vbellur at redhat.com> wrote:

> On 12/13/2013 10:58 AM, Joe Topjian wrote:
>
>> Hello,
>>
>> I'm having a problem getting remote servers to connect to Gluster with
>> qemu.
>>
>> I have 5 servers, 4 of which run Gluster and host a volume. The qemu
>> user on all 5 servers has the same uid.
>>
>> storage.owner-uid and storage.owner-gid is set to that user.
>>
>> In addition, server.allow-insecure is on and is also set in the
>> glusterd.vol file. glusterd has also been restarted (numerous times).
>>
>> When attempting to create a qemu file by connecting to the same server,
>> everything works:
>>
>> qemu at 192.168.1.11 <mailto:qemu at 192.168.1.11>> qemu-img create
>> gluster://192.168.1.11/volumes/v.img <http://192.168.1.11/volumes/v.img>
>> 1M
>> Formatting 'gluster://192.168.1.11/volumes/v.img
>> <http://192.168.1.11/volumes/v.img>', fmt=raw size=1048576
>> qemu at 192.168.1.11 <mailto:qemu at 192.168.1.11>>
>>
>>
>> But when trying to do it remotely, the command hangs indefinitely:
>>
>> qemu at 192.168.1.12 <mailto:qemu at 192.168.1.12>> qemu-img create
>> gluster://192.168.1.11/volumes/v.img <http://192.168.1.11/volumes/v.img>
>> 1M
>> Formatting 'gluster://192.168.1.11/volumes/v.img
>> <http://192.168.1.11/volumes/v.img>', fmt=raw size=1048576
>>
>> ^C
>>
>> Yet when 192.168.1.12 connects to gluster://192.168.1.12
>> <http://192.168.1.12>, the command works and the file shows up in the
>>
>> distributed volume.
>>
>> Further, when turning server.allow-insecure off, I get an immediate
>> error no matter what the source and destination connection is:
>>
>> qemu at 192.168.1.12 <mailto:qemu at 192.168.1.12>> qemu-img create
>> gluster://192.168.1.11/volumes/v.img <http://192.168.1.11/volumes/v.img>
>> 1M
>> Formatting 'gluster://192.168.1.11/volumes/v.img
>> <http://192.168.1.11/volumes/v.img>', fmt=raw size=1048576
>>
>> qemu-img: Gluster connection failed for server=192.168.1.11 port=0
>> volume=volumes image=v.img transport=tcp
>> qemu-img: gluster://192.168.1.11/volumes/v.img
>> <http://192.168.1.11/volumes/v.img>: error while creating raw: No data
>>
>> available
>>
>> Does anyone have any ideas how I can have an unprivileged user connect
>> to remote gluster servers?
>>
>>
> Can you please provide glusterd and glusterfsd logs from 192.168.1.11?
>
> -Vijay
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20131215/53879d07/attachment.html>