From: Kevin Coffman <kwc@citi.umich.edu>
To: "Beyersdorf, Wolfgang" <Wolfgang.Beyersdorf.Fa.Kontraktor@rwedea.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS4 / GSS: Problem with users accessing the mounted directories (with root, everything ist okay)
Date: Wed, 29 Sep 2010 10:21:06 -0400 [thread overview]
Message-ID: <AANLkTimHnNCaQrj2T4vuC8m3R_S8oqc9o6zQBW_GOGoo@mail.gmail.com> (raw)
In-Reply-To: <D4AFE98FB48D2F4CBFEACD015C9642DF026628@sha2122.hamburg.rwedea.de>
On Wed, Sep 29, 2010 at 5:02 AM, Beyersdorf, Wolfgang
<Wolfgang.Beyersdorf.Fa.Kontraktor@rwedea.com> wrote:
>
>
>
> Dear all,
>
> I got NFS4 with GSS running on CentOS 5. Everything is okay, all TGTs are okay and is working fine for the user ROOT.
>
> When I change to an other user, I got a permission denied, when I try to access the dierctory (e.g. ls -la)
>
> Here is the /var/log/messages part for this access (with full debugging on ndf, ndfs and rcp):
>
> Sep 29 10:11:59 sha9013 rpc.gssd[1645]: creating context with server nfs@sha9012.hamburg.rwedea.de <================================== system ist wating for 25 seconds
> Sep 29 10:12:23 sha9013 rpc.gssd[1645]: WARNING: Failed to create krb5 context for user with uid 569926353 for server sha9012.hamburg.rwedea.de
> Sep 29 10:12:23 sha9013 rpc.gssd[1645]: WARNING: Failed to create krb5 context for user with uid 569926353 for server sha9012.hamburg.rwedea.de
> [ ... ]
> Sep 29 10:12:23 sha9013 rpc.gssd[1645]: creating context with server nfs@sha9012.hamburg.rwedea.de
> Sep 29 10:12:48 sha9013 rpc.gssd[1645]: WARNING: Failed to create krb5 context for user with uid 569926353 for server sha9012.hamburg.rwedea.de
> Sep 29 10:12:48 sha9013 rpc.gssd[1645]: WARNING: Failed to create krb5 context for user with uid 569926353 for server sha9012.hamburg.rwedea.de
>
> A klist gives the following result:
> ========================
What does "klist -e" show?
>
> On the server, there is nothing inside the /var/log/messages
>
I assume there is output from svcgssd on the server when root accesses it?
The 25-second pauses sound as if there is an error of some kind on the
server and it is dropping the request rather than replying. Perhaps a
network trace would reveal something.
K.C.
next prev parent reply other threads:[~2010-09-29 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 9:02 NFS4 / GSS: Problem with users accessing the mounted directories (with root, everything ist okay) Beyersdorf, Wolfgang
2010-09-29 14:21 ` Kevin Coffman [this message]
[not found] ` <D4AFE98FB48D2F4CBFEACD015C9642DF02662B@sha2122.hamburg.rwedea.de>
[not found] ` <AANLkTi=FGmot-QyimqCk6O=zHto2fjxfpv1SAU6YrGhD@mail.gmail.com>
[not found] ` <D4AFE98FB48D2F4CBFEACD015C9642DF02662D@sha2122.hamburg.rwedea.de>
2010-09-29 15:13 ` Kevin Coffman
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=AANLkTimHnNCaQrj2T4vuC8m3R_S8oqc9o6zQBW_GOGoo@mail.gmail.com \
--to=kwc@citi.umich.edu \
--cc=Wolfgang.Beyersdorf.Fa.Kontraktor@rwedea.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).