From: Malahal Naineni <malahal@us.ibm.com>
To: linux-nfs@vger.kernel.org
Subject: NFS with ActiveDirectory+Kerberos
Date: Tue, 1 Oct 2013 13:17:50 -0500 [thread overview]
Message-ID: <20131001181750.GA24424@us.ibm.com> (raw)
Hi All,
We are using RHEL6.1 as an NFS server, and we have configured an RHEL6.2
system as an NFS client. We configured AD+Kerberos set up on both these
machines. The kerberos TGT ticket is set to expire after a long time,
but the kerberos service ticket is set to expire only after a short time
(10 minutes), but the service ticket is renewable! NFS I/O fails around
when service ticket expires (EIO or EACCESS). If we retry the command
(or any command that generates NFS I/O), the service ticket gets renewed
and everything works until the next service expiry time.
Could this be an AD (Active Directory) related issue? Do auto renewing
service tickets work in NFS (nfs-utils-1.2.3-15.el6.x86_64)? We have
tried with 10 hour service ticket expiry time as well. Same issue, the
I/O fails after 10 hours!
I am not familiar with kerberos and NFS security. Is there a way to
manually (cron/script) renew those tickets and make it work without NFS
errors? I would appreciate any help.
Regards, Malahal.
reply other threads:[~2013-10-01 18:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131001181750.GA24424@us.ibm.com \
--to=malahal@us.ibm.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).