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