From: John Hughes <john@Calva.COM>
To: peter.staubach@emc.com
Cc: Trond.Myklebust@netapp.com, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Don't spam kernel log with EKEYEXPIRED and EACCESS errors
Date: Fri, 18 Nov 2011 17:51:53 +0100 [thread overview]
Message-ID: <4EC68D29.7030005@Calva.COM> (raw)
In-Reply-To: <5E6794FC7B8FCA41A704019BE3C70E8B9422FC09@MX31A.corp.emc.com>
On 18/11/11 17:27, peter.staubach@emc.com wrote:
> Given that the poor user will be sitting, with almost nothing working because of the expired ticket, how does the user figure out what is going on or how does the admin help him?
>
> Some guidance seems like a good thing. Is there really a problem with these messages being printed to the log?
If you're sat at your console with nothing responding how are you going
to see the log messages?
The "ticket expired" messages are rate limited.
The "Error: state manager failed on NFSv4 server" messages are not rate
limited, but if you use my "rpc.gssd -e" hack they'll be written to the
log every 5 seconds all night long.
next prev parent reply other threads:[~2011-11-18 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 16:20 [PATCH] Don't spam kernel log with EKEYEXPIRED and EACCESS errors John Hughes
2011-11-18 16:27 ` peter.staubach
2011-11-18 16:34 ` Bryan Schumaker
2011-11-18 16:51 ` John Hughes [this message]
2011-11-18 17:50 ` peter.staubach
2011-11-18 18:30 ` Trond Myklebust
2011-11-18 19:17 ` John Hughes
[not found] <1020589474.75.1321635498473.JavaMail.root@thunderbeast.private.linuxbox.com>
2011-11-18 16:58 ` Matt W. Benjamin
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=4EC68D29.7030005@Calva.COM \
--to=john@calva.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=peter.staubach@emc.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