All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: new in 2.6.0-test11: recv_rply: can't decode RPC message!
Date: Thu, 04 Dec 2003 00:52:24 +0100	[thread overview]
Message-ID: <3FCE7738.7010002@g-house.de> (raw)

hi,

i noticed *lots* of the following messages in my system log:

prinz rpc.statd[455]: recv_rply: can't decode RPC message!
prinz rpc.statd[455]: recv_rply: can't decode RPC message!
prinz rpc.statd[455]: recv_rply: can't decode RPC message!
prinz rpc.statd[455]: recv_rply: can't decode RPC message!

(yes, and so on). it's not flooding the log, but constantly filling it up.

this client is running Debian GNU/Linux (unstable) on i386.

nfs-common and nfs-kernel-server is both 1.0.6-1
(server is Debian GNU/Linux (unstable) on ppc32, not any busier than
before. kernel on the server is 2.4.23)

i noticed the messages on the client firtst with 2.6.0-test11, they did
not occur on any former kernelversions. however, the changelog to
-test11 does not reveal any nfs-related changes.


nfs-utils-1.0.6.orig/utils/statd/rmtcall.c  says at line 227:

if (!xdr_replymsg(xdrs, &mesg)) {
                 note(N_WARNING, "recv_rply: can't decode RPC message!\n");
                 goto done;
         }

any hints?

Thank you,
Christian.

-- 
BOFH excuse #254:

Interference from lunar radiation



                 reply	other threads:[~2003-12-03 23:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3FCE7738.7010002@g-house.de \
    --to=evil@g-house.de \
    --cc=linux-kernel@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.