Glad that for both of you, things are back to normal. Could one of you help us find what is the problem you are facing with libgfapi, if you have any spare test machines. Otherwise we need to understand proxmox etc which may take a bit more time. On Wed, Jun 29, 2016 at 11:49 PM, Kevin Lemonnier <lemonnierk at ulrar.net> wrote:> > > > To me it looks like a libgfapi problem. VM's were working via fuse. > > > > Yeah, as mentionned in other messages I can confirm libgfapi isn't working > in 3.7.12. > I don't know if there was some breaking change between 3.7.11 and 3.7.12 > but looks like > it's not working anymore, at least not in the latest proxmox. > > -- > Kevin Lemonnier > PGP Fingerprint : 89A5 2283 04A0 E6E9 0111 > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users >-- Pranith -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160630/1a2630e4/attachment.html>
On 30 June 2016 at 14:42, Pranith Kumar Karampuri <pkarampu at redhat.com> wrote:> Could one of you help us find what is the problem you are facing with > libgfapi, if you have any spare test machines. Otherwise we need to > understand proxmox etc which may take a bit more time.I'm looking at getting a basic PC reurposed for testing today - to be exact a Celeron NU with 8GB ram. We'll see if its usable :) -- Lindsay
> Glad that for both of you, things are back to normal. Could one of you > help us find what is the problem you are facing with libgfapi, if you have > any spare test machines. Otherwise we need to understand proxmox etc which > may take a bit more time.Sure, I have my test cluster working now using NFS but I can create other VMs using the lib to test if needed. What would you need ? Unfortunatly creating a VM on gluster through the lib doesn't work and I don't know how to get the logs of that, the only error I get is this in proxmox logs : Jun 29 13:26:25 s2.name pvedaemon[2803]: create failed - unable to create image: got lock timeout - aborting command Jun 29 13:26:52 s2.name qemu-img[2811]: [2016-06-29 11:26:52.485296] C [rpc-clnt-ping.c:165:rpc_clnt_ping_timer_expired] 0-gluster-client-3: server 172.16.0.2:49153 has not responded in the last 42 seconds, disconnecting. Jun 29 13:26:52 s2.name qemu-img[2811]: [2016-06-29 11:26:52.485407] C [rpc-clnt-ping.c:165:rpc_clnt_ping_timer_expired] 0-gluster-client-4: server 172.16.0.3:49153 has not responded in the last 42 seconds, disconnecting. Jun 29 13:26:52 s2.name qemu-img[2811]: [2016-06-29 11:26:52.485443] C [rpc-clnt-ping.c:165:rpc_clnt_ping_timer_expired] 0-gluster-client-5: server 172.16.0.50:49153 has not responded in the last 42 seconds, disconnecting. -- Kevin Lemonnier PGP Fingerprint : 89A5 2283 04A0 E6E9 0111 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160630/1ee859df/attachment.sig>
On 30/06/2016 2:42 PM, Pranith Kumar Karampuri wrote:> Glad that for both of you, things are back to normal. Could one of you > help us find what is the problem you are facing with libgfapi, if you > have any spare test machines. Otherwise we need to understand proxmox > etc which may take a bit more time.I got a test node running, with a replica 3 volumes (3 bricks on same node). Replicated the problem with 3.7.12 *and* 3.8.0 :( I can trash this node as needed, happy to build from src and apply patches. -- Lindsay Mathieson