Bug 1105283 - Failure to start geo-replication.
Summary: Failure to start geo-replication.
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.5.0
Hardware: x86_64
OS: Linux
medium
urgent
Target Milestone: ---
Assignee: Aravinda VK
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-05 18:50 UTC by vnosov
Modified: 2016-06-17 16:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-17 16:23:41 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description vnosov 2014-06-05 18:50:55 UTC
Description of problem:

Command "gluster volume geo-replication <master_volume> <slave_host>::<slave_volume> start" returns success,
but status of the geo-replication is "Not Started" permanently.




Version-Release number of selected component (if applicable):


How reproducible:

Each time.


Steps to Reproduce:
1. Create geo-replication session.
2. Call to start the geo-replication.
3. Call to check status for the geo-replication.

Actual results:  Status "Not Started".


Expected results:


Additional info:

GlusterFS log file has next error messages created for each geo-replication status call:

[2014-06-05 17:46:38.574485] E [glusterd-geo-rep.c:2685:glusterd_gsync_read_frm_status] 0-: Unable to read gsyncd status file
[2014-06-05 17:46:38.574554] E [glusterd-geo-rep.c:2999:glusterd_read_status_file] 0-: Unable to read the statusfile for /exports/nas-segment-0001/nas-volume-loc1 brick for  nas-volume-loc1(master), 10.10.200.142::nas-volume-rem1(slave) session

Comment 1 vnosov 2014-06-07 01:01:06 UTC
Version 3.5.1beta has the same problem.
The GlusterFS installation was done on Centos by using glusterfs-3.5.1.tar or glusterfs-3.5.1beta.tar.

 GlusterFS configure summary
 ===========================
 FUSE client          : yes
 Infiniband verbs     : no
 epoll IO multiplex   : yes
 argp-standalone      : no
 fusermount           : yes
 readline             : yes
 georeplication       : yes
 Linux-AIO            : yes
 Enable Debug         : no
 systemtap            : no
 Block Device xlator  : no
 glupy                : no
 Use syslog           : yes
 XML output           : yes
 QEMU Block formats   : yes
 Encryption xlator    : yes

It seems that the installation has problem to run geo-replication because
scripts do not have valid path for gluster, glusterfs and gsyncd.

For example: attempt to execute /nonexistent/gsyncd fails.

After setting symbolic links geo-replication started successfully.
Installation from the tar file has to do it itself and set valid path for gluster, glusterfs and qsyncd.

Comment 2 Aravinda VK 2014-12-29 05:20:32 UTC
looks like pem key distribution failed.

Comment 3 vnosov 2015-04-20 23:02:21 UTC
Was not able duplicate this bug with version 3.6.2.

Comment 4 Niels de Vos 2016-06-17 16:23:41 UTC
This bug is getting closed because the 3.5 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.


Note You need to log in before you can comment on or make changes to this bug.