Re: [ceph-users] Ceph Status - Segmentation Fault

2016-06-13 Thread Brad Hubbard
nd saw your bug this morning. Cheers, Brad -Original Message- > From: Brad Hubbard > To: Mathias Buresch > Cc: jsp...@redhat.com , ceph-us...@ceph.com e...@ceph.com> > Subject: Re: [ceph-users] Ceph Status - Segmentation Fault > Date: Thu, 2 Jun 2016 09:50:20 +1000 > &g

Re: [ceph-users] Ceph Status - Segmentation Fault

2016-06-13 Thread Mathias Buresch
Hey, I opened an issue at tracker.ceph.com -> http://tracker.ceph.com/issues /16266-Original Message- From: Brad Hubbard To: Mathias Buresch Cc: jsp...@redhat.com , ceph-us...@ceph.com Subject: Re: [ceph-users] Ceph Status - Segmentation Fault Date: Thu, 2 Jun 2016 09:50:20 +1

Re: [ceph-users] Ceph Status - Segmentation Fault

2016-06-01 Thread Brad Hubbard
t=..., in=..., this=0x7fffea882470) > at auth/cephx/../Crypto.h:110 > #1 encode_encrypt_enc_bl (cct=, > error="", out=..., key=..., t=) > at auth/cephx/CephxProtocol.h:464 > #2 encode_encrypt (cct=, error="", > out=..., key=..., t=) > at auth/ceph

Re: [ceph-users] Ceph Status - Segmentation Fault

2016-05-31 Thread Mathias Buresch
Mathias Buresch Subject: Re: [ceph-users] Ceph Status - Segmentation Fault Date: Wed, 25 May 2016 19:22:03 -0400 Hi John, This looks a lot like http://tracker.ceph.com/issues/12417 which is, of course, fixed. Worth gathering debug-auth=20 ? Maybe on the MON end as well? Cheers, Brad -

Re: [ceph-users] Ceph Status - Segmentation Fault

2016-05-25 Thread Brad Hubbard
om > Sent: Thursday, 26 May, 2016 12:57:47 AM > Subject: Re: [ceph-users] Ceph Status - Segmentation Fault > > There wasnt a package ceph-debuginfo available (Maybe bc I am running > Ubuntu). Have installed those: > > * ceph-dbg > * librados2-dbg > > There would b

Re: [ceph-users] Ceph Status - Segmentation Fault

2016-05-25 Thread Mathias Buresch
x7fffec0555d8) at msg/simple/DispatchQueue.cc:185 #9  0x731023bd in DispatchQueue::DispatchThread::entry (this=) at msg/simple/DispatchQueue.h:103 #10 0x77bc4182 in start_thread () from /lib/x86_64-linux- gnu/libpthread.so.0 #11 0x778f147d in clone () from /lib/x86_64-li

Re: [ceph-users] Ceph Status - Segmentation Fault

2016-05-25 Thread John Spray
883700 (LWP 23411)] > 0x73141a57 in ?? () from /usr/lib/librados.so.2 > (gdb) bt > #0 0x73141a57 in ?? () from /usr/lib/librados.so.2 > #1 0x00007ffff313aff4 in ?? () from /usr/lib/librados.so.2 > #2 0x72fe4a79 in ?? () from /usr/lib/librados.so.2 > #3 0

Re: [ceph-users] Ceph Status - Segmentation Fault

2016-05-25 Thread Mathias Buresch
0778f147d in clone () from /lib/x86_64-linux-gnu/libc.so.6   Does that help? I cant really see where the error is. :) -Original Message- From: John Spray To: Mathias Buresch Cc: ceph-us...@ceph.com Subject: Re: [ceph-users] Ceph Status - Segmentation Fault Date: Wed, 25 May 2016 10

Re: [ceph-users] Ceph Status - Segmentation Fault

2016-05-25 Thread John Spray
On Mon, May 23, 2016 at 12:41 PM, Mathias Buresch wrote: > Please found the logs with higher debug level attached to this email. You've attached the log from your mon, but it's not your mon that's segfaulting, right? You can use normal ceph command line flags to crank up the verbosity on the CLI

Re: [ceph-users] Ceph Status - Segmentation Fault

2016-05-24 Thread Brad Hubbard
/usr/bin/ceph is a python script so it's not segfaulting but some binary it's launching is and there doesn't appear to be much information about it in the log you uploaded. Are you able to capture a core file and generate a stack trace from gdb? The following may help to get some data. $ ulimit