linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ray Van Dolson <rvandolson@esri.com>
To: rhelv6-list@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: NFSv4 automount - nss_getpwnam name 'user@domain.com' does not map into domain 'localdomain'
Date: Tue, 18 Jan 2011 16:29:07 -0800	[thread overview]
Message-ID: <20110119002907.GA25400@esri.com> (raw)

Am doing a kickstart installation of RHEL 6.0 vanilla (no errata
applied).

After reboot, when using the automounter to access NFSv4 shares
(running on Fedora 13), we see the following in the logs on the RHEL6
client:

Jan 18 15:56:16 rhel6test rpc.idmapd[1387]: nss_getpwnam: name 'root@esri.com' does not map into domain 'localdomain'
Jan 18 15:56:16 rhel6test rpc.idmapd[1387]: nss_getpwnam: name 'ray5147@esri.com' does not map into domain 'localdomain'

As a result, directories are not mapped to the correct users but
instead to 'nobody'.

This is odd, because per the idmap man pages, the default domain used
by rpc.idmapd should be the same as the system domain minus the
hostname.  This should be esri.com, and is when I type hostname.

Thinking that perhaps rpc.idmapd was started before the network
subsystem, I restarted it.  Immediately everything worked fine.

I rebooted the system assuming the problem would return, but it didn't.
Maybe there's a cache used by rpc.idmapd (nscd?)?  Is there something
else maybe I'm missing?

Trying to determine if the "right" thing to do is to leave my
configuration as default or if I should be modifying /etc/idmapd.conf
to set a default domain.

Thanks,
Ray

             reply	other threads:[~2011-01-19  0:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19  0:29 Ray Van Dolson [this message]
2011-01-19 14:22 ` [rhelv6-list] NFSv4 automount - nss_getpwnam name 'user@domain.com' does not map into domain 'localdomain' Greg_Swift
2011-01-19 15:04   ` Ray Van Dolson
2011-01-19 15:52     ` Greg_Swift
2011-01-26 15:02       ` Dan Burkland

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=20110119002907.GA25400@esri.com \
    --to=rvandolson@esri.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rhelv6-list@redhat.com \
    /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).