From: Orion Poplawski <orion@cora.nwra.com>
To: linux-nfs@vger.kernel.org
Subject: Re: rpc.idmapd: nss_getpwnam: name '#' does not map into domain
Date: Wed, 14 Aug 2013 19:24:54 +0000 (UTC) [thread overview]
Message-ID: <loom.20130814T212246-502@post.gmane.org> (raw)
In-Reply-To: loom.20130814T210744-290@post.gmane.org
Orion Poplawski <orion@...> writes:
>
> On our EL6 nfs servers we see periodic messages like:
>
> Aug 14 12:55:19 alexandria rpc.idmapd[19237]: nss_getpwnam: name '612' does
> not map into domain 'cora.nwra.com'
>
> I imagine that this is caused by a client actually passing the uid instead
> of the username for some reason but I have no idea how to track down which.
> Any ideas?
These *appear* to be triggered by the following types of requests:
Network File System, Ops(3): PUTFH SETATTR GETATTR
[Program Version: 4]
[V4 Procedure: COMP (1)]
Tag: <EMPTY>
length: 0
contents: <EMPTY>
minorversion: 0
Operations (count: 3)
Opcode: PUTFH (22)
filehandle
length: 28
[hash (CRC-32): 0xcdbd24f8]
decode type as: unknown
filehandle: 010006018355CA85FB1E02DF00000000000000000A00682B...
Opcode: SETATTR (34)
stateid
seqid: 0x00000000
Data: 000000000000000000000000
obj_attributes
attrmask
recc_attr: FATTR4_OWNER (36)
fattr4_owner: 612
length: 3
contents: 612
fill bytes: opaque data
recc_attr: FATTR4_OWNER_GROUP (37)
fattr4_owner_group: 1001
length: 4
contents: 1001
attr_vals: <DATA>
length: 16
contents: <DATA>
Opcode: GETATTR (9)
GETATTR4args
attr_request
bitmap[0] = 0x0010011a
[5 attributes requested]
mand_attr: FATTR4_TYPE (1)
mand_attr: FATTR4_CHANGE (3)
mand_attr: FATTR4_SIZE (4)
mand_attr: FATTR4_FSID (8)
recc_attr: FATTR4_FILEID (20)
bitmap[1] = 0x0030a23a
[9 attributes requested]
recc_attr: FATTR4_MODE (33)
recc_attr: FATTR4_NUMLINKS (35)
recc_attr: FATTR4_OWNER (36)
recc_attr: FATTR4_OWNER_GROUP (37)
recc_attr: FATTR4_RAWDEV (41)
recc_attr: FATTR4_SPACE_USED (45)
recc_attr: FATTR4_TIME_ACCESS (47)
recc_attr: FATTR4_TIME_METADATA (52)
recc_attr: FATTR4_TIME_MODIFY (53)
next prev parent reply other threads:[~2013-08-14 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 19:09 rpc.idmapd: nss_getpwnam: name '#' does not map into domain Orion Poplawski
2013-08-14 19:24 ` Orion Poplawski [this message]
2013-08-14 20:08 ` Myklebust, Trond
2013-08-14 20:27 ` Orion Poplawski
2013-08-16 20:51 ` J. Bruce Fields
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20130814T212246-502@post.gmane.org \
--to=orion@cora.nwra.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).