Skip to contentSkip to conversation

Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254

DISCUSSION Ben Hutchings 3 participants 8 messages May 22, 2010 – Aug 8, 2010 1 message not in the archive

Subsystems (2)
NFS client NFS server
lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Ben Hutchings

author
#1 lore raw
Quoted 8 lines · Steven Shiau

Same problem here. However, mine is on the client side.
On sid system, running kernel is 2.6.32-5-686, nfs-common is 1:1.2.2-1. When I mount my NFS server 192.168.120.254, it works. However, if I want to use some tool which need to lock file to save the file on the NFS server, e.g.
vgcfgbackup -f $NFS_MNT_POINT/vg.cfg
I get the message "lockd: cannot monitor 192.168.120.254", and the message shown on the /var/log/daemon.log:

Quoted 4 lines
May 21 08:52:44 debian rpc.statd[1298]: STAT_FAIL to debian for SM_MON 
of 192.168.120.254
May 21 08:52:44 debian rpc.statd[1298]: No canonical hostname found for

192.168.120.254

[...]

nfs-utils 1.2.2 includes the change:

commit 8ce130c4c828b9d13d429f22160f992b9c1d45cd

Author: Chuck Lever <[email protected]>
Date:   Thu Jan 14 12:24:15 2010 -0500

statd: Support IPv6 in sm_mon_1_svc()

This appears to have removed support for IPv4 literals. Was this intentional?

Ben.

Signature · 2 lines
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
#2 lore raw
Quoted 17 lines · Ben Hutchings
Quoted 8 lines · Steven Shiau

Same problem here. However, mine is on the client side.
On sid system, running kernel is 2.6.32-5-686, nfs-common is 1:1.2.2-1. When I mount my NFS server 192.168.120.254, it works. However, if I want to use some tool which need to lock file to save the file on the NFS server, e.g.
vgcfgbackup -f $NFS_MNT_POINT/vg.cfg
I get the message "lockd: cannot monitor 192.168.120.254", and the message shown on the /var/log/daemon.log:

Quoted 4 lines
May 21 08:52:44 debian rpc.statd[1298]: STAT_FAIL to debian for SM_MON
of 192.168.120.254
May 21 08:52:44 debian rpc.statd[1298]: No canonical hostname found for

192.168.120.254

[...]

nfs-utils 1.2.2 includes the change:

Quoted 8 lines

commit 8ce130c4c828b9d13d429f22160f992b9c1d45cd

Author: Chuck Lever<[email protected]>
Date:   Thu Jan 14 12:24:15 2010 -0500

statd: Support IPv6 in sm_mon_1_svc()

This appears to have removed support for IPv4 literals. Was this intentional?

statd usually requires a DNS reverse mapping for any host it monitors. Does your DNS have a reverse mapping for 192.168.120.254?

It looks like the new logic is more restrictive than the old statd when mon_name is a presentation address. The old code simply allowed presentation addresses with no reverse mapping. The new code requires a reverse DNS mapping for presentation addresses. I think even an entry in /etc/hosts would allow a raw address to work in this case.

We can probably remove the reverse mapping constraint for presentation addresses. A simple fix might be to change statd_canonical_name() from:

	freeaddrinfo(ai);
	if (!result)
		return NULL;

to

	freeaddrinfo(ai);
	if (!result)
		return strdup(hostname);

Let me know if this works.

#3 lore raw
Quoted 43 lines · Chuck Lever
Quoted 17 lines · Ben Hutchings
Quoted 8 lines · Steven Shiau

Same problem here. However, mine is on the client side.
On sid system, running kernel is 2.6.32-5-686, nfs-common is 1:1.2.2-1. When I mount my NFS server 192.168.120.254, it works. However, if I want to use some tool which need to lock file to save the file on the NFS server, e.g.
vgcfgbackup -f $NFS_MNT_POINT/vg.cfg
I get the message "lockd: cannot monitor 192.168.120.254", and the message shown on the /var/log/daemon.log:

Quoted 4 lines
May 21 08:52:44 debian rpc.statd[1298]: STAT_FAIL to debian for SM_MON
of 192.168.120.254
May 21 08:52:44 debian rpc.statd[1298]: No canonical hostname found for

192.168.120.254

[...]

nfs-utils 1.2.2 includes the change:

Quoted 8 lines

commit 8ce130c4c828b9d13d429f22160f992b9c1d45cd
Author: Chuck Lever<[email protected]>
Date: Thu Jan 14 12:24:15 2010 -0500

statd: Support IPv6 in sm_mon_1_svc()

This appears to have removed support for IPv4 literals. Was this intentional?

statd usually requires a DNS reverse mapping for any host it monitors. Does your DNS have a reverse mapping for 192.168.120.254?

It looks like the new logic is more restrictive than the old statd when mon_name is a presentation address. The old code simply allowed presentation addresses with no reverse mapping. The new code requires a reverse DNS mapping for presentation addresses. I think even an entry in /etc/hosts would allow a raw address to work in this case.

We can probably remove the reverse mapping constraint for presentation addresses. A simple fix might be to change statd_canonical_name() from:

freeaddrinfo(ai);
if (!result)
return NULL;

Quoted 7 lines

to

freeaddrinfo(ai);
if (!result)
return strdup(hostname);

Let me know if this works.

Any update? I have a patch ready for nfs-utils to fix this regression, but I need confirmation that it addresses your problem.

author
#4 lore raw
Quoted 1 line · Chuck Lever

On 05/24/10 11:22 AM, Chuck Lever wrote:

[...]

Quoted 9 lines
Quoted 9 lines

We can probably remove the reverse mapping constraint for presentation addresses. A simple fix might be to change statd_canonical_name() from:

