Description of problem: Following is logged in Geo-rep logs when Geo-rep setup is not correct, [2016-05-18 02:18:53.765701] W [syncdutils(/bricks/b1):256:log_raise_exception] <top>: !!!!!!!!!!!!! [2016-05-18 02:18:53.765799] W [syncdutils(/bricks/b1):257:log_raise_exception] <top>: !!! getting "No such file or directory" errors is most likely due to MISCONFIGURATION, please consult https://access.redhat.com/site/documentation/en-US/Red_Hat_Storage/2.1/html/Administration_Guide/chap-User_Guide-Geo_Rep-Preparation-Settingup_Environment.html [2016-05-18 02:18:53.765701] W [syncdutils(/bricks/b1):256:log_raise_exception] <top>: !!!!!!!!!!!!! [2016-06-08 11:32:09.540306] E [resource(/bricks/b1):226:errlog] Popen: command "ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret.pem -p 22 -oControlMaster=auto -S /tmp/gsyncd-aux-ssh-bc3lL1/8b0e044a3aff9be1443052d3dab4f8e2.sock root@fvm1 /usr/local/libexec/gsyncd --session-owner be79b4c8-5d53-49e0-93c2-ba87ffd00a5c -N --listen --timeout 120 gluster://localhost:gv2" returned with 127, saying: [2016-06-08 11:32:09.540374] E [resource(/bricks/b1):230:logerr] Popen: ssh> bash: /usr/local/libexec/gsyncd: No such file or directory [2016-06-08 11:32:09.540601] I [syncdutils(/bricks/b1):220:finalize] <top>: exiting. [2016-06-08 11:32:09.541364] I [repce(agent):92:service_loop] RepceServer: terminating on reaching EOF. [2016-06-08 11:32:09.541495] I [syncdutils(agent):220:finalize] <top>: exiting. Version-Release number of selected component (if applicable): Document link is old and not appropriate.
REVIEW: http://review.gluster.org/14673 (geo-rep: Error message cleanup) posted (#1) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/14673 (geo-rep: Error message cleanup) posted (#2) for review on master by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/14673 committed in master by Jeff Darcy (jdarcy) ------ commit 3b69e25c0f3cf0b958fbd2b8459712ad21239caa Author: Aravinda VK <avishwan> Date: Wed Jun 8 16:56:26 2016 +0530 geo-rep: Error message cleanup If ssh returns 127 that means the remote gsyncd path is wrong or push-pem failed during create. Existing error message was pointing old documentation. Change-Id: Ifbbb4a604fc0ae0fd5cb2746df6363bf28cde1e9 BUG: 1343943 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/14673 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Milind Changire <mchangir> Reviewed-by: Kotresh HR <khiremat>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.0, please open a new bug report. glusterfs-3.9.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/