Hey Bernhard,
I'm running a very similar setup to you. What are your gluster options? What's the migration command you're using? Are you using gfapi or a fuse mount? I think I've hit this error before but I'll need some info to jog brain on how I fixed it.
Best,
Josh
From: "Bernhard Glomm" <bernhard.glomm@xxxxxxxxxxx>
To: gluster-users@xxxxxxxxxxx
Sent: Saturday, November 30, 2013 8:13:26 AM
Subject: glusterfs 3.4
Hi all, I just stumbled over a possible bug in glusterfs-3.4.1 Since I used the package from ppa:semiosis/ubuntu-glusterfs-3.4 for ubuntu (running 13.04 up to date) I like to report here first / ask for confirmation. I had glusterfs 3.3 installed and it worked fine. I used it as the storage backend for the image files of my kvm virtualized instances (two sided mirror/two kvm hosts running four VM as a test environment) I upgraded to 3.4 and all seemed okay on the first glance, but live-migration failed with error: "-incoming tcp:0.0.0.0:49153: Failed to bind socket: Address already in use" reverting back to glusterfs 3.3 and the problem was gone anybody knows about that prob? couldn't find anything on the net about it yet. best regards Bernhard -- sysadmin www.ecologic.eu
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
To: gluster-users@xxxxxxxxxxx
Sent: Saturday, November 30, 2013 8:13:26 AM
Subject: glusterfs 3.4
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
