Linux NFS development
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@redhat.com>
To: Jarod Beekman <JBeekman@apu.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: Tracking rpc errors 'svc: unknown version (0)'
Date: Wed, 17 Jul 2002 11:27:32 -0400	[thread overview]
Message-ID: <20020717112732.A2361@redhat.com> (raw)
In-Reply-To: <78B78720E680564CB7302950FA6CCF17D302EB@james.fs.apu.edu>; from JBeekman@apu.edu on Wed, Jul 17, 2002 at 07:41:02AM -0700

On Wed, Jul 17, 2002 at 07:41:02AM -0700, Jarod Beekman wrote:
> I upgraded our nfs server from 2.4.9-34 Redhat 7.2 to 2.4.18-5 Redhat
> 7.3 and I am now seeing 'svc: unknown version (0)' errors.  Poking
> around on the list and the net tells me that this is a reflection of an
> unrecognized rpc request.  Is this correct, and if so is there a way to
> track down the source and nature of the request?  Thanks for your help.

Whoops, that's a patch that got lost between 2.4.9-34 and 2.4.18-5.  The 
message is a null rpc request, and can be safely ignored.

		-ben
-- 
"You will be reincarnated as a toad; and you will be much happier."


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      parent reply	other threads:[~2002-07-17 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17 14:41 Tracking rpc errors 'svc: unknown version (0)' Jarod Beekman
2002-07-17 15:09 ` Trond Myklebust
2002-07-17 15:27 ` Benjamin LaHaise [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=20020717112732.A2361@redhat.com \
    --to=bcrl@redhat.com \
    --cc=JBeekman@apu.edu \
    --cc=nfs@lists.sourceforge.net \
    /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