Red Hat Bugzilla – Bug 868877
[22.214.171.124rhs-34.el6rhs.x86_64.rpm] geo-rep status gives N/A.
Last modified: 2014-08-24 20:49:52 EDT
Description of problem: After upgrading to version 126.96.36.199rhs-34.el6rhs.x86_64.rpm , the geo-rep status says N/A. This is because checkpoint service went down. I have tested again with 188.8.131.52rhs-33.el6rhs.x86_64.rpm. It worked fine. After the upgrade only it is happening consistently.
Version-Release number of selected component (if applicable):184.108.40.206rhs-34.el6rhs.x86_64.rpm
Steps to Reproduce:
1.Start a geo-rep session between master(dist-rep) and slave(dist-rep)
2.check geo-rep status
Actual results: status shows N/A
Expected results: It should show proper status.
N/A means that checkpoint service is not functional.
That happened because the change of the location of
unix domain sockets that are used for inter-component
communication has changed as of
on the glusterd side, but gsyncd has not been
adjusted so the checkpoint service is not found
where glusterd expects it to be.
The proper fix is to have glusterd to specify
the socket location to gsyncd, instead of hardwiring
it into gsyncd code.
*** Bug 870503 has been marked as a duplicate of this bug. ***
*** Bug 870502 has been marked as a duplicate of this bug. ***
CHANGE: http://review.gluster.org/4143 (geo-rep / gsyncd,glusterd: do not hardcode socket path) merged in master by Anand Avati (firstname.lastname@example.org)
Kindly verify the edited doc text for technical accuracy and sign off.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.