From: "Christian G. Warden" <cwarden@xerus.org>
To: Kevin Coffman <kwc@citi.umich.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs3/krb5 mounts fail
Date: Tue, 12 Dec 2006 15:38:13 -0800 [thread overview]
Message-ID: <20061212233813.GD21890@xerus.org> (raw)
In-Reply-To: <4d569c330612120920g3d36cfe6j8baaf3054fec6ac3@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
On Tue, Dec 12, 2006 at 12:20:33PM -0500, Kevin Coffman wrote:
> On 12/11/06, Christian G. Warden <cwarden@xerus.org> wrote:
> >I'm having a problem where nfs3 filesystems mounted with krb5 fail after
> >about 2 hours. In userspace, I get a permission denied error when
> >trying to access such a filesystem. Restarting rpc.svcgssd on the
> >server fixes the problem.
> >
> >Below is the debugging output from the client and server? Does anything
> >indicate where the problem might be?
> >
> >Thanks,
> >Christian
>
> I'm not sure what is going on. What kernel version is on the server?
It's 2.6.17 (Debian kernel 2.6.17-2-xen-686) on the server and 2.6.18
(Debian kernel 2.6.18-3-xen-686) on the client.
> The svcgssd messages indicate it is happy and sending down a context,
> but it appears that the kernel is dropping the request?
>
> >Dec 11 10:18:35 fs01 kernel: svc: got len=532
> >Dec 11 10:18:35 fs01 kernel: svc: svc_authenticate (6)
> >Dec 11 10:18:35 fs01 kernel: RPC: svcauth_gss: argv->iov_len = 504
> >Dec 11 10:18:35 fs01 kernel: Want update, refage=120, age=0
> >Dec 11 10:18:35 fs01 kernel: svc: svc_process dropit
> >Dec 11 10:18:35 fs01 kernel: svc: socket e6db9240 dropped request
>
> Followed by:
>
> >Dec 11 10:18:35 fs01 kernel: RPC: Succesfully imported new context.
>
> Could you send a network trace containing the conversation between
> client and server when this happens?
The dump is attached.
Thanks for your help.
Christian
[-- Attachment #2: dump.out --]
[-- Type: application/octet-stream, Size: 1572 bytes --]
[-- Attachment #3: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-12-12 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 18:55 nfs3/krb5 mounts fail Christian G. Warden
2006-12-12 17:20 ` Kevin Coffman
2006-12-12 23:38 ` Christian G. Warden [this message]
2006-12-13 2:07 ` Kevin Coffman
2006-12-13 2:17 ` Kevin Coffman
2006-12-13 4:38 ` J. Bruce Fields
2006-12-14 23:04 ` Christian G. Warden
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=20061212233813.GD21890@xerus.org \
--to=cwarden@xerus.org \
--cc=kwc@citi.umich.edu \
--cc=nfs@lists.sourceforge.net \
/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