From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: linux-nfs@vger.kernel.org
Subject: linux-image: on nfs4 server: RPC: AUTH_GSS upcall timed out Please check user daemon is running
Date: Thu, 08 Dec 2011 10:29:42 -0500 [thread overview]
Message-ID: <8762hrozdl.fsf@fifthhorseman.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Hello Linux-NFS folks--
I've got an nfs4 server running linux kernel 3.1.1 with nfs-utils 1.2.4.
When an NFSv4 client connects to the server using sec=krb5p, the kernel
emits:
[ 3505.754807] RPC: AUTH_GSS upcall timed out.
[ 3505.754810] Please check user daemon is running.
It's true, i don't have rpc.gssd running on the server (though i do have
rpc.svcgssd running).
But the client can go ahead and mount the filesystem anyway, and users
with the appropriate krb5 credentials on the clients can access files on
the server based on their credentials.
So it's not clear to me what this warning is about. Should i be
running rpc.gssd on the nfs server? If so, what functionality am i
losing out on by not running it? If i don't need to run it, why is the
kernel emitting this message?
--dkg
[-- Attachment #2: Type: application/pgp-signature, Size: 965 bytes --]
next reply other threads:[~2011-12-08 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 15:29 Daniel Kahn Gillmor [this message]
2011-12-08 17:45 ` linux-image: on nfs4 server: RPC: AUTH_GSS upcall timed out Please check user daemon is running J. Bruce Fields
2011-12-09 18:31 ` Daniel Kahn Gillmor
2011-12-09 19:10 ` J. Bruce Fields
2012-02-23 5:58 ` Daniel Kahn Gillmor
2012-02-28 19:49 ` J. Bruce Fields
2013-08-11 13:15 ` Mario Bachmann
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=8762hrozdl.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.