Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Kotresh Hiremath Ravishankar]

Answer inline

On Tue, Aug 28, 2018 at 4:28 PM, Krishna Verma  wrote:

> Hi Kotresh,
>
>
>
> I created the links before. Below is the detail.
>
>
>
> [root@gluster-poc-noida ~]# ls -l /usr/lib64 | grep libgfch
>
> lrwxrwxrwx   1 root root  30 Aug 28 14:59 libgfchangelog.so ->
> /usr/lib64/libgfchangelog.so.1
>

The link created is pointing to wrong library. Please fix this

#cd /usr/lib64
#rm libgfchangelog.so
#ln -s "libgfchangelog.so.0.0.1" libgfchangelog.so

lrwxrwxrwx   1 root root  23 Aug 23 23:35 libgfchangelog.so.0 ->
> libgfchangelog.so.0.0.1
>
> -rwxr-xr-x   1 root root   63384 Jul 24 19:11 libgfchangelog.so.0.0.1
>
> [root@gluster-poc-noida ~]# locate libgfchangelog.so
>
> /usr/lib64/libgfchangelog.so.0
>
> /usr/lib64/libgfchangelog.so.0.0.1
>
> [root@gluster-poc-noida ~]#
>
>
>
> Is it looks good what we exactly need or di I need to create any more link
> or How to get “libgfchangelog.so” file if missing.
>
>
>
> /Krishna
>
>
>
> *From:* Kotresh Hiremath Ravishankar 
> *Sent:* Tuesday, August 28, 2018 4:22 PM
> *To:* Krishna Verma 
> *Cc:* Sunny Kumar ; Gluster Users <
> gluster-users@gluster.org>
>
> *Subject:* Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not
> work
>
>
>
> EXTERNAL MAIL
>
> Hi Krishna,
>
> As per the output shared, I don't see the file "libgfchangelog.so" which
> is what is required.
>
> I only see "libgfchangelog.so.0". Please confirm "libgfchangelog.so" is
> present in "/usr/lib64/".
>
> If not create a symlink similar to "libgfchangelog.so.0"
>
>
>
> It should be something like below.
>
>
>
> #ls -l /usr/lib64 | grep libgfch
> -rwxr-xr-x. 1 root root1078 Aug 28 05:56 libgfchangelog.la
> 
> lrwxrwxrwx. 1 root root  23 Aug 28 05:56 libgfchangelog.so ->
> libgfchangelog.so.0.0.1
> lrwxrwxrwx. 1 root root  23 Aug 28 05:56 libgfchangelog.so.0 ->
> libgfchangelog.so.0.0.1
> -rwxr-xr-x. 1 root root  336888 Aug 28 05:56 libgfchangelog.so.0.0.1
>
>
>
> On Tue, Aug 28, 2018 at 4:04 PM, Krishna Verma  wrote:
>
> Hi Kotresh,
>
>
>
> Thanks for the response, I did that also but nothing changed.
>
>
>
> [root@gluster-poc-noida ~]# ldconfig /usr/lib64
>
> [root@gluster-poc-noida ~]# ldconfig -p | grep libgfchangelog
>
> libgfchangelog.so.0 (libc6,x86-64) =>
> /usr/lib64/libgfchangelog.so.0
>
> [root@gluster-poc-noida ~]#
>
>
>
> [root@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@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@gluster-poc-noida ~]# gluster volume geo-replication glusterep
> gluster-poc-sj::glusterep status
>
>
>
> MASTER NODE  MASTER VOLMASTER BRICK SLAVE USER
> SLAVESLAVE NODESTATUSCRAWL STATUS
> LAST_SYNCED
>
> 
> 
> -
>
> gluster-poc-noidaglusterep /data/gluster/gv0root
> gluster-poc-sj::glusterepN/A   FaultyN/A N/A
>
> noi-poc-gluster  glusterep /data/gluster/gv0root
>gluster-poc-sj::glusterepN/A   Faulty
> N/A N/A
>
> [root@gluster-poc-noida ~]#
>
>
>
> /Krishna
>
>
>
> *From:* Kotresh Hiremath Ravishankar 
> *Sent:* Tuesday, August 28, 2018 4:00 PM
> *To:* Sunny Kumar 
> *Cc:* Krishna Verma ; Gluster Users <
> gluster-users@gluster.org>
>
>
> *Subject:* Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not
> work
>
>
>
> EXTERNAL MAIL
>
> Hi Krishna,
>
> Since your libraries are in /usr/lib64, you should be doing
>
> #ldconfig /usr/lib64
>
> Confirm that below command lists the library
>
> #ldconfig -p | grep libgfchangelog
>
>
>
>
>
> On Tue, Aug 28, 2018 at 3:52 PM, Sunny Kumar  wrote:
>
> 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  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@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@gluster-poc-noida ~]# gluster volume geo-replication glusterep
> 

Re: [Gluster-users] Announcing Glusterfs release 3.12.13 (Long Term Maintenance)

[Niels de Vos]

On Tue, Aug 28, 2018 at 03:49:38PM +0200, Paolo Margara wrote:
> Hi,
> 
> we’ve now tested version 3.12.13 on our ovirt dev cluster and all seems
> to be ok (obviously it's too early to see if the infamous memory leak
> issue got fixed), I think that should be safe to move related packages
> from -test to release for centos-gluster312

Thanks! I've marked the packages for release and expect them to become
available on the CentOS mirrors during the day tomorrow.

Niels


> Greetings,
> 
>     Paolo M.
> 
> 
> Il 27/08/2018 07:40, Jiffin Tony Thottan ha scritto:
> >
> > The Gluster community is pleased to announce the release of Gluster
> > 3.12.13 (packages available at [1,2,3]).
> >
> > Release notes for the release can be found at [4].
> >
> > Thanks,
> > Gluster community
> >
> >
> > [1] https://download.gluster.org/pub/gluster/glusterfs/3.12/3.12.13/
> > [2] https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-3.12 
> > [3] https://build.opensuse.org/project/subprojects/home:glusterfs
> > [4] Release notes:
> > https://gluster.readthedocs.io/en/latest/release-notes/3.12.12/
> >
> >
> >
> > ___
> > Gluster-users mailing list
> > Gluster-users@gluster.org
> > https://lists.gluster.org/mailman/listinfo/gluster-users
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Announcing Glusterfs release 3.12.13 (Long Term Maintenance)

[Paolo Margara]

Hi,

we’ve now tested version 3.12.13 on our ovirt dev cluster and all seems
to be ok (obviously it's too early to see if the infamous memory leak
issue got fixed), I think that should be safe to move related packages
from -test to release for centos-gluster312

Greetings,

    Paolo M.


Il 27/08/2018 07:40, Jiffin Tony Thottan ha scritto:
>
> The Gluster community is pleased to announce the release of Gluster
> 3.12.13 (packages available at [1,2,3]).
>
> Release notes for the release can be found at [4].
>
> Thanks,
> Gluster community
>
>
> [1] https://download.gluster.org/pub/gluster/glusterfs/3.12/3.12.13/
> [2] https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-3.12 
> [3] https://build.opensuse.org/project/subprojects/home:glusterfs
> [4] Release notes:
> https://gluster.readthedocs.io/en/latest/release-notes/3.12.12/
>
>
>
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Upgrade gluster 3.7 to 4.1

[Pablo Schandin]

Hello!

I have some old 2-nodes replication gluster clusters with 3.7 and would 
need to upgrade them to 4.1. Is it safe to jump that much versions 
directly with the 'online'(so no downtime) documentation?


