Bug 764699 (GLUSTER-2967)

Summary: Geo-replication fails to start (EOFError)
Product: [Community] GlusterFS Reporter: Evan <evan>
Component: geo-replicationAssignee: Csaba Henk <csaba>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: 3.2.0CC: gluster-bugs, rahulcs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTNR Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Csaba Henk 2011-05-31 19:54:40 UTC

*** This bug has been marked as a duplicate of bug 2919 ***

Comment 1 Evan 2011-05-31 21:18:20 UTC
When trying to start geo-replication, it always fails with the following error in the log:


  File "/usr/lib/glusterfs/glusterfs/python/syncdaemon/repce.py", line 42, in recv
    return pickle.load(inf)
EOFError

After looking at the default geo-replication config, it is trying to use the following option for "remote_gsyncd"

remote_gsyncd: /usr/local/libexec/glusterfs/gsyncd

However, the location of gsyncd is in /usr/lib/glusterfs/glusterfs/gsyncd (on Ubuntu)

Both (master and slave) are Ubuntu 10.04 (64bit) using the glusterfs_3.2.0-1_amd64.deb package.

Upon re-configuring geo-replication to use the new path, replication is working.