[Gluster-users] Geo-Replication Faulty.

[Tiemen Ruiten]

I had the same issue a few weeks ago and found this thread which helped me
resolve it:
https://lists.gluster.org/pipermail/gluster-users/2018-July/034465.html

On 28 August 2018 at 08:50, Krishna Verma <kverma at cadence.com> wrote:

> Hi All,
>
>
>
> I need a help in setup geo replication as its getting faulty.
>
>
>
> I did the following :
>
>
>
>    1. Setup 2 node gluster with replicated volume.
>    2. Setup single node slave with gluster volume.
>    3. Setup geo-replication with master and slave but its status is
>    getting faulty.
>
>
>
> I have installed “glusterfs 4.1.2” on all the nodes.
>
>
>
> In logs I was getting below error:
>
>
>
> 2018-08-28 04:39:00.639724] E [syncdutils(worker
> /data/gluster/gv0):753:logerr] Popen: ssh> failure: execution of
> "/usr/local/sbin/glusterfs" failed with ENOENT (No such file or directory)
>
> My gluster binaries are in /use/sbin, So I did :
>
>
>
> gluster volume geo-replication glusterep gluster-poc-sj::glusterep config
> gluster_command_dir /usr/sbin/
>
> gluster volume geo-replication glusterep gluster-poc-sj::glusterep config
> slave_gluster_command_dir /usr/sbin/
>
>
>
> I also created the links as below :
>
>
>
> ln -s /usr/sbin/gluster /usr/local/sbin/gluster
>
> ln -s /usr/sbin/glusterfs /usr/local/sbin/glusterfs
>
>
>
> But status is still faulty after restarted glusterd and created a session
> again.
>
>
>
> MASTER NODE          MASTER VOL    MASTER BRICK         SLAVE USER
> SLAVE                        SLAVE NODE    STATUS    CRAWL STATUS
> LAST_SYNCED
>
> ------------------------------------------------------------
> ------------------------------------------------------------
> -----------------------------
>
> gluster-poc-noida    glusterep     /data/gluster/gv0    root
> gluster-poc-sj::glusterep    N/A           Faulty    N/A             N/A
>
> noi-poc-gluster      glusterep     /data/gluster/gv0    root
> gluster-poc-sj::glusterep    N/A           Faulty    N/A             N/A
>
>
>
> And now I am getting errors in logs for libraries.
>
>
>
> ============================================
>
> OSError: libgfchangelog.so: cannot open shared object file: No such file
> or directory
>
> [2018-08-28 06:46:46.667423] E [repce(worker /data/gluster/gv0):197:__call__]
> RepceClient: call failed  call=19929:140516964480832:1535438806.66
> method=init     error=OSError
>
> [2018-08-28 06:46:46.667567] E [syncdutils(worker
> /data/gluster/gv0):330:log_raise_exception] <top>: FAIL:
>
> Traceback (most recent call last):
>
>   File "/usr/libexec/glusterfs/python/syncdaemon/gsyncd.py", line 311, in
> main
>
>     func(args)
>
>   File "/usr/libexec/glusterfs/python/syncdaemon/subcmds.py", line 72, in
> subcmd_worker
>
>     local.service_loop(remote)
>
>   File "/usr/libexec/glusterfs/python/syncdaemon/resource.py", line 1236,
> in service_loop
>
>     changelog_agent.init()
>
>   File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 216, in
> __call__
>
>     return self.ins(self.meth, *a)
>
>   File "/usr/libexec/glusterfs/python/syncdaemon/repce.py", line 198, in
> __call__
>
>     raise res
>
> OSError: libgfchangelog.so: cannot open shared object file: No such file
> or directory
>
> [2018-08-28 06:46:46.678463] I [repce(agent /data/gluster/gv0):80:service_loop]
> RepceServer: terminating on reaching EOF.
>
> [2018-08-28 06:46:47.662086] I [monitor(monitor):272:monitor] Monitor:
> worker died in startup phase     brick=/data/gluster/gv0
>
>
>
>
>
> Any help please.
>
>
>
>
>
> /Krish
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
>



-- 
Tiemen Ruiten
Systems Engineer
R&D Media
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20180831/69f80478/attachment.html>