From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Jarod Beekman" <JBeekman@apu.edu>
Cc: <nfs@lists.sourceforge.net>
Subject: Re: Tracking rpc errors 'svc: unknown version (0)'
Date: 17 Jul 2002 17:09:24 +0200 [thread overview]
Message-ID: <shsr8i2tmqj.fsf@charged.uio.no> (raw)
In-Reply-To: <78B78720E680564CB7302950FA6CCF17D302EB@james.fs.apu.edu>
>>>>> " " == Jarod Beekman <JBeekman@apu.edu> writes:
> 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.
'ethereal' should be able to help you out here.
Just look for a null 'version' field in the RPC header: that should
tell you who and what the offender is.
If I were to hazard a guess, though, I'd expect that you will find
this is a NULL RPC request (i.e. the procedure number is '0') which is
often used in order to probe for whether or not an RPC server is up.
Cheers,
Trond
-------------------------------------------------------
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
next prev parent reply other threads:[~2002-07-17 15:09 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 [this message]
2002-07-17 15:27 ` Benjamin LaHaise
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=shsr8i2tmqj.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--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