Hi, I’m ready for new testing, I delete the geo-rep session between master and slace, remove the lines in authorized keys file on slave. I also remove the common secret pem from slave, and from master. There is only the gsyncd_template.conf in /var/lib/gluster now. Here is our setup: Site A: gluster 3 nodes Site B: gluster 1 node (for now, a second will come). I can issue gluster systen:: execute gsec_create what to check? then gluster geo vol geo_test slave::geo_test create push-pem force (force is needed because the slave vol is smaller than the master vol). What to check ? I want to use change_detector changelog and not rsync btw. Can you guide me to setup this but also debug why it’s not working out of the box ? If needed I can get in touch with you through IRC. Thanks for your help. -- Cyril Peponnet > On Jan 15, 2015, at 9:40 AM, Aravinda <avishwan@xxxxxxxxxx> wrote: > > Run the hook script directly in master node to discover the root cause for the error. > > /var/lib/glusterd/hooks/1/gsync-create/post/S56glusterd-geo-rep-create-post.sh —volname=geo_test is_push_pem=1 pub_file=/var/lib/glusterd/geo-replication/common_secret.pem.pub slave_ip=gluster-slave01 > > Also let us know the GlusterFS version in Master nodes and Slave nodes. > > -- > regards > Aravinda > > On 01/15/2015 09:12 PM, PEPONNET, Cyril N (Cyril) wrote: >> [2015-01-15 15:38:13.676252] E [run.c:190:runner_log] 0-management: Failed to execute script: /var/lib/glusterd/hooks/1/gsync-create/post/S56glusterd-geo-rep-create-post.sh —volname=geo_test is_push_pem=1 pub_file=/var/lib/glusterd/geo-replication/common_secret.pem.pub slave_ip=gluster-slave01 >> >> >> On my slave: >> >> gluster system:: execute add_secret_pub >> One or more nodes do not support the required op version. >> >> I never really understood what is the op_version but looks a good lead. >> > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users