Bug 764699 (GLUSTER-2967) - Geo-replication fails to start (EOFError)
Summary: Geo-replication fails to start (EOFError)
Keywords:
Status: CLOSED DUPLICATE of bug 764651
Alias: GLUSTER-2967
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.2.0
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ---
Assignee: Csaba Henk
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-31 21:18 UTC by Evan
Modified: 2011-12-20 17:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.