Or do you think I need to go through all the middle versions? For 
example, upgrade the cluster to 3.10, then 3.12 and then 4.1.


Thanks!

Pablo.




smime.p7s
Description: S/MIME Cryptographic Signature
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Krishna Verma]

Hi Kotresh,

I created the links before. Below is the detail.

[root@gluster-poc-noida ~]# ls -l /usr/lib64 | grep libgfch
lrwxrwxrwx   1 root root  30 Aug 28 14:59 libgfchangelog.so -> 
/usr/lib64/libgfchangelog.so.1
lrwxrwxrwx   1 root root  23 Aug 23 23:35 libgfchangelog.so.0 -> 
libgfchangelog.so.0.0.1
-rwxr-xr-x   1 root root   63384 Jul 24 19:11 libgfchangelog.so.0.0.1
[root@gluster-poc-noida ~]# locate libgfchangelog.so
/usr/lib64/libgfchangelog.so.0
/usr/lib64/libgfchangelog.so.0.0.1
[root@gluster-poc-noida ~]#

Is it looks good what we exactly need or di I need to create any more link or 
How to get “libgfchangelog.so” file if missing.

/Krishna

From: Kotresh Hiremath Ravishankar 
Sent: Tuesday, August 28, 2018 4:22 PM
To: Krishna Verma 
Cc: Sunny Kumar ; Gluster Users 
Subject: Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

EXTERNAL MAIL
Hi Krishna,
As per the output shared, I don't see the file "libgfchangelog.so" which is 
what is required.
I only see "libgfchangelog.so.0". Please confirm "libgfchangelog.so" is present 
in "/usr/lib64/".
If not create a symlink similar to "libgfchangelog.so.0"

It should be something like below.

#ls -l /usr/lib64 | grep libgfch
-rwxr-xr-x. 1 root root1078 Aug 28 05:56 
libgfchangelog.la
lrwxrwxrwx. 1 root root  23 Aug 28 05:56 libgfchangelog.so -> 
libgfchangelog.so.0.0.1
lrwxrwxrwx. 1 root root  23 Aug 28 05:56 libgfchangelog.so.0 -> 
libgfchangelog.so.0.0.1
-rwxr-xr-x. 1 root root  336888 Aug 28 05:56 libgfchangelog.so.0.0.1

On Tue, Aug 28, 2018 at 4:04 PM, Krishna Verma 
mailto:kve...@cadence.com>> wrote:
Hi Kotresh,

Thanks for the response, I did that also but nothing changed.

[root@gluster-poc-noida ~]# ldconfig /usr/lib64
[root@gluster-poc-noida ~]# ldconfig -p | grep libgfchangelog
libgfchangelog.so.0 (libc6,x86-64) => /usr/lib64/libgfchangelog.so.0
[root@gluster-poc-noida ~]#

[root@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@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@gluster-poc-noida ~]# gluster volume geo-replication glusterep 
gluster-poc-sj::glusterep status

MASTER NODE  MASTER VOLMASTER BRICK SLAVE USERSLAVE 
   SLAVE NODESTATUSCRAWL STATUSLAST_SYNCED
-
gluster-poc-noidaglusterep /data/gluster/gv0root  
gluster-poc-sj::glusterepN/A   FaultyN/A N/A
noi-poc-gluster  glusterep /data/gluster/gv0root  
gluster-poc-sj::glusterepN/A   FaultyN/A N/A
[root@gluster-poc-noida ~]#

/Krishna

From: Kotresh Hiremath Ravishankar 
mailto:khire...@redhat.com>>
Sent: Tuesday, August 28, 2018 4:00 PM
To: Sunny Kumar mailto:sunku...@redhat.com>>
Cc: Krishna Verma mailto:kve...@cadence.com>>; Gluster 
Users mailto:gluster-users@gluster.org>>

Subject: Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

EXTERNAL MAIL
Hi Krishna,
Since your libraries are in /usr/lib64, you should be doing
#ldconfig /usr/lib64
Confirm that below command lists the library
#ldconfig -p | grep libgfchangelog


On Tue, Aug 28, 2018 at 3:52 PM, Sunny Kumar 
mailto:sunku...@redhat.com>> wrote:
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 
mailto:kve...@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@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@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@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@gluster-poc-noida ~]# gluster volume 

Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Krishna Verma]

Hi Sunny,

[root@gluster-poc-noida ~]# ldconfig /usr/local/lib
[root@gluster-poc-noida ~]# ldconfig -p /usr/local/lib | grep libgf
libgfxdr.so.0 (libc6,x86-64) => /lib64/libgfxdr.so.0
libgfrpc.so.0 (libc6,x86-64) => /lib64/libgfrpc.so.0
libgfortran.so.3 (libc6,x86-64) => /lib64/libgfortran.so.3
libgfortran.so.1 (libc6,x86-64) => /lib64/libgfortran.so.1
libgfdb.so.0 (libc6,x86-64) => /lib64/libgfdb.so.0
libgfchangelog.so.0 (libc6,x86-64) => /lib64/libgfchangelog.so.0
libgfapi.so.0 (libc6,x86-64) => /lib64/libgfapi.so.0
[root@gluster-poc-noida ~]#

-Original Message-
From: Sunny Kumar  
Sent: Tuesday, August 28, 2018 3:53 PM
To: Krishna Verma 
Cc: gluster-users@gluster.org
Subject: Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

EXTERNAL MAIL


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 
 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@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@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@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@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@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@gluster-poc-noida ~]# vim 
> /usr/libexec/glusterfs/python/syncdaemon/repce.py
> [root@gluster-poc-noida ~]# systemctl restart glusterd 
> [root@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@gluster-poc-noida ~]# gluster volume geo-replication glusterep 
> gluster-poc-sj::glusterep status
>
> MASTER NODE  MASTER VOLMASTER BRICK SLAVE USERSLAVE   
>  SLAVE NODESTATUSCRAWL STATUSLAST_SYNCED
> -
> gluster-poc-noidaglusterep /data/gluster/gv0root  
> gluster-poc-sj::glusterepN/A   FaultyN/A N/A
> noi-poc-gluster  glusterep /data/gluster/gv0root  
> gluster-poc-sj::glusterepN/A   FaultyN/A N/A
> [root@gluster-poc-noida ~]#
>
>
> /Krishna.
>
> -Original Message-
> From: Sunny Kumar 
> Sent: Tuesday, August 28, 2018 3:17 PM
> To: Krishna Verma 
> Cc: gluster-users@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_=DwIBaQ=aUq983L2pue2FqKFoP6PGHMJQyoJ7kl3s3GZ-_haXqY=0E5nRoxLsT2ZXgCpJM_6ZItAWQ2jH8rVLG6tiXhoLFE=F0ExtFUfa_YCktOGvy82x3IAxvi2GrbPR72jZ8beuYk=fGtkmezHJj5YoLN3dUeVUCcYFnREHyOSk36mRjbTTEQ=
>  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  wrote:
> >
> > Hi Sunny,
> >
> > Thanks for your response, I tried both, but still I am getting the same 
> > error.
> >
> >
> > [root@noi-poc-gluster ~]# ldconfig /usr/lib [root@noi-poc-gluster 
> > ~]#
> >
> > [root@noi-poc-gluster ~]# ln -s /usr/lib64/libgfchangelog.so.1 
> > /usr/lib64/libgfchangelog.so [root@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 
> > Sent: Tuesday, August 28, 2018 2:55 PM
> > To: Krishna Verma 
> > Cc: gluster-users@gluster.org
> > Subject: Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does 
> > not work
> >
> > EXTERNAL MAIL
> >
> >
> > Hi Krish,

Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Kotresh Hiremath Ravishankar]