freeaddrinfo(ai);
if (!result)
return NULL;

to

Quoted 8 lines
Quoted 5 lines

freeaddrinfo(ai);
if (!result)
return strdup(hostname);

Let me know if this works.

Any update? I have a patch ready for nfs-utils to fix this regression, but I need confirmation that it addresses your problem.

Steven originally had this problem, not me. Steven, do you need me to build a new package with this change?

Ben.

Signature · 2 lines
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
#5 lore raw
Quoted 7 lines · Ben Hutchings

On Thu, 2010-06-03 at 17:08 -0400, Chuck Lever wrote:
=20

Quoted 2 lines · Chuck Lever
    =20

[...]
=20

Quoted 1 line
Quoted 1 line

We can probably remove the reverse mapping constraint for presentatio=

n

Quoted 1 line
Quoted 1 line
Quoted 1 line

addresses. A simple fix might be to change statd_canonical_name() fro=

m:

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

freeaddrinfo(ai);
if (!result)
return NULL;

to

Quoted 7 lines
Quoted 7 lines
Quoted 6 lines

freeaddrinfo(ai);
if (!result)
return strdup(hostname);

Let me know if this works.

      =20

Any update? I have a patch ready for nfs-utils to fix this regression=

,

Quoted 8 lines
Quoted 2 lines

but I need confirmation that it addresses your problem.

    =20

Steven originally had this problem, not me. Steven, do you need me to build a new package with this change?

Ben.

=20

Ben,
Yes, please.
Thanks.

Steven.

--=20
Steven Shiau<steven _at_ nchc org tw> <steven _at_ stevenshiau org> National Center for High-performance Computing, Taiwan.
http://www.nchc.org.tw
Public Key Server PGP Key ID: 1024D/9762755A
Fingerprint: A2A1 08B7 C22C 3D06 34DB F4BC 08B3 E3D7 9762 755A

#6 lore raw
Quoted 7 lines · Steven Shiau
Quoted 4 lines · Ben Hutchings
Quoted 1 line · Chuck Lever

On 05/24/10 11:22 AM, Chuck Lever wrote:

[...]

Quoted 1 line
Quoted 1 line

We can probably remove the reverse mapping constraint for presenta=

tion

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

addresses. A simple fix might be to change statd_canonical_name() =

from:

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

freeaddrinfo(ai);
if (!result)
return NULL;

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 7 lines

to

freeaddrinfo(ai);
if (!result)
return strdup(hostname);

Let me know if this works.

Any update? I have a patch ready for nfs-utils to fix this regressi=

on,

Quoted 2 lines
Quoted 2 lines
Quoted 1 line

but I need confirmation that it addresses your problem.

Steven originally had this problem, not me. Steven, do you need me t=

o

Quoted 7 lines
Quoted 4 lines

build a new package with this change?

Ben.

Ben,
Yes, please.
Thanks.

Any progress on this?

author
#7 lore raw
Quoted 26 lines · Chuck Lever
Quoted 25 lines · Steven Shiau
Quoted 22 lines · Ben Hutchings
Quoted 1 line · Chuck Lever

On 05/24/10 11:22 AM, Chuck Lever wrote:

[...]

Quoted 9 lines
Quoted 9 lines

We can probably remove the reverse mapping constraint for presentation addresses. A simple fix might be to change statd_canonical_name() from:

freeaddrinfo(ai);
if (!result)
return NULL;

to

Quoted 7 lines
Quoted 5 lines

freeaddrinfo(ai);
if (!result)
return strdup(hostname);

Let me know if this works.

Any update? I have a patch ready for nfs-utils to fix this regression, but I need confirmation that it addresses your problem.

Steven originally had this problem, not me. Steven, do you need me to build a new package with this change?

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

Ben.

Ben,
Yes, please.
Thanks.

Any progress on this?

I've heard nothing from Steven but one positive report from another user. In any case we'll include this in our package.

We now have a git repository of the nfs-utils package at
<git://git.debian.org/kernel/nfs-utils.git>; currently our changes are kept in a quilt patch series in debian/patches.

Ben.

Signature · 2 lines
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
#8 lore raw
Quoted 9 lines · Ben Hutchings
Quoted 8 lines · Chuck Lever
Quoted 7 lines · Steven Shiau

=20
=20

Quoted 4 lines · Ben Hutchings
Quoted 1 line · Chuck Lever

On 05/24/10 11:22 AM, Chuck Lever wrote:

[...]

Quoted 1 line
Quoted 1 line

We can probably remove the reverse mapping constraint for presen=

tation

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

addresses. A simple fix might be to change statd_canonical_name(=

) from:

Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines
Quoted 12 lines

=20
freeaddrinfo(ai);
if (!result)
return NULL;
=20
to
=20
freeaddrinfo(ai);
if (!result)
return strdup(hostname);
=20
Let me know if this works.

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Any update? I have a patch ready for nfs-utils to fix this regres=

sion,

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 1 line

but I need confirmation that it addresses your problem.

Steven originally had this problem, not me. Steven, do you need me=

to

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines

build a new package with this change?
=20
Ben.
=20

Ben,
Yes, please.
Thanks.

Quoted 8 lines
Quoted 2 lines

=20
Any progress on this?

=20
I've heard nothing from Steven but one positive report from another user. In any case we'll include this in our package.
=20
We now have a git repository of the nfs-utils package at
<git://git.debian.org/kernel/nfs-utils.git>; currently our changes ar=

e

Quoted 1 line

kept in a quilt patch series in debian/patches.

Thanks, I'll submit the latest version of this to the nfs-utils maintai= ner.

--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com