From: "J. Bruce Fields" <bfields@fieldses.org>
To: Michael Guntsche <mike@it-loops.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Kerberos auth Problem with nfs3/4
Date: Tue, 3 Aug 2010 19:16:25 -0400 [thread overview]
Message-ID: <20100803231625.GD9752@fieldses.org> (raw)
In-Reply-To: <20100803215523.GA25413@gibson.comsick.at>
On Tue, Aug 03, 2010 at 11:55:24PM +0200, Michael Guntsche wrote:
> On 03 Aug 10 17:36, J. Bruce Fields wrote:
> > > Aug 3 23:12:23 gibson kernel: RPC: AUTH_GSS upcall timed out.
> > > Aug 3 23:12:23 gibson kernel: Please check user daemon is running.
> > >
> > > Of course all the daemons on the server are running and the system seems
> > > to work fine otherwise.
> >
> > That's actually a client-side complaint--if you're seeing it on the
> > server then it's probably the server trying to do a callback to an NFSv4
> > client. Are you running rpc.gssd as well as rpc.svcgssd on the server?
> > Might want to if you want delegations to work (but it's not a critical
> > problem).
> Yes, rpc.gssd as well as rpc.svcgssd is running on the server. To make
> matters worse I noticed something else with sec=krb5. This messages
> appears on first access to a file either read or write. Not always, it
> seems that it reappears after some timeout but it is sparmming my logs
> nevertheless. But what's worse is that I now got a Stale NFS file handle
> on the lost+found directory of the export. A lot of question marks and
> then just the name. I am now running with sec=sys and cannot up to now
> was not able to reproduce this problem. Is it possible that does two
> problems are related or are they completely separate from each other?
I doubt they're related.
Is there something special about the lost+found directory that would
lead to stale filehandles? I can't think why there would be.
--b.
> FYI the patched nfs-utils version is only running on the server for now
> but I do not think that this is the problem.
next prev parent reply other threads:[~2010-08-03 23:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:45 Kerberos auth Problem with nfs3/4 Michael Guntsche
2010-08-03 19:43 ` J. Bruce Fields
2010-08-03 20:13 ` Michael Guntsche
2010-08-03 21:19 ` Michael Guntsche
2010-08-03 21:36 ` J. Bruce Fields
2010-08-03 21:55 ` Michael Guntsche
2010-08-03 23:16 ` J. Bruce Fields [this message]
2010-08-04 5:29 ` Michael Guntsche
2010-08-03 22:20 ` Michael Guntsche
2010-08-03 23:14 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2010-08-03 16:27 Michael Guntsche
2010-08-03 19:03 Michael Guntsche
2010-08-03 20:07 ` Andy Adamson
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=20100803231625.GD9752@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mike@it-loops.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 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.