I’ve also seen this behavior. I fixed it in the same method.
The strange part is that using Vagrant for testing, I didn’t see the same behavior. It only happens on bare metal boxes in my case. I’m not sure why that is though… I’m using the same version CentOS, etc.
-CJ
From: Steve Dainard <sdainard@xxxxxxxxxxxxx>
Date: Tuesday, April 29, 2014 at 10:42 AM To: "gluster-users@xxxxxxxxxxx List" <gluster-users@xxxxxxxxxxx> Subject: Re: geo-replication status faulty Fixed by editing the geo-rep volumes gsyncd.conf file, changing /nonexistent/gsyncd to /usr/libexec/glusterfs/gsyncd on both the master nodes.
Any reason why this is in the default template? Also any reason why when I stop glusterd, change the template on both master nodes and start the gluster service its overwritten?
Steve
On Tue, Apr 29, 2014 at 12:11 PM, Steve Dainard
<sdainard@xxxxxxxxxxxxx> wrote:
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users