This list has been deprecated. Please subscribe to the new devel list at
lists.nfs-ganesha.org.
I think this is due to the low traffic. What that check says is that we
got new ops enqueued (1, in this case) but no ops dequeued. However,
since there was only 1 op enqueued, I suspect that the issue is that no
ops came in during the sampling period, except for one right at the end,
which hasn't been handled yet.
Does this message keep occurring? Or does it happen only once?
Daniel
On 09/24/2018 12:28 PM, David C wrote:
This list has been deprecated. Please subscribe to the new devel list at
lists.nfs-ganesha.org.
Hi All
CentOS 7.5
nfs-ganesha-vfs-2.6.3-1.el7.x86_64
nfs-ganesha-2.6.3-1.el7.x86_64
libntirpc-1.6.3-1.el7.x86_64
Exporting some directories with VFS FSAL
Nfsv3 only, currently very light traffic (a few clients connecting).
After starting Ganesha the following was logged after about 12 hours:
24/09/2018 12:11:00 : epoch 5ba8165e : fsrv01:
ganesha.nfsd-22835[dbus_heartbeat] nfs_health :DBUS :WARN :Health
status is unhealthy. enq new: 11925, old: 11924; deq new: 11924,
old: 11924
Nfs access still seems fine from the clients.
Could someone point me in the direction of how to diagnose this message
please?
Thanks,
David
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
