From: Valentijn Sessink <v.sessink@openoffice.nl>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Strange rpc.svcgssd behavior
Date: Tue, 16 Nov 2010 16:58:51 +0100 [thread overview]
Message-ID: <4CE2AA3B.6070302@openoffice.nl> (raw)
In-Reply-To: <1C8B051A-5DC1-4871-B9B9-96E571036A9B@oracle.com>
Hi Chuck,
We have been disabling NM for years now because of this. As far as I can
see from it's behaviour, it sets the hostname all by itself, during
startup (but I could be wrong here, didn't look in the source code).
V.
Chuck Lever schreef:
> ERROR: GSS-API: error in gss_acquire_cred(): Unspecified GSS failure. Minor code may provide more information - Key table entry not found
> unable to obtain root (machine) credentials
> do you have a keytab entry for nfs/<your.host>@<YOUR.REALM> in /etc/krb5.keytab?
[...]
> Removing "your.host your" from the "::1" entry makes this problem go away -- rpc.svcgssd starts up as expected.
>
> Now I reboot, and NetworkManager happily adds "your.host your" back to the "::1" entry, and rpc.svcgssd fails again. I haven't tried this, but I suspect if the ::1 entry weren't there, NM would add "your.host.net your" to the IPv4 loopback entry, and we'd have the same problem.
--
http://www.openoffice.nl/ Open Office - Linux Office Solutions
Valentijn Sessink v.sessink@openoffice.nl +31(0)20-4214059
next prev parent reply other threads:[~2010-11-16 16:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 17:39 Strange rpc.svcgssd behavior Chuck Lever
2010-11-16 15:58 ` Valentijn Sessink [this message]
2010-11-16 19:44 ` Valentijn Sessink
2010-11-16 20:17 ` Jim Rees
2010-11-16 20:22 ` Chuck Lever
2010-11-16 20:54 ` Jim Rees
2010-11-16 21:41 ` J. Bruce Fields
2010-11-16 21:42 ` Chuck Lever
2010-11-17 15:18 ` Steve Dickson
2010-11-17 15:30 ` Chuck Lever
2010-11-17 15:54 ` Kevin Coffman
2010-11-17 16:05 ` Chuck Lever
2010-11-17 16:26 ` Kevin Coffman
2010-11-17 17:51 ` Chuck Lever
2010-11-17 18:52 ` Valentijn Sessink
2010-11-17 16:15 ` Valentijn Sessink
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=4CE2AA3B.6070302@openoffice.nl \
--to=v.sessink@openoffice.nl \
--cc=chuck.lever@oracle.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 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.