On Tue, May 3, 2011 at 5:03 PM, Csaba Henk <csaba at gluster.com> wrote: > [repost for the ML after subscription, pls. reply to this one] > > Hi, > > On Tue, May 3, 2011 at 4:25 PM, Kaushik BV <kaushikbv at gluster.com> wrote: >> to locate the slave log-file do the following: >> ? ? execute this command on the slave domain: >> ? ? ? ? ? #gluster volume geo-replication ssh://root at slave.mydomain.com:file:///data/test ?config log-file > > Sorry, this command is bogus. The proper command would be: > > # gluster volume geo-replication file:///data/test config log-file > > or for short: > > # gluster volume geo-replication /data/test config log-file > > (because on the slave you are already at the other end of the ssh > tunnel, so you should strip the ssh part off of the slave url). > > Also, to ease debugging, you are suggested to set the log-level to > DEBUG on slave side too (that is independent of master side > log-level): > > # gluster volume geo-replication /data/test config log-level DEBUG Also, to add, for slave side config commands to work: - you need to run them prior to starting the geo-replication session with this slave; - you need a running glusterd at that point and further on (Just to start the geo-replication session with a file or file-over-ssh slave, you don't need a running glusterd on slave side, but then "config" subcommand won't be usable on slave side.) Csaba
