Krishna Verma
2018-Aug-28 10:15 UTC
[Gluster-users] Upgrade to 4.1.2 geo-replication does not work
Hi Sunny, I did the mentioned changes given in patch and restart the session for geo-replication. But again same errors in the logs. I have attaching the config files and logs here. [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep stop Stopping geo-replication session between glusterep & gluster-poc-sj::glusterep has been successful [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep delete Deleting geo-replication session between glusterep & gluster-poc-sj::glusterep has been successful [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep create push-pem force Creating geo-replication session between glusterep & gluster-poc-sj::glusterep has been successful [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep start geo-replication start failed for glusterep gluster-poc-sj::glusterep geo-replication command failed [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep start geo-replication start failed for glusterep gluster-poc-sj::glusterep geo-replication command failed [root at gluster-poc-noida ~]# vim /usr/libexec/glusterfs/python/syncdaemon/repce.py [root at gluster-poc-noida ~]# systemctl restart glusterd [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep start Starting geo-replication session between glusterep & gluster-poc-sj::glusterep has been successful [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep status 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 [root at gluster-poc-noida ~]# /Krishna. -----Original Message----- From: Sunny Kumar <sunkumar at redhat.com> Sent: Tuesday, August 28, 2018 3:17 PM To: Krishna Verma <kverma at cadence.com> Cc: gluster-users at gluster.org Subject: Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work EXTERNAL MAIL With same log message ? Can you please verify that https://urldefense.proofpoint.com/v2/url?u=https-3A__review.gluster.org_-23_c_glusterfs_-2B_20207_&d=DwIBaQ&c=aUq983L2pue2FqKFoP6PGHMJQyoJ7kl3s3GZ-_haXqY&r=0E5nRoxLsT2ZXgCpJM_6ZItAWQ2jH8rVLG6tiXhoLFE&m=F0ExtFUfa_YCktOGvy82x3IAxvi2GrbPR72jZ8beuYk&s=fGtkmezHJj5YoLN3dUeVUCcYFnREHyOSk36mRjbTTEQ&e= patch is present if not can you please apply that. and try with symlinking ln -s /usr/lib64/libgfchangelog.so.0 /usr/lib64/libgfchangelog.so. Please share the log also. Regards, Sunny On Tue, Aug 28, 2018 at 3:02 PM Krishna Verma <kverma at cadence.com> wrote:> > Hi Sunny, > > Thanks for your response, I tried both, but still I am getting the same error. > > > [root at noi-poc-gluster ~]# ldconfig /usr/lib [root at noi-poc-gluster ~]# > > [root at noi-poc-gluster ~]# ln -s /usr/lib64/libgfchangelog.so.1 > /usr/lib64/libgfchangelog.so [root at noi-poc-gluster ~]# ls -l > /usr/lib64/libgfchangelog.so lrwxrwxrwx. 1 root root 30 Aug 28 14:59 > /usr/lib64/libgfchangelog.so -> /usr/lib64/libgfchangelog.so.1 > > /Krishna > > -----Original Message----- > From: Sunny Kumar <sunkumar at redhat.com> > Sent: Tuesday, August 28, 2018 2:55 PM > To: Krishna Verma <kverma at cadence.com> > Cc: gluster-users at gluster.org > Subject: Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not > work > > EXTERNAL MAIL > > > Hi Krish, > > You can run - > #ldconfig /usr/lib > > If that still does not solves your problem you can do manual symlink > like - ln -s /usr/lib64/libgfchangelog.so.1 > /usr/lib64/libgfchangelog.so > > Thanks, > Sunny Kumar > On Tue, Aug 28, 2018 at 1:47 PM Krishna Verma <kverma at cadence.com> wrote: > > > > Hi > > > > > > > > I am getting below error in gsyncd.log > > > > > > > > OSError: libgfchangelog.so: cannot open shared object file: No such > > file or directory > > > > [2018-08-28 07:19:41.446785] E [repce(worker /data/gluster/gv0):197:__call__] RepceClient: call failed call=26469:139794524604224:1535440781.44 method=init error=OSError > > > > [2018-08-28 07:19:41.447041] 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 07:19:41.457555] I [repce(agent /data/gluster/gv0):80:service_loop] RepceServer: terminating on reaching EOF. > > > > [2018-08-28 07:19:42.440184] I [monitor(monitor):272:monitor] Monitor: > > worker died in startup phase brick=/data/gluster/gv0 > > > > > > > > Below is my file location: > > > > > > > > /usr/lib64/libgfchangelog.so.0 > > > > /usr/lib64/libgfchangelog.so.0.0.1 > > > > > > > > What I can do to fix it ? > > > > > > > > /Krish > > > > _______________________________________________ > > Gluster-users mailing list > > Gluster-users at gluster.org > > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.gluster.o > > rg > > _mailman_listinfo_gluster-2Dusers&d=DwIBaQ&c=aUq983L2pue2FqKFoP6PGHM > > JQ > > yoJ7kl3s3GZ-_haXqY&r=0E5nRoxLsT2ZXgCpJM_6ZItAWQ2jH8rVLG6tiXhoLFE&m=_ > > u6 > > vGRjlVsype7Z8hXDgCONilqVe4sIWkXNqqz2n3IQ&s=i0EUwtUHurhJHyw9UPpepCdLB > > 70 > > 1mkxoNZWYvU7XXug&e-------------- next part --------------An embedded and charset-unspecified text was scrubbed... Name: repce.py.txt URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20180828/4fc80a32/attachment.txt> -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: gsyncdconfig.py.txt URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20180828/4fc80a32/attachment-0001.txt> -------------- next part -------------- A non-text attachment was scrubbed... Name: gsyncd.log Type: application/octet-stream Size: 1304 bytes Desc: gsyncd.log URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20180828/4fc80a32/attachment.obj>
Sunny Kumar
2018-Aug-28 10:22 UTC
[Gluster-users] Upgrade to 4.1.2 geo-replication does not work
can you do ldconfig /usr/local/lib and share the output of ldconfig -p /usr/local/lib | grep libgf On Tue, Aug 28, 2018 at 3:45 PM Krishna Verma <kverma at cadence.com> wrote:> > Hi Sunny, > > I did the mentioned changes given in patch and restart the session for geo-replication. But again same errors in the logs. > > I have attaching the config files and logs here. > > > [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep stop > Stopping geo-replication session between glusterep & gluster-poc-sj::glusterep has been successful > [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep delete > Deleting geo-replication session between glusterep & gluster-poc-sj::glusterep has been successful > [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep create push-pem force > Creating geo-replication session between glusterep & gluster-poc-sj::glusterep has been successful > [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep start > geo-replication start failed for glusterep gluster-poc-sj::glusterep > geo-replication command failed > [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep start > geo-replication start failed for glusterep gluster-poc-sj::glusterep > geo-replication command failed > [root at gluster-poc-noida ~]# vim /usr/libexec/glusterfs/python/syncdaemon/repce.py > [root at gluster-poc-noida ~]# systemctl restart glusterd > [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep start > Starting geo-replication session between glusterep & gluster-poc-sj::glusterep has been successful > [root at gluster-poc-noida ~]# gluster volume geo-replication glusterep gluster-poc-sj::glusterep status > > 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 > [root at gluster-poc-noida ~]# > > > /Krishna. > > -----Original Message----- > From: Sunny Kumar <sunkumar at redhat.com> > Sent: Tuesday, August 28, 2018 3:17 PM > To: Krishna Verma <kverma at cadence.com> > Cc: gluster-users at gluster.org > Subject: Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work > > EXTERNAL MAIL > > > With same log message ? > > Can you please verify that > https://urldefense.proofpoint.com/v2/url?u=https-3A__review.gluster.org_-23_c_glusterfs_-2B_20207_&d=DwIBaQ&c=aUq983L2pue2FqKFoP6PGHMJQyoJ7kl3s3GZ-_haXqY&r=0E5nRoxLsT2ZXgCpJM_6ZItAWQ2jH8rVLG6tiXhoLFE&m=F0ExtFUfa_YCktOGvy82x3IAxvi2GrbPR72jZ8beuYk&s=fGtkmezHJj5YoLN3dUeVUCcYFnREHyOSk36mRjbTTEQ&e= patch is present if not can you please apply that. > and try with symlinking ln -s /usr/lib64/libgfchangelog.so.0 /usr/lib64/libgfchangelog.so. > > Please share the log also. > > Regards, > Sunny > On Tue, Aug 28, 2018 at 3:02 PM Krishna Verma <kverma at cadence.com> wrote: > > > > Hi Sunny, > > > > Thanks for your response, I tried both, but still I am getting the same error. > > > > > > [root at noi-poc-gluster ~]# ldconfig /usr/lib [root at noi-poc-gluster ~]# > > > > [root at noi-poc-gluster ~]# ln -s /usr/lib64/libgfchangelog.so.1 > > /usr/lib64/libgfchangelog.so [root at noi-poc-gluster ~]# ls -l > > /usr/lib64/libgfchangelog.so lrwxrwxrwx. 1 root root 30 Aug 28 14:59 > > /usr/lib64/libgfchangelog.so -> /usr/lib64/libgfchangelog.so.1 > > > > /Krishna > > > > -----Original Message----- > > From: Sunny Kumar <sunkumar at redhat.com> > > Sent: Tuesday, August 28, 2018 2:55 PM > > To: Krishna Verma <kverma at cadence.com> > > Cc: gluster-users at gluster.org > > Subject: Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not > > work > > > > EXTERNAL MAIL > > > > > > Hi Krish, > > > > You can run - > > #ldconfig /usr/lib > > > > If that still does not solves your problem you can do manual symlink > > like - ln -s /usr/lib64/libgfchangelog.so.1 > > /usr/lib64/libgfchangelog.so > > > > Thanks, > > Sunny Kumar > > On Tue, Aug 28, 2018 at 1:47 PM Krishna Verma <kverma at cadence.com> wrote: > > > > > > Hi > > > > > > > > > > > > I am getting below error in gsyncd.log > > > > > > > > > > > > OSError: libgfchangelog.so: cannot open shared object file: No such > > > file or directory > > > > > > [2018-08-28 07:19:41.446785] E [repce(worker /data/gluster/gv0):197:__call__] RepceClient: call failed call=26469:139794524604224:1535440781.44 method=init error=OSError > > > > > > [2018-08-28 07:19:41.447041] 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 07:19:41.457555] I [repce(agent /data/gluster/gv0):80:service_loop] RepceServer: terminating on reaching EOF. > > > > > > [2018-08-28 07:19:42.440184] I [monitor(monitor):272:monitor] Monitor: > > > worker died in startup phase brick=/data/gluster/gv0 > > > > > > > > > > > > Below is my file location: > > > > > > > > > > > > /usr/lib64/libgfchangelog.so.0 > > > > > > /usr/lib64/libgfchangelog.so.0.0.1 > > > > > > > > > > > > What I can do to fix it ? > > > > > > > > > > > > /Krish > > > > > > _______________________________________________ > > > Gluster-users mailing list > > > Gluster-users at gluster.org > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.gluster.o > > > rg > > > _mailman_listinfo_gluster-2Dusers&d=DwIBaQ&c=aUq983L2pue2FqKFoP6PGHM > > > JQ > > > yoJ7kl3s3GZ-_haXqY&r=0E5nRoxLsT2ZXgCpJM_6ZItAWQ2jH8rVLG6tiXhoLFE&m=_ > > > u6 > > > vGRjlVsype7Z8hXDgCONilqVe4sIWkXNqqz2n3IQ&s=i0EUwtUHurhJHyw9UPpepCdLB > > > 70 > > > 1mkxoNZWYvU7XXug&e=