> 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
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
