On Tue, Mar 20, 2012 at 14:34, Greg Swift <gregswift at gmail.com> wrote: > Hi all. ?I'm looking to see if anyone can tell me this is already > working for them or if they wouldn't mind performing a quick test. > > I'm trying to set up a geo-replication instance on 3.2.5 from a local > volume to a remote directory. ?This is the command I am using: > > gluster volume geo-replication myvol ssh://root at remoteip:/data/path start > > I am able to perform a geo-replication from a local volume to a remote > volume with no problem using the following command: > > gluster volume geo-replication myvol ssh://root at remoteip::remotevol start > > The steps I am using to implement this: > > 1: Create key for geo-replication in > /etc/glusterd/geo-replication/secret.pem.pub and secret.pem.pub > 2: Add pub key to ~root/.ssh/authorized_keys on target systems > 3: Verify key works (using geo-replication's ssh syntax): > [root at myboxen ~]# ssh -oPasswordAuthentication=no > -oStrictHostKeyChecking=no -i /etc/glusterd/geo-replication/secret.pem > root at remoteip "ls -l /data" > drwxr-xr-x 2 root root 4096 Mar 15 11:53 path > > 4: Run the geo-replication command > gluster volume geo-replication myvol ssh://root at remoteip:/data/path start > > > I'd expect to get : > > [root at myboxen ~]# gluster volume geo-replication myvol > ssh://root at remoteip:/data/path start > Starting geo-replication session between ecfcerts & > ssh://root at remoteip:/data/path has been successful > > [root at myboxen ~]# gluster volume geo-replication status > MASTER ? ? ? ? ? ? ? SLAVE ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?STATUS > -------------------------------------------------------------------------------- > myvol ? ? ? ? ? ? ssh://root at remoteip:file:///data/path OK > > Instead I get: > > [root at myboxen ~]# gluster volume geo-replication myvol > ssh://root at remoteip:/data/path start > geo-replication start failed for myvol ssh://root at remoteip:/data/path > geo-replication command failed > > [root at myboxen ~]# gluster volume geo-replication status > MASTER ? ? ? ? ? ? ? SLAVE ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?STATUS > -------------------------------------------------------------------------------- > myvol ? ? ? ? ? ? ssh://root at remoteip:file:///data/path ? ?corrupt > > > I was not getting any logs about this either. > > I then set log-level to DEBUG: > gluster volume geo-replication myvol ssh://root at remoteip:/data/path > config log-level debug > > My responses started being a bit different, but still a fail: > > [root at myboxen ecfcerts]# gluster volume geo-replication myvol > ssh://root at remoteip:/data/path start > Starting geo-replication session between myvol & > ssh://root at remoteip:/data/path has been successful > [root at myboxen ecfcerts]# gluster volume geo-replication status > MASTER ? ? ? ? ? ? ? SLAVE ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?STATUS > -------------------------------------------------------------------------------- > myvol ? ? ? ? ? ? ssh://root at remoteip:file:///data/path ? ?faulty > > At which I do start getting logs. ?I've attached it. So no one is doing geo-replication to a remote directory?