Hi Krishna,

As per the output shared, I don't see the file "libgfchangelog.so" which is
what is required.
I only see "libgfchangelog.so.0". Please confirm "libgfchangelog.so" is
present in "/usr/lib64/".
If not create a symlink similar to "libgfchangelog.so.0"

It should be something like below.

#ls -l /usr/lib64 | grep libgfch
-rwxr-xr-x. 1 root root1078 Aug 28 05:56 libgfchangelog.la
lrwxrwxrwx. 1 root root  23 Aug 28 05:56 libgfchangelog.so ->
libgfchangelog.so.0.0.1
lrwxrwxrwx. 1 root root  23 Aug 28 05:56 libgfchangelog.so.0 ->
libgfchangelog.so.0.0.1
-rwxr-xr-x. 1 root root  336888 Aug 28 05:56 libgfchangelog.so.0.0.1


On Tue, Aug 28, 2018 at 4:04 PM, Krishna Verma  wrote:

> Hi Kotresh,
>
>
>
> Thanks for the response, I did that also but nothing changed.
>
>
>
> [root@gluster-poc-noida ~]# ldconfig /usr/lib64
>
> [root@gluster-poc-noida ~]# ldconfig -p | grep libgfchangelog
>
> libgfchangelog.so.0 (libc6,x86-64) =>
> /usr/lib64/libgfchangelog.so.0
>
> [root@gluster-poc-noida ~]#
>
>
>
> [root@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@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@gluster-poc-noida ~]# gluster volume geo-replication glusterep
> gluster-poc-sj::glusterep status
>
>
>
> MASTER NODE  MASTER VOLMASTER BRICK SLAVE USER
> SLAVESLAVE NODESTATUSCRAWL STATUS
> LAST_SYNCED
>
> 
> 
> -
>
> gluster-poc-noidaglusterep /data/gluster/gv0root
> gluster-poc-sj::glusterepN/A   FaultyN/A N/A
>
> noi-poc-gluster  glusterep /data/gluster/gv0root
>gluster-poc-sj::glusterepN/A   Faulty
> N/A N/A
>
> [root@gluster-poc-noida ~]#
>
>
>
> /Krishna
>
>
>
> *From:* Kotresh Hiremath Ravishankar 
> *Sent:* Tuesday, August 28, 2018 4:00 PM
> *To:* Sunny Kumar 
> *Cc:* Krishna Verma ; Gluster Users <
> gluster-users@gluster.org>
>
> *Subject:* Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not
> work
>
>
>
> EXTERNAL MAIL
>
> Hi Krishna,
>
> Since your libraries are in /usr/lib64, you should be doing
>
> #ldconfig /usr/lib64
>
> Confirm that below command lists the library
>
> #ldconfig -p | grep libgfchangelog
>
>
>
>
>
> On Tue, Aug 28, 2018 at 3:52 PM, Sunny Kumar  wrote:
>
> 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  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@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@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@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@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@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@gluster-poc-noida ~]# vim /usr/libexec/glusterfs/python/
> syncdaemon/repce.py
> > [root@gluster-poc-noida ~]# systemctl restart glusterd
> > [root@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@gluster-poc-noida ~]# gluster volume geo-replication glusterep
> gluster-poc-sj::glusterep status
> >
> > MASTER NODE  MASTER VOLMASTER BRICK SLAVE USER
> SLAVESLAVE NODESTATUSCRAWL STATUS
> LAST_SYNCED
> > 
> 
> 

[Gluster-users] Geo-Replication Faulty.

[Krishna Verma]

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 VOLMASTER BRICK SLAVE USERSLAVE 
   SLAVE NODESTATUSCRAWL STATUSLAST_SYNCED
-
gluster-poc-noidaglusterep /data/gluster/gv0root  
gluster-poc-sj::glusterepN/A   FaultyN/A N/A
noi-poc-gluster  glusterep /data/gluster/gv0root  
gluster-poc-sj::glusterepN/A   FaultyN/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] : 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@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Krishna Verma]

Hi Kotresh,

Thanks for the response, I did that also but nothing changed.

[root@gluster-poc-noida ~]# ldconfig /usr/lib64
[root@gluster-poc-noida ~]# ldconfig -p | grep libgfchangelog
libgfchangelog.so.0 (libc6,x86-64) => /usr/lib64/libgfchangelog.so.0
[root@gluster-poc-noida ~]#

[root@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@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@gluster-poc-noida ~]# gluster volume geo-replication glusterep 
gluster-poc-sj::glusterep status

MASTER NODE  MASTER VOLMASTER BRICK SLAVE USERSLAVE 
   SLAVE NODESTATUSCRAWL STATUSLAST_SYNCED
-
gluster-poc-noidaglusterep /data/gluster/gv0root  
gluster-poc-sj::glusterepN/A   FaultyN/A N/A
noi-poc-gluster  glusterep /data/gluster/gv0root  
gluster-poc-sj::glusterepN/A   FaultyN/A N/A
[root@gluster-poc-noida ~]#

/Krishna

From: Kotresh Hiremath Ravishankar 
Sent: Tuesday, August 28, 2018 4:00 PM
To: Sunny Kumar 
Cc: Krishna Verma ; Gluster Users 

Subject: Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

EXTERNAL MAIL
Hi Krishna,
Since your libraries are in /usr/lib64, you should be doing
#ldconfig /usr/lib64
Confirm that below command lists the library
#ldconfig -p | grep libgfchangelog


On Tue, Aug 28, 2018 at 3:52 PM, Sunny Kumar 
mailto:sunku...@redhat.com>> wrote:
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 
mailto:kve...@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@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@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@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@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@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@gluster-poc-noida ~]# vim 
> /usr/libexec/glusterfs/python/syncdaemon/repce.py
> [root@gluster-poc-noida ~]# systemctl restart glusterd
> [root@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@gluster-poc-noida ~]# gluster volume geo-replication glusterep 
> gluster-poc-sj::glusterep status
>
> MASTER NODE  MASTER VOLMASTER BRICK SLAVE USERSLAVE   
>  SLAVE NODESTATUSCRAWL STATUSLAST_SYNCED
> -
> gluster-poc-noidaglusterep /data/gluster/gv0root  
> gluster-poc-sj::glusterepN/A   FaultyN/A N/A
> noi-poc-gluster  glusterep /data/gluster/gv0root  
> gluster-poc-sj::glusterepN/A   FaultyN/A N/A
> [root@gluster-poc-noida ~]#
>
>
> /Krishna.
>
> -Original Message-
> From: Sunny Kumar mailto:sunku...@redhat.com>>
> Sent: Tuesday, August 28, 2018 3:17 PM
> To: Krishna Verma mailto:kve...@cadence.com>>
> Cc: gluster-users@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
> 

Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Kotresh Hiremath Ravishankar]

Hi Krishna,

Since your libraries are in /usr/lib64, you should be doing

#ldconfig /usr/lib64

Confirm that below command lists the library

#ldconfig -p | grep libgfchangelog



On Tue, Aug 28, 2018 at 3:52 PM, Sunny Kumar  wrote:

