My guess is that this is related to IPv6.  IPv6 support in 2.5 was
spotty, but that's been fixed since.  It's clearly using the 4-in-6
address (pretty common on a v6 enabled machine), and I don't believe it
could have used that in 2.5, so that's seems the smoking gun.

Does IPv6 work on your system?  If you ping ::ffff:10.0.0.7 on that box,
does it work?  If the problem is IPv6, you may be able to work around it
by preferring IPv4 to IPv6.  This is done by adding this line to
/etc/gai.conf:

precedence ::ffff:0:0/96  100

Daniel

On 09/11/2018 03:42 AM, Naresh Babu wrote:
> This list has been deprecated. Please subscribe to the new devel list at lists.nfs-ganesha.org.
>
>
>
> We have developed a custom FSAL on top of nfs-ganesha 2.5.4 version and
> lock tests ran fine with that. But, after upgrading nfs-ganesha to
> 2.6.2, lock tests are failing with the following errors:
>
> ganesha.nfsd-1419[svc_70] nsm_monitor :NLM :CRIT :Monitor
> ::ffff:10.0.0.7 SM_MON failed (1)
>
> /var/log/messages:
> Sep 11 07:26:27 mbclvm3 rpc.statd[1439]: SM_MON/SM_UNMON call from
> non-local host ::1
> Sep 11 07:26:27 mbclvm3 rpc.statd[1439]: STAT_FAIL to mbclvm3 for SM_MON
> of ::ffff:10.0.0.7
>
> $ rpcinfo -p |grep "status\|lockmgr"
>      100024    1   udp  46991  status
>      100024    1   tcp  33715  status
>      100021    4   udp  45075  nlockmgr
>      100021    4   tcp  45075  nlockmgr
>
>
>
>
> _______________________________________________
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>