From: Joao Eduardo Luis <joao.luis@inktank.com>
To: Noah Watkins <noah.watkins@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: assertion failure in update_from_paxos
Date: Tue, 09 Jul 2013 20:47:54 +0100 [thread overview]
Message-ID: <51DC68EA.3020705@inktank.com> (raw)
In-Reply-To: <CA+Hcz5-QbboUXYsNU7jXe0Z8Lr6f5rTM=OCMJrm4ya9SchcYVA@mail.gmail.com>
On 07/09/2013 08:45 PM, Noah Watkins wrote:
> It appears to be resolved in master now.
Yep!
-Joao
>
> On Tue, Jul 9, 2013 at 12:43 PM, Joao Eduardo Luis
> <joao.luis@inktank.com> wrote:
>> On 07/09/2013 04:37 PM, Noah Watkins wrote:
>>>
>>> I'm getting the following failure when running a vstart instance with
>>> 1 of each daemon.
>>
>>
>> I can confirm this happens, as it just happened to me as well.
>>
>> My guess is that this is something Sage may have fixed last night, but will
>> have to check.
>>
>> -Joao
>>
>>>
>>> --
>>>
>>> 0> 2013-07-09 08:30:43.213345 7fdc289e97c0 -1 mon/OSDMonitor.cc: In
>>> function 'virtual void OSDMonitor::update_from_paxos(bool*)' thread
>>> 7fdc289e97c0 time 2013-07-09 08:30:43.207686
>>> mon/OSDMonitor.cc: 129: FAILED assert(latest_bl.length() != 0)
>>>
>>> ceph version 0.65-307-g0e93dd9
>>> (0e93dd93e5439fb82c416cb8eec7f36598ae7b48)
>>> 1: (OSDMonitor::update_from_paxos(bool*)+0x16bd) [0x5ad5ed]
>>> 2: (PaxosService::refresh(bool*)+0x143) [0x592963]
>>> 3: (Monitor::refresh_from_paxos(bool*)+0x57) [0x536c87]
>>> 4: (Paxos::finish_proposal()+0x3a) [0x58c13a]
>>> 5: (Paxos::begin(ceph::buffer::list&)+0x82c) [0x58bbac]
>>> 6: (Paxos::propose_queued()+0xd9) [0x58be79]
>>> 7: (Paxos::propose_new_value(ceph::buffer::list&, Context*)+0x140)
>>> [0x58d230]
>>> 8: (PaxosService::propose_pending()+0x6c8) [0x593c28]
>>> 9: (PaxosService::_active()+0x58b) [0x5956fb]
>>> 10: (PaxosService::election_finished()+0x328) [0x595c38]
>>> 11: (Monitor::win_election(unsigned int, std::set<int,
>>> std::less<int>, std::allocator<int> >&, unsigned long)+0x2e5)
>>> [0x55ae05]
>>> 12: (Monitor::win_standalone_election()+0x197) [0x55b027]
>>> 13: (Monitor::bootstrap()+0x84b) [0x55b8fb]
>>> 14: (Monitor::init()+0xad) [0x55bbcd]
>>> 15: (main()+0x1ac7) [0x5296b7]
>>> 16: (__libc_start_main()+0xf5) [0x3f2dc21b75]
>>> 17: ./ceph-mon() [0x52e259]
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>
>>
>> --
>> Joao Eduardo Luis
>> Software Engineer | http://inktank.com | http://ceph.com
--
Joao Eduardo Luis
Software Engineer | http://inktank.com | http://ceph.com
prev parent reply other threads:[~2013-07-09 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 15:37 assertion failure in update_from_paxos Noah Watkins
2013-07-09 19:43 ` Joao Eduardo Luis
2013-07-09 19:45 ` Noah Watkins
2013-07-09 19:47 ` Joao Eduardo Luis [this message]
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=51DC68EA.3020705@inktank.com \
--to=joao.luis@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=noah.watkins@inktank.com \
/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.