> 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  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@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@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@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@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@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@gluster-poc-noida ~]# vim /usr/libexec/glusterfs/python/
> syncdaemon/repce.py
> > [root@gluster-poc-noida ~]# systemctl restart glusterd
> > [root@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@gluster-poc-noida ~]# gluster volume geo-replication glusterep
> gluster-poc-sj::glusterep status
> >
> > MASTER NODE  MASTER VOLMASTER BRICK SLAVE USER
> SLAVESLAVE NODESTATUSCRAWL STATUS
> LAST_SYNCED
> > 
> 
> -
> > gluster-poc-noidaglusterep /data/gluster/gv0root
> gluster-poc-sj::glusterepN/A   FaultyN/A N/A
> > noi-poc-gluster  glusterep /data/gluster/gv0root
> gluster-poc-sj::glusterepN/A   FaultyN/A N/A
> > [root@gluster-poc-noida ~]#
> >
> >
> > /Krishna.
> >
> > -Original Message-
> > From: Sunny Kumar 
> > Sent: Tuesday, August 28, 2018 3:17 PM
> > To: Krishna Verma 
> > Cc: gluster-users@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_=DwIBaQ=
> aUq983L2pue2FqKFoP6PGHMJQyoJ7kl3s3GZ-_haXqY=0E5nRoxLsT2ZXgCpJM_
> 6ZItAWQ2jH8rVLG6tiXhoLFE=F0ExtFUfa_YCktOGvy82x3IAxvi2GrbPR72jZ8beuYk=
> fGtkmezHJj5YoLN3dUeVUCcYFnREHyOSk36mRjbTTEQ= 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 
> wrote:
> > >
> > > Hi Sunny,
> > >
> > > Thanks for your response, I tried both, but still I am getting the
> same error.
> > >
> > >
> > > [root@noi-poc-gluster ~]# ldconfig /usr/lib [root@noi-poc-gluster ~]#
> > >
> > > [root@noi-poc-gluster ~]# ln -s /usr/lib64/libgfchangelog.so.1
> > > /usr/lib64/libgfchangelog.so [root@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 
> > > Sent: Tuesday, August 28, 2018 2:55 PM
> > > To: Krishna Verma 
> > > Cc: gluster-users@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 
> wrote:
> > > >
> > > > Hi
> > > >
> > > >
> > > >
> > > > I am getting below error in gsyncd.log
> > > >
> > > >
> > > >
> > > > OSError: 

Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Krishna Verma]

No, its again goes faulty after rebuild the session. And still getting the 
errors in the logs for lib

[root@gluster-poc-noida ~]# gluster volume geo-replication glusterep 
gluster-poc-sj::glusterep status

MASTER NODE  MASTER VOLMASTER BRICK SLAVE USERSLAVE 
   SLAVE NODESTATUSCRAWL STATUSLAST_SYNCED
-
gluster-poc-noidaglusterep /data/gluster/gv0root  
gluster-poc-sj::glusterepN/A   FaultyN/A N/A
noi-poc-gluster  glusterep /data/gluster/gv0root  
gluster-poc-sj::glusterepN/A   FaultyN/A N/A
[root@gluster-poc-noida ~]#

/krishna  

-Original Message-
From: Sunny Kumar  
Sent: Tuesday, August 28, 2018 3:56 PM
To: Krishna Verma 
Cc: gluster-users@gluster.org
Subject: Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

EXTERNAL MAIL


On Tue, Aug 28, 2018 at 3:55 PM Krishna Verma  wrote:
>
> Hi Sunny,
>
> [root@gluster-poc-noida ~]# ldconfig /usr/local/lib 
> [root@gluster-poc-noida ~]# ldconfig -p /usr/local/lib | grep libgf
> libgfxdr.so.0 (libc6,x86-64) => /lib64/libgfxdr.so.0
> libgfrpc.so.0 (libc6,x86-64) => /lib64/libgfrpc.so.0
> libgfortran.so.3 (libc6,x86-64) => /lib64/libgfortran.so.3
> libgfortran.so.1 (libc6,x86-64) => /lib64/libgfortran.so.1
> libgfdb.so.0 (libc6,x86-64) => /lib64/libgfdb.so.0
> libgfchangelog.so.0 (libc6,x86-64) => 
> /lib64/libgfchangelog.so.0
This is linked properly so check for geo-rep It should be working
> libgfapi.so.0 (libc6,x86-64) => /lib64/libgfapi.so.0 
> [root@gluster-poc-noida ~]#
>
> -Original Message-
> From: Sunny Kumar 
> Sent: Tuesday, August 28, 2018 3:53 PM
> To: Krishna Verma 
> Cc: gluster-users@gluster.org
> Subject: Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not 
> work
>
> EXTERNAL MAIL
>
>
> 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 
>  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@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@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@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@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@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@gluster-poc-noida ~]# vim 
> > /usr/libexec/glusterfs/python/syncdaemon/repce.py
> > [root@gluster-poc-noida ~]# systemctl restart glusterd 
> > [root@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@gluster-poc-noida ~]# gluster volume geo-replication glusterep 
> > gluster-poc-sj::glusterep status
> >
> > MASTER NODE  MASTER VOLMASTER BRICK SLAVE USERSLAVE 
> >SLAVE NODESTATUSCRAWL STATUSLAST_SYNCED
> > -
> > gluster-poc-noidaglusterep /data/gluster/gv0root  
> > gluster-poc-sj::glusterepN/A   FaultyN/A N/A
> > noi-poc-gluster  glusterep /data/gluster/gv0root  
> > gluster-poc-sj::glusterepN/A   FaultyN/A N/A
> > [root@gluster-poc-noida ~]#
> >
> >
> > /Krishna.
> >
> > -Original Message-
> > From: Sunny Kumar 
> > Sent: Tuesday, August 28, 2018 3:17 PM
> > To: Krishna Verma 
> > Cc: gluster-users@gluster.org
> > Subject: Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does 
> > not work
> >
> > EXTERNAL MAIL
> >
> >
> > With same log 

Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Sunny Kumar]

On Tue, Aug 28, 2018 at 3:55 PM Krishna Verma  wrote:
>
> Hi Sunny,
>
> [root@gluster-poc-noida ~]# ldconfig /usr/local/lib
> [root@gluster-poc-noida ~]# ldconfig -p /usr/local/lib | grep libgf
> libgfxdr.so.0 (libc6,x86-64) => /lib64/libgfxdr.so.0
> libgfrpc.so.0 (libc6,x86-64) => /lib64/libgfrpc.so.0
> libgfortran.so.3 (libc6,x86-64) => /lib64/libgfortran.so.3
> libgfortran.so.1 (libc6,x86-64) => /lib64/libgfortran.so.1
> libgfdb.so.0 (libc6,x86-64) => /lib64/libgfdb.so.0
> libgfchangelog.so.0 (libc6,x86-64) => /lib64/libgfchangelog.so.0
This is linked properly so check for geo-rep It should be working
> libgfapi.so.0 (libc6,x86-64) => /lib64/libgfapi.so.0
> [root@gluster-poc-noida ~]#
>
> -Original Message-
> From: Sunny Kumar 
> Sent: Tuesday, August 28, 2018 3:53 PM
> To: Krishna Verma 
> Cc: gluster-users@gluster.org
> Subject: Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work
>
> EXTERNAL MAIL
>
>
> 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 
>  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@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@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@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@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@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@gluster-poc-noida ~]# vim
> > /usr/libexec/glusterfs/python/syncdaemon/repce.py
> > [root@gluster-poc-noida ~]# systemctl restart glusterd
> > [root@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@gluster-poc-noida ~]# gluster volume geo-replication glusterep
> > gluster-poc-sj::glusterep status
> >
> > MASTER NODE  MASTER VOLMASTER BRICK SLAVE USERSLAVE 
> >SLAVE NODESTATUSCRAWL STATUSLAST_SYNCED
> > -
> > gluster-poc-noidaglusterep /data/gluster/gv0root  
> > gluster-poc-sj::glusterepN/A   FaultyN/A N/A
> > noi-poc-gluster  glusterep /data/gluster/gv0root  
> > gluster-poc-sj::glusterepN/A   FaultyN/A N/A
> > [root@gluster-poc-noida ~]#
> >
> >
> > /Krishna.
> >
> > -Original Message-
> > From: Sunny Kumar 
> > Sent: Tuesday, August 28, 2018 3:17 PM
> > To: Krishna Verma 
> > Cc: gluster-users@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_=DwIBaQ=aUq983L2pue2FqKFoP6PGHMJQyoJ7kl3s3GZ-_haXqY=0E5nRoxLsT2ZXgCpJM_6ZItAWQ2jH8rVLG6tiXhoLFE=F0ExtFUfa_YCktOGvy82x3IAxvi2GrbPR72jZ8beuYk=fGtkmezHJj5YoLN3dUeVUCcYFnREHyOSk36mRjbTTEQ=
> >  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  wrote:
> > >
> > > Hi Sunny,
> > >
> > > Thanks for your response, I tried both, but still I am getting the same 
> > > error.
> > >
> > >
> > > [root@noi-poc-gluster ~]# ldconfig /usr/lib [root@noi-poc-gluster
> > > ~]#
> > >
> > > [root@noi-poc-gluster ~]# ln -s /usr/lib64/libgfchangelog.so.1
> > > /usr/lib64/libgfchangelog.so [root@noi-poc-gluster ~]# ls -l
> > > /usr/lib64/libgfchangelog.so lrwxrwxrwx. 1 root root 30 Aug 28 14:59
> > > /usr/lib64/libgfchangelog.so -> 

Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Sunny Kumar]

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  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@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@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@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@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@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@gluster-poc-noida ~]# vim 
> /usr/libexec/glusterfs/python/syncdaemon/repce.py
> [root@gluster-poc-noida ~]# systemctl restart glusterd
> [root@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@gluster-poc-noida ~]# gluster volume geo-replication glusterep 
> gluster-poc-sj::glusterep status
>
> MASTER NODE  MASTER VOLMASTER BRICK SLAVE USERSLAVE   
>  SLAVE NODESTATUSCRAWL STATUSLAST_SYNCED
> -
> gluster-poc-noidaglusterep /data/gluster/gv0root  
> gluster-poc-sj::glusterepN/A   FaultyN/A N/A
> noi-poc-gluster  glusterep /data/gluster/gv0root  
> gluster-poc-sj::glusterepN/A   FaultyN/A N/A
> [root@gluster-poc-noida ~]#
>
>
> /Krishna.
>
> -Original Message-
> From: Sunny Kumar 
> Sent: Tuesday, August 28, 2018 3:17 PM
> To: Krishna Verma 
> Cc: gluster-users@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_=DwIBaQ=aUq983L2pue2FqKFoP6PGHMJQyoJ7kl3s3GZ-_haXqY=0E5nRoxLsT2ZXgCpJM_6ZItAWQ2jH8rVLG6tiXhoLFE=F0ExtFUfa_YCktOGvy82x3IAxvi2GrbPR72jZ8beuYk=fGtkmezHJj5YoLN3dUeVUCcYFnREHyOSk36mRjbTTEQ=
>  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  wrote:
> >
> > Hi Sunny,
> >
> > Thanks for your response, I tried both, but still I am getting the same 
> > error.
> >
> >
> > [root@noi-poc-gluster ~]# ldconfig /usr/lib [root@noi-poc-gluster ~]#
> >
> > [root@noi-poc-gluster ~]# ln -s /usr/lib64/libgfchangelog.so.1
> > /usr/lib64/libgfchangelog.so [root@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 
> > Sent: Tuesday, August 28, 2018 2:55 PM
> > To: Krishna Verma 
> > Cc: gluster-users@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  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.44method=init 
> > > error=OSError
> > >
> > > [2018-08-28 07:19:41.447041] E [syncdutils(worker 
> > > /data/gluster/gv0):330:log_raise_exception] : FAIL:
> > >
> > > 

Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Krishna Verma]

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@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@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@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@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@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@gluster-poc-noida ~]# vim 
/usr/libexec/glusterfs/python/syncdaemon/repce.py
[root@gluster-poc-noida ~]# systemctl restart glusterd
[root@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@gluster-poc-noida ~]# gluster volume geo-replication glusterep 
gluster-poc-sj::glusterep status

MASTER NODE  MASTER VOLMASTER BRICK SLAVE USERSLAVE 
   SLAVE NODESTATUSCRAWL STATUSLAST_SYNCED
-
gluster-poc-noidaglusterep /data/gluster/gv0root  
gluster-poc-sj::glusterepN/A   FaultyN/A N/A
noi-poc-gluster  glusterep /data/gluster/gv0root  
gluster-poc-sj::glusterepN/A   FaultyN/A N/A
[root@gluster-poc-noida ~]#


/Krishna.

-Original Message-
From: Sunny Kumar  
Sent: Tuesday, August 28, 2018 3:17 PM
To: Krishna Verma 
Cc: gluster-users@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_=DwIBaQ=aUq983L2pue2FqKFoP6PGHMJQyoJ7kl3s3GZ-_haXqY=0E5nRoxLsT2ZXgCpJM_6ZItAWQ2jH8rVLG6tiXhoLFE=F0ExtFUfa_YCktOGvy82x3IAxvi2GrbPR72jZ8beuYk=fGtkmezHJj5YoLN3dUeVUCcYFnREHyOSk36mRjbTTEQ=
 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  wrote:
>
> Hi Sunny,
>
> Thanks for your response, I tried both, but still I am getting the same error.
>
>
> [root@noi-poc-gluster ~]# ldconfig /usr/lib [root@noi-poc-gluster ~]#
>
> [root@noi-poc-gluster ~]# ln -s /usr/lib64/libgfchangelog.so.1 
> /usr/lib64/libgfchangelog.so [root@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 
> Sent: Tuesday, August 28, 2018 2:55 PM
> To: Krishna Verma 
> Cc: gluster-users@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  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.44method=init 
> > error=OSError
> >
> > [2018-08-28 07:19:41.447041] E [syncdutils(worker 
> > /data/gluster/gv0):330:log_raise_exception] : 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
> >
> > 

Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Sunny Kumar]

With same log message ?

Can you please verify that
https://review.gluster.org/#/c/glusterfs/+/20207/ 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  wrote:
>
> Hi Sunny,
>
> Thanks for your response, I tried both, but still I am getting the same error.
>
>
> [root@noi-poc-gluster ~]# ldconfig /usr/lib
> [root@noi-poc-gluster ~]#
>
> [root@noi-poc-gluster ~]# ln -s /usr/lib64/libgfchangelog.so.1 
> /usr/lib64/libgfchangelog.so
> [root@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 
> Sent: Tuesday, August 28, 2018 2:55 PM
> To: Krishna Verma 
> Cc: gluster-users@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  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.44method=init 
> > error=OSError
> >
> > [2018-08-28 07:19:41.447041] E [syncdutils(worker 
> > /data/gluster/gv0):330:log_raise_exception] : 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@gluster.org
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.gluster.org
> > _mailman_listinfo_gluster-2Dusers=DwIBaQ=aUq983L2pue2FqKFoP6PGHMJQ
> > yoJ7kl3s3GZ-_haXqY=0E5nRoxLsT2ZXgCpJM_6ZItAWQ2jH8rVLG6tiXhoLFE=_u6
> > vGRjlVsype7Z8hXDgCONilqVe4sIWkXNqqz2n3IQ=i0EUwtUHurhJHyw9UPpepCdLB70
> > 1mkxoNZWYvU7XXug=
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Krishna Verma]

