Hello Olivier,
I attempted to recreate the issue with latest Ganesha code. It works fine for me.
$ rpm -qa | grep ganesha
gpfs.pm-ganesha-10.0.0-1.el8.x86_64
nfs-ganesha-gpfs-4-dev.7.el8.x86_64
nfs-ganesha-gpfs-debuginfo-4-dev.7.el8.x86_64
nfs-ganesha-selinux-4-dev.7.el8.noarch
nfs-ganesha-utils-debuginfo-4-dev.7.el8.x86_64
nfs-ganesha-4-dev.7.el8.x86_64
nfs-ganesha-debuginfo-4-dev.7.el8.x86_64
nfs-ganesha-utils-4-dev.7.el8.x86_64

[root@ganeshanode1 2020_03_04-12:42:50 fs1]$ ganesha_stats enable client_all_ops
Successfully enabled statistics counting
[root@ganeshanode1 2020_03_04-12:43:02 fs1]$ ganesha_stats list_clients

Timestamp: Wed Mar  4 12:43:33 2020606796548 nsecs
Client List:

Address: ::ffff:127.0.0.1
       NFSv3 stats available: 0
       MNT stats available: 0
       NLM4 stats available: 0
       RQUOTA stats available: 0
       NFSv4.0 stats available 0
       NFSv4.1 stats available: 0
       NFSv4.2 stats available: 0
       9P stats available: 0
Address: ::ffff:192.168.122.1
       NFSv3 stats available: 1
       MNT stats available: 1
       NLM4 stats available: 0
       RQUOTA stats available: 0
       NFSv4.0 stats available 0
       NFSv4.1 stats available: 0
       NFSv4.2 stats available: 0
       9P stats available: 0
[root@ganeshanode1 2020_03_04-12:43:33 fs1]$ ganesha_stats client_all_ops ::ffff:192.168.122.1

Client last active at: Wed Mar  4 12:43:15 202096989749 nsecs
               NFSv3 Operations
Op Name                  total   errors     dups
LOOKUP                        2         0         0
ACCESS                        1         0         0
CREATE                        1         0         0
MKDIR                         3         0         0
       No NLMv4 activity
       No NFSv4 activity
       No NFSv4 compound ops

My client is RHEL 8. I tried with IPV6 enabled & disabled mode. It works fine. 
$ cat /etc/redhat-release  
Red Hat Enterprise Linux release 8.0 (Ootpa)




On Mon, Mar 2, 2020 at 9:55 PM Olivier Garaud <olivier.garaud@scality.com> wrote:
Hi Sachin and Wyllys,

I'm running ganesha 3.2 and I'm facing the same stats issue.
Did you find what was going wrong ?

Thanks for your help,

Olivier

./ganesha_stats.py list_clients

Timestamp: Mon Mar  2 16:57:42 2020788845132 nsecs
Client List:

Address: ::ffff:10.0.61.12
NFSv3 stats available: 0
MNT stats available: 0
NLM4 stats available: 0
RQUOTA stats available: 0
NFSv4.0 stats available 1
NFSv4.1 stats available: 0
NFSv4.2 stats available: 0
9P stats available: 0

./ganesha_stats.py client_all_ops ::ffff:10.0.61.12
GANESHA RESPONSE STATUS: Client IP address not found

On Wed, Jan 22, 2020 at 3:34 PM Wyllys Ingersoll <wyllys.ingersoll@keepertech.com> wrote:

I did verify that the client had activity, in fact I was purposely generating activity on the client with the express purpose of generating stats so I could see what it was tracking and generating.  The issue is the "client_all_ops" doesn't recognize *any* of the valid IP addresses (as reported by list_clients) that I've tried to give it (with and without the leading "::ffff:").



On Wed, Jan 22, 2020 at 2:14 AM Sachin Punadikar <punadikar.sachin@gmail.com> wrote:
I suppose the client has no activity, hence the message.
You can validate it by running below:
#ganesha_stats list_clients
Typical o/p will be as below:
$ ganesha_stats list_clients

Timestamp: Wed Jan 22 12:37:40 2020165232526 nsecs
Client List:


Address: ::ffff:127.0.0.1
NFSv3 stats available: 0
MNT stats available: 0
NLM4 stats available: 0
RQUOTA stats available: 0
NFSv4.0 stats available 0
NFSv4.1 stats available: 0
NFSv4.2 stats available: 0
9P stats available: 0

Address: ::ffff:192.168.122.243
NFSv3 stats available: 0
MNT stats available: 0
NLM4 stats available: 0
RQUOTA stats available: 0
NFSv4.0 stats available 1
NFSv4.1 stats available: 0
NFSv4.2 stats available: 0
9P stats available: 0

If it is 0 for all fields for that client (like ::ffff:127.0.0.1 in above), then client_all_ops will fail.

On Wed, Jan 22, 2020 at 3:40 AM Wyllys Ingersoll <wyllys.ingersoll@keepertech.com> wrote:
Im running ganesha 3.2 and I've enabled "all" stats using ganesha_stats but whenever I try to display the stats, it always fails and says that the IP address is not found.  Is this a known issue or am I using it incorrectly?  I've made sure to mount from a v4 client and generate activity on the client.

```
# ganesha_stats client_all_ops ::ffff:10.15.15.2
GANESHA RESPONSE STATUS: Client IP address not found
```
_______________________________________________
Support mailing list -- support@lists.nfs-ganesha.org
To unsubscribe send an email to support-leave@lists.nfs-ganesha.org


--
with regards,
Sachin Punadikar
_______________________________________________
Support mailing list -- support@lists.nfs-ganesha.org
To unsubscribe send an email to support-leave@lists.nfs-ganesha.org


--

Olivier GARAUD

Scality

11, rue tronchet 75008 Paris

http://www.scality.com


--
with regards,
Sachin Punadikar