From: John Leach <john@brightbox.co.uk>
To: ceph-devel@vger.kernel.org
Subject: librados: failed to decode message of type 59 v1: buffer::end_of_buffer
Date: Mon, 24 Sep 2012 22:14:39 +0100 [thread overview]
Message-ID: <5060CD3F.7060101@brightbox.co.uk> (raw)
Hi,
I'm calling rados_ioctx_pool_stat and it's hanging.
logs show:
> 2012-09-24 21:30:08.411947 7f0041251700 failed to decode message of type 59 v1: buffer::end_of_buffer
> 2012-09-24 21:30:08.412286 7f0043255700 monclient: hunting for new mon
my local client is the Ubuntu Precise provided librados2 package
(0.41-1ubuntu2.1)
my cluster is running the unstable packages provided by Ceph
(0.51-1precise).
If I upgrade my client just up to the stable 0.48.1argonaut-1precise
package, it fixes the problem.
If the protocol changed, then I'd expect librados would let me know. Is
there some way to check this? rados_version returns the version of the
library, but I can't see how to get the version of the cluster (or quite
how I'd compare them in a meaningful way).
Thanks,
John.
--
UK multi-zone cloud: http://brightbox.com
next reply other threads:[~2012-09-24 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 21:14 John Leach [this message]
2012-09-25 1:37 ` librados: failed to decode message of type 59 v1: buffer::end_of_buffer Sage Weil
2012-09-25 9:54 ` John Leach
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=5060CD3F.7060101@brightbox.co.uk \
--to=john@brightbox.co.uk \
--cc=ceph-devel@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.