Hi Sunny,

Thanks for your response, I tried both, but still I am getting the same error. 


[root@noi-poc-gluster ~]# ldconfig /usr/lib
[root@noi-poc-gluster ~]#

[root@noi-poc-gluster ~]# ln -s /usr/lib64/libgfchangelog.so.1 
/usr/lib64/libgfchangelog.so
[root@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  
Sent: Tuesday, August 28, 2018 2:55 PM
To: Krishna Verma 
Cc: gluster-users@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  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] : 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@gluster.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.gluster.org
> _mailman_listinfo_gluster-2Dusers=DwIBaQ=aUq983L2pue2FqKFoP6PGHMJQ
> yoJ7kl3s3GZ-_haXqY=0E5nRoxLsT2ZXgCpJM_6ZItAWQ2jH8rVLG6tiXhoLFE=_u6
> vGRjlVsype7Z8hXDgCONilqVe4sIWkXNqqz2n3IQ=i0EUwtUHurhJHyw9UPpepCdLB70
> 1mkxoNZWYvU7XXug=
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Sunny Kumar]

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  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] : 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@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Upgrade to 4.1.2 geo-replication does not work

[Krishna Verma]

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] : 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@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] Gluter 3.12.12: performance during heal and in general

[Hu Bert]

Hm, i noticed that in the shared.log (volume log file) on gluster11
and gluster12 (but not on gluster13) i now see these warnings:

[2018-08-28 07:18:57.224367] W [MSGID: 109011]
[dht-layout.c:186:dht_layout_search] 0-shared-dht: no subvolume for
hash (value) = 3054593291
[2018-08-28 07:19:17.733625] W [MSGID: 109011]
[dht-layout.c:186:dht_layout_search] 0-shared-dht: no subvolume for
hash (value) = 2595205890
[2018-08-28 07:19:27.950355] W [MSGID: 109011]
[dht-layout.c:186:dht_layout_search] 0-shared-dht: no subvolume for
hash (value) = 3105728076
[2018-08-28 07:19:42.519010] W [MSGID: 109011]
[dht-layout.c:186:dht_layout_search] 0-shared-dht: no subvolume for
hash (value) = 3740415196
[2018-08-28 07:19:48.194774] W [MSGID: 109011]
[dht-layout.c:186:dht_layout_search] 0-shared-dht: no subvolume for
hash (value) = 2922795043
[2018-08-28 07:19:52.506135] W [MSGID: 109011]
[dht-layout.c:186:dht_layout_search] 0-shared-dht: no subvolume for
hash (value) = 2841655539
[2018-08-28 07:19:55.466352] W [MSGID: 109011]
[dht-layout.c:186:dht_layout_search] 0-shared-dht: no subvolume for
hash (value) = 3049465001

Don't know if that could be related.


2018-08-28 8:54 GMT+02:00 Hu Bert :
> a little update after about 2 hours of uptime: still/again high cpu
> usage by one brick processes. server load >30.
>
> gluster11: high cpu; brick /gluster/bricksdd1/; no hdd exchange so far
> gluster12: normal cpu; brick /gluster/bricksdd1_new/; hdd change /dev/sdd
> gluster13: high cpu; brick /gluster/bricksdd1_new/; hdd change /dev/sdd
>
> The process for brick bricksdd1 consumes almost all 12 cores.
> Interestingly there are more threads for the bricksdd1 process than
> for the other bricks. Counted with "ps huH p  | wc
> -l"
>
> gluster11:
> bricksda1 59 threads, bricksdb1 65 threads, bricksdc1 68 threads,
> bricksdd1 85 threads
> gluster12:
> bricksda1 65 threads, bricksdb1 60 threads, bricksdc1 61 threads,
> bricksdd1_new 58 threads
> gluster13:
> bricksda1 61 threads, bricksdb1 60 threads, bricksdc1 61 threads,
> bricksdd1_new 82 threads
>
> Don't know if that could be relevant.
>
> 2018-08-28 7:04 GMT+02:00 Hu Bert :
>> Good Morning,
>>
>> today i update + rebooted all gluster servers, kernel update to
>> 4.9.0-8 and gluster to 3.12.13. Reboots went fine, but on one of the
>> gluster servers (gluster13) one of the bricks did come up at the
>> beginning but then lost connection.
>>
>> OK:
>>
>> Status of volume: shared
>> Gluster process TCP Port  RDMA Port  Online  Pid
>> --
>> [...]
>> Brick gluster11:/gluster/bricksdd1/shared 49155 0
>> Y   2506
>> Brick gluster12:/gluster/bricksdd1_new/shared49155 0
>> Y   2097
>> Brick gluster13:/gluster/bricksdd1_new/shared49155 0
>> Y   2136
>>
>> Lost connection:
>>
>> Brick gluster11:/gluster/bricksdd1/shared  49155 0
>>  Y   2506
>> Brick gluster12:/gluster/bricksdd1_new/shared 49155 0
>> Y   2097
>> Brick gluster13:/gluster/bricksdd1_new/shared N/A   N/A
>> N   N/A
>>
>> gluster volume heal shared info:
>> Brick gluster13:/gluster/bricksdd1_new/shared
>> Status: Transport endpoint is not connected
>> Number of entries: -
>>
>> reboot was at 06:15:39; brick then worked for a short period, but then
>> somehow disconnected.
>>
>> from gluster13:/var/log/glusterfs/glusterd.log:
>>
>> [2018-08-28 04:27:36.944608] I [MSGID: 106005]
>> [glusterd-handler.c:6071:__glusterd_brick_rpc_notify] 0-management:
>> Brick gluster13:/gluster/bricksdd1_new/shared has disconnected from
>> glusterd.
>> [2018-08-28 04:28:57.869666] I
>> [glusterd-utils.c:6056:glusterd_brick_start] 0-management: starting a
>> fresh brick process for brick /gluster/bricksdd1_new/shared
>> [2018-08-28 04:35:20.732666] I [MSGID: 106143]
>> [glusterd-pmap.c:295:pmap_registry_bind] 0-pmap: adding brick
>> /gluster/bricksdd1_new/shared on port 49157
>>
>> After 'gluster volume start shared force' (then with new port 49157):
>>
>> Brick gluster11:/gluster/bricksdd1/shared   49155 0
>>   Y   2506
>> Brick gluster12:/gluster/bricksdd1_new/shared  49155 0
>>  Y   2097
>> Brick gluster13:/gluster/bricksdd1_new/shared  49157 0
>>  Y   3994
>>
>> from /var/log/syslog:
>>
>> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: pending frames:
>> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: frame :
>> type(0) op(0)
>> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: frame :
>> type(0) op(0)
>> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]:
>> patchset: git://git.gluster.org/glusterfs.git
>> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: signal
>> received: 11
>> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: time of crash:
>> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]:
>> 2018-08-28 

Re: [Gluster-users] Gluter 3.12.12: performance during heal and in general

[Hu Bert]

a little update after about 2 hours of uptime: still/again high cpu
usage by one brick processes. server load >30.

gluster11: high cpu; brick /gluster/bricksdd1/; no hdd exchange so far
gluster12: normal cpu; brick /gluster/bricksdd1_new/; hdd change /dev/sdd
gluster13: high cpu; brick /gluster/bricksdd1_new/; hdd change /dev/sdd

