Re: librados: failed to decode message of type 59 v1: buffer::end_of_buffer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 25/09/12 02:37, Sage Weil wrote:
> Hi John,
> 
> It looks like we aren't encoding the old format for the pool_stat_t 
> structure (which changed in v0.42).  Can you try with the patch from 
> wip-3212 applied?  You can get debs from the gitbuilders, see
> 
> 	http://ceph.com/docs/master/install/debian/
> 
> under development testing packages.
> 
> Thanks!
> sage
> 
> http://tracker.newdream.net/issues/3212

I've tested and this looks fixed (as in, my client now gives a better
error message when trying to connect). have responded to ticket 3212.
Thanks!

The logs are more helpful now but my client still hangs - how should I
detect this situation in code (using librados)? It just keeps trying to
connect and finally returns a "Connection timed out" error.

tbh, I presume this really isn't a common situation but just wanted to
be sure that I'm not missing something.

Thanks,

John.


> 
> On Mon, 24 Sep 2012, John Leach wrote:
> 
>> 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
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux