From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tom H <tom-6kxvdouIZplzjhtm8Ag3mw@public.gmane.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Jul 22 23:53:35 serverNameNX: svc: unknown version (0 for prog 100003 nfsd)
Date: Tue, 3 Aug 2010 15:55:00 -0400 [thread overview]
Message-ID: <20100803195500.GF31579@fieldses.org> (raw)
In-Reply-To: <4C495DBA.6090600-6kxvdouIZplzjhtm8Ag3mw@public.gmane.org>
On Fri, Jul 23, 2010 at 10:15:38AM +0100, Tom H wrote:
>
> Hi,
>
> Since last week my syslog is full of these messages;
>
>
> Jul 22 23:53:35 serverNameNX: svc: unknown version (0 for prog 100003
> nfsd)
>
> <http://serverfault.com/questions/163306/jul-22-235335-servernamexxx-svc-unknown-version-0-for-prog-100003-nfsd>
>
>
> I think it is since we started to monitor for rpcinfo -p serverNameNX
> remotely.
I don't see why rpcinfo -p should be sending version 0 nfsd packets.
> Any suggestions on what I can do to either understand or suppress this
> alert?
We should probably just remove it some day.
--b.
prev parent reply other threads:[~2010-08-03 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 9:15 Jul 22 23:53:35 serverNameNX: svc: unknown version (0 for prog 100003 nfsd) Tom H
[not found] ` <4C495DBA.6090600-6kxvdouIZplzjhtm8Ag3mw@public.gmane.org>
2010-08-03 19:55 ` 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=20100803195500.GF31579@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tom-6kxvdouIZplzjhtm8Ag3mw@public.gmane.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).