The process for brick bricksdd1 consumes almost all 12 cores.
Interestingly there are more threads for the bricksdd1 process than
for the other bricks. Counted with "ps huH p  | wc
-l"

gluster11:
bricksda1 59 threads, bricksdb1 65 threads, bricksdc1 68 threads,
bricksdd1 85 threads
gluster12:
bricksda1 65 threads, bricksdb1 60 threads, bricksdc1 61 threads,
bricksdd1_new 58 threads
gluster13:
bricksda1 61 threads, bricksdb1 60 threads, bricksdc1 61 threads,
bricksdd1_new 82 threads

Don't know if that could be relevant.

2018-08-28 7:04 GMT+02:00 Hu Bert :
> Good Morning,
>
> today i update + rebooted all gluster servers, kernel update to
> 4.9.0-8 and gluster to 3.12.13. Reboots went fine, but on one of the
> gluster servers (gluster13) one of the bricks did come up at the
> beginning but then lost connection.
>
> OK:
>
> Status of volume: shared
> Gluster process TCP Port  RDMA Port  Online  Pid
> --
> [...]
> Brick gluster11:/gluster/bricksdd1/shared 49155 0
> Y   2506
> Brick gluster12:/gluster/bricksdd1_new/shared49155 0
> Y   2097
> Brick gluster13:/gluster/bricksdd1_new/shared49155 0
> Y   2136
>
> Lost connection:
>
> Brick gluster11:/gluster/bricksdd1/shared  49155 0
>  Y   2506
> Brick gluster12:/gluster/bricksdd1_new/shared 49155 0
> Y   2097
> Brick gluster13:/gluster/bricksdd1_new/shared N/A   N/A
> N   N/A
>
> gluster volume heal shared info:
> Brick gluster13:/gluster/bricksdd1_new/shared
> Status: Transport endpoint is not connected
> Number of entries: -
>
> reboot was at 06:15:39; brick then worked for a short period, but then
> somehow disconnected.
>
> from gluster13:/var/log/glusterfs/glusterd.log:
>
> [2018-08-28 04:27:36.944608] I [MSGID: 106005]
> [glusterd-handler.c:6071:__glusterd_brick_rpc_notify] 0-management:
> Brick gluster13:/gluster/bricksdd1_new/shared has disconnected from
> glusterd.
> [2018-08-28 04:28:57.869666] I
> [glusterd-utils.c:6056:glusterd_brick_start] 0-management: starting a
> fresh brick process for brick /gluster/bricksdd1_new/shared
> [2018-08-28 04:35:20.732666] I [MSGID: 106143]
> [glusterd-pmap.c:295:pmap_registry_bind] 0-pmap: adding brick
> /gluster/bricksdd1_new/shared on port 49157
>
> After 'gluster volume start shared force' (then with new port 49157):
>
> Brick gluster11:/gluster/bricksdd1/shared   49155 0
>   Y   2506
> Brick gluster12:/gluster/bricksdd1_new/shared  49155 0
>  Y   2097
> Brick gluster13:/gluster/bricksdd1_new/shared  49157 0
>  Y   3994
>
> from /var/log/syslog:
>
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: pending frames:
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: frame :
> type(0) op(0)
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: frame :
> type(0) op(0)
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]:
> patchset: git://git.gluster.org/glusterfs.git
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: signal
> received: 11
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: time of crash:
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]:
> 2018-08-28 04:27:36
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]:
> configuration details:
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: argp 1
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: backtrace 1
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: dlfcn 1
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: libpthread 1
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: llistxattr 1
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: setfsid 1
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: spinlock 1
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: epoll.h 1
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: xattr.h 1
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: st_atim.tv_nsec 
> 1
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]:
> package-string: glusterfs 3.12.13
> Aug 28 06:27:36 gluster13 gluster-bricksdd1_new-shared[2136]: -
>
> There are some errors+warnings in the shared.log (volume logfile), but
> no error message telling me why
> gluster13:/gluster/bricksdd1_new/shared has disconnected.
>
> Well... at the moment load is ok, all 3 servers at about 15 (but i
> think it will go up when more users will cause more 

Re: [Gluster-users] [Gluster-devel] Announcing Glusterfs release 3.12.13 (Long Term Maintenance)

[Pasi Kärkkäinen]

On Tue, Aug 28, 2018 at 10:12:06AM +0530, Jiffin Tony Thottan wrote:
> 
> 
> On Monday 27 August 2018 01:57 PM, Pasi Kärkkäinen wrote:
> >Hi,
> >
> >On Mon, Aug 27, 2018 at 11:10:21AM +0530, Jiffin Tony Thottan wrote:
> >>The Gluster community is pleased to announce the release of Gluster
> >>3.12.13 (packages available at [1,2,3]).
> >>
> >>Release notes for the release can be found at [4].
> >>
> >>Thanks,
> >>Gluster community
> >>
> >>[1] [1]https://download.gluster.org/pub/gluster/glusterfs/3.12/3.12.13/
> >>[2] [2]https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-3.12
> >>[3] [3]https://build.opensuse.org/project/subprojects/home:glusterfs
> >>[4] Release notes:
> >>[4]https://gluster.readthedocs.io/en/latest/release-notes/3.12.12/
> >>
> >Hmm, I guess release-notes link should say 
> >https://gluster.readthedocs.io/en/latest/release-notes/3.12.13 instead.. but 
> >that page doesn't seem to exist (yet) ?
> 
> It got fixed now :)
> 

Great, thanks!


-- Pasi

> Thanks,
> Jiffin
> 
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users

Re: [Gluster-users] KVM lockups on Gluster 4.1.1

[Amar Tumballi]

On Tue, Aug 28, 2018 at 11:24 AM, Dmitry Melekhov  wrote:

