All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Kevin Coffman <kwc@citi.umich.edu>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] gssd: By default,	don't spam syslog when users' credentials expire
Date: Mon, 05 Jan 2009 15:09:29 -0500	[thread overview]
Message-ID: <496268F9.8010607@RedHat.com> (raw)
In-Reply-To: <20081217173927.3031.53736.stgit@jazz.citi.umich.edu>



Kevin Coffman wrote:
> Change the priority of "common" log messages so that syslog doesn't get
> slammed/spammed when users' credentials expire, or there is another common
> problem which would cause error messages for all context creation requests.
> 
> Note that this will now require that gssd or svcgssd option "-v" is used to
> debug these common cases.
> 
> Original patch from Andrew Pollock <apollock@google.com>.
> 
Committed... 

This took a little longer than expected do to a fairly
nasty bug in the Fedora 10 installation....

The installation process adds both the FQDN and the host name
(i.e. the non-FQDN) to the 127.0.0.1 line in /etc/hosts. This
causes gethostname() on the FQDN to return 127.0.0.1 instead of 
DNS IP address... This caused svcgssd to always fail due to 
the host name not being found in the key tab. 

Unfortunately it took quite a bit to figure out what host name the
kerberos libs were looking since the host name in the key tab was
indeed correct... That lib code is definitely lacking when it comes
to debug-ability... :-(

So buyer bewared... if you recently installed F-10 please check to see
if your /etc/hosts file only contains the non-FQDN host name on the
127.0.0.1 line. 

Details are at: https://bugzilla.redhat.com/show_bug.cgi?id=474086

steved.


  reply	other threads:[~2009-01-05 20:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 17:39 [PATCH] gssd: By default, don't spam syslog when users' credentials expire Kevin Coffman
2009-01-05 20:09 ` Steve Dickson [this message]
2009-01-05 21:53   ` Chuck Lever

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=496268F9.8010607@RedHat.com \
    --to=steved@redhat.com \
    --cc=kwc@citi.umich.edu \
    --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.