From: "J. Bruce Fields" <bfields@fieldses.org>
To: rauch.holger@googlemail.com
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>, linux-nfs@vger.kernel.org
Subject: Re: NFSv4: rpc.svcgssd claims that no machine credentials exist
Date: Mon, 6 Dec 2010 13:04:27 -0500 [thread overview]
Message-ID: <20101206180427.GA32657@fieldses.org> (raw)
In-Reply-To: <20101204233627.GD5862@gmail.com>
On Sun, Dec 05, 2010 at 12:36:28AM +0100, rauch.holger@googlemail.com wrote:
> Hi Trond,
>
> thanks for your reply. Please see my answer(s) below.
>
> On Wed, 01 Dec 2010, Trond Myklebust wrote:
>
> > [...]
> > ::1 my.host.name
> >
> > would completely screw up MIT kerberos's (and hence rpc.svcgssd's)
> > ability to figure out the correct fdqn for my server.
>
> Ok, but I have IPv6 disabled and thus also no such line in my /etc/hosts
> file since I removed it manually.
It could still be some problem with /etc/hosts; googling "/etc/hosts
kerberos" may get you more. And see also
http://www.citi.umich.edu/projects/nfsv4/linux/faq/.
> > [...]
> > Unfortunately, NetworkManager loves to add 'my.host.name' to any
> > existing '::1' line. The only solution I've found so far is to disable
> > NetworkManager on my server.
>
> I use Debian which doesn't use NetworkManager.
>
> >
> > The other interesting rpcsec bug I found recently had to do with
> > selinux: apparently MIT kerberos also likes to create a
> > [...]
>
> selinux is disabled as well.
>
> > [...]
>
> FYI, I also ran strace on the mentioned invocation of rpc.svcgssd but I
> couldn't figure out the principal name rpc.svcgssd is really looking for.
> How can I figure this out? Do I need some to enable debug logging in my
> /etc/krb5.conf file?
Adding -vvv to the rpc.svcgssd line may give you that information, I
can't remember.
--b.
prev parent reply other threads:[~2010-12-06 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 2:05 NFSv4: rpc.svcgssd claims that no machine credentials exist Holger Rauch
2010-12-02 2:34 ` Trond Myklebust
2010-12-04 23:36 ` rauch.holger
2010-12-06 18:04 ` J. Bruce Fields [this message]
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=20101206180427.GA32657@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rauch.holger@googlemail.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 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).