> Hello!
>
>
> Yesterday we hit something like this on 4.1.2
>
> Centos 7.5.
>
>
> Volume is replicated - two bricks and one arbiter.
>
>
> We rebooted arbiter, waited for heal end,  and tried to live migrate VM to
> another node ( we run VMs on gluster nodes ):
>
>
> [2018-08-27 09:56:22.085411] I [MSGID: 115029]
> [server-handshake.c:763:server_setvolume] 0-pool-server: accepted client
> from CTX_ID:b55f4a90-e241-48ce-bd4d-268c8a956f4a-GRAPH_ID:0-PID:
> 8887-HOST:son-PC_NAME:pool-
> client-6-RECON_NO:-0 (version: 4.1.2)
> [2018-08-27 09:56:22.107609] I [MSGID: 115036]
> [server.c:483:server_rpc_notify] 0-pool-server: disconnecting connection
> from CTX_ID:b55f4a90-e241-48ce-bd4d-268c8a956f4a-GRAPH_ID:0-PID:
> 8887-HOST:son-PC_NAME:pool-
> client-6-RECON_NO:-0
> [2018-08-27 09:56:22.107747] I [MSGID: 101055]
> [client_t.c:444:gf_client_unref] 0-pool-server: Shutting down connection
> CTX_ID:b55f4a90-e241-48ce-bd4d-268c8a956f4a-GRAPH_ID:0-PID:
> 8887-HOST:son-PC_NAME:pool-clien
> t-6-RECON_NO:-0
> [2018-08-27 09:58:37.905829] I [MSGID: 115036]
> [server.c:483:server_rpc_notify] 0-pool-server: disconnecting connection
> from CTX_ID:c3eb6cfc-2ef9-470a-89d1-a87170d00da5-GRAPH_ID:0-PID:
> 30292-HOST:father-PC_NAME:p
> ool-client-6-RECON_NO:-0
> [2018-08-27 09:58:37.905926] W [inodelk.c:610:pl_inodelk_log_cleanup]
> 0-pool-server: releasing lock on 12172afe-f0a4-4e10-bc0f-c5e4e0d9f318
> held by {client=0x7ffb58035bc0, pid=30292 lk-owner=28c831d8bc55}
> [2018-08-27 09:58:37.905959] W [inodelk.c:610:pl_inodelk_log_cleanup]
> 0-pool-server: releasing lock on 12172afe-f0a4-4e10-bc0f-c5e4e0d9f318
> held by {client=0x7ffb58035bc0, pid=30292 lk-owner=2870a7d6bc55}
> [2018-08-27 09:58:37.905979] W [inodelk.c:610:pl_inodelk_log_cleanup]
> 0-pool-server: releasing lock on 12172afe-f0a4-4e10-bc0f-c5e4e0d9f318
> held by {client=0x7ffb58035bc0, pid=30292 lk-owner=2880a7d6bc55}
> [2018-08-27 09:58:37.905997] W [inodelk.c:610:pl_inodelk_log_cleanup]
> 0-pool-server: releasing lock on 12172afe-f0a4-4e10-bc0f-c5e4e0d9f318
> held by {client=0x7ffb58035bc0, pid=30292 lk-owner=28f031d8bc55}
> [2018-08-27 09:58:37.906016] W [inodelk.c:610:pl_inodelk_log_cleanup]
> 0-pool-server: releasing lock on 12172afe-f0a4-4e10-bc0f-c5e4e0d9f318
> held by {client=0x7ffb58035bc0, pid=30292 lk-owner=28b07dd5bc55}
> [2018-08-27 09:58:37.906034] W [inodelk.c:610:pl_inodelk_log_cleanup]
> 0-pool-server: releasing lock on 12172afe-f0a4-4e10-bc0f-c5e4e0d9f318
> held by {client=0x7ffb58035bc0, pid=30292 lk-owner=28e0a7d6bc55}
> [2018-08-27 09:58:37.906056] W [inodelk.c:610:pl_inodelk_log_cleanup]
> 0-pool-server: releasing lock on 12172afe-f0a4-4e10-bc0f-c5e4e0d9f318
> held by {client=0x7ffb58035bc0, pid=30292 lk-owner=28b845d8bc55}
> [2018-08-27 09:58:37.906079] W [inodelk.c:610:pl_inodelk_log_cleanup]
> 0-pool-server: releasing lock on 12172afe-f0a4-4e10-bc0f-c5e4e0d9f318
> held by {client=0x7ffb58035bc0, pid=30292 lk-owner=2858a7d8bc55}
> [2018-08-27 09:58:37.906098] W [inodelk.c:610:pl_inodelk_log_cleanup]
> 0-pool-server: releasing lock on 12172afe-f0a4-4e10-bc0f-c5e4e0d9f318
> held by {client=0x7ffb58035bc0, pid=30292 lk-owner=2868a8d7bc55}
> [2018-08-27 09:58:37.906121] W [inodelk.c:610:pl_inodelk_log_cleanup]
> 0-pool-server: releasing lock on 12172afe-f0a4-4e10-bc0f-c5e4e0d9f318
> held by {client=0x7ffb58035bc0, pid=30292 lk-owner=28f80bd7bc55}
> ...
>
> [2018-08-27 09:58:37.907375] W [inodelk.c:610:pl_inodelk_log_cleanup]
> 0-pool-server: releasing lock on 12172afe-f0a4-4e10-bc0f-c5e4e0d9f318
> held by {client=0x7ffb58035bc0, pid=30292 lk-owner=28a8cdd6bc55}
> [2018-08-27 09:58:37.907393] W [inodelk.c:610:pl_inodelk_log_cleanup]
> 0-pool-server: releasing lock on 12172afe-f0a4-4e10-bc0f-c5e4e0d9f318
> held by {client=0x7ffb58035bc0, pid=30292 lk-owner=2880cdd6bc55}
> [2018-08-27 09:58:37.907476] I [socket.c:3837:socket_submit_reply]
> 0-tcp.pool-server: not connected (priv->connected = -1)
> [2018-08-27 09:58:37.907520] E [rpcsvc.c:1378:rpcsvc_submit_generic]
> 0-rpc-service: failed to submit message (XID: 0xcb88cb, Program: GlusterFS
> 4.x v1, ProgVers: 400, Proc: 30) to rpc-transport (tcp.pool-server)
> [2018-08-27 09:58:37.910727] E [server.c:137:server_submit_reply]
> (-->/usr/lib64/glusterfs/4.1.2/xlator/debug/io-stats.so(+0x20084)
> [0x7ffb64379084] -->/usr/lib64/glusterfs/4.1.2/
> xlator/protocol/server.so(+0x605
> ba) [0x7ffb5fddf5ba] -->/usr/lib64/glusterfs/4.1.2/
> xlator/protocol/server.so(+0xafce) [0x7ffb5fd89fce] ) 0-: Reply
> submission failed
> [2018-08-27 09:58:37.910814] E [rpcsvc.c:1378:rpcsvc_submit_generic]
> 0-rpc-service: failed to submit message (XID: 0xcb88ce, Program: GlusterFS
> 4.x v1, ProgVers: 400, Proc: 30) to rpc-transport (tcp.pool-server)
> [2018-08-27 09:58:37.910861] E [server.c:137:server_submit_reply]
> (-->/usr/lib64/glusterfs/4.1.2/xlator/debug/io-stats.so(+0x20084)
> [0x7ffb64379084] 

Re: [Gluster-users] file metadata operations performance - gluster 4.1

[Amar Tumballi]

One of the observation we had with git clone like work load was, nl-cache
(negative-lookup cache), helps here.

Try 'gluster volume set $volume-name nl-cache enable'.

Also sharing the 'profile info' during this performance observations also
helps us to narrow down the situation.

More on how to capture profile info @
https://hackmd.io/PhhT5jPdQIKxzfeLQmnjJQ?view

-Amar


On Thu, Aug 23, 2018 at 7:11 PM, Davide Obbi 
wrote:

> Hello,
>
> did anyone ever managed to achieve reasonable waiting time while
> performing metadata intensive operations such as git clone, untar etc...?
> Is this possible workload or will never be in scope for glusterfs?
>
> I'd like to know, if possible, what would be the options that affect such
> volume performances.
> Albeit i managed to achieve decent git status/git grep operations, 3 and
> 30 secs, the git clone and untarring a file from/to the same share take
> ages. for a git repo of aprox 6GB.
>
> I'm running a test environment with 3 way replica 128GB RAM and 24 cores
> are  2.40GHz, one internal SSD dedicated to the volume brick and 10Gb
> network
>
> The options set so far that affects volume performances are:
>  48 performance.readdir-ahead: on
>  49 features.cache-invalidation-timeout: 600
>  50 features.cache-invalidation: on
>  51 performance.md-cache-timeout: 600
>  52 performance.stat-prefetch: on
>  53 performance.cache-invalidation: on
>  54 performance.parallel-readdir: on
>  55 network.inode-lru-limit: 90
>  56 performance.io-thread-count: 32
>  57 performance.cache-size: 10GB
>
> ___
> Gluster-users mailing list
> Gluster-users@gluster.org
> https://lists.gluster.org/mailman/listinfo/gluster-users
>



-- 
Amar Tumballi (amarts)
___
Gluster-users mailing list
Gluster-users@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users