From: Stefan Priebe <s.priebe@profihost.ag>
To: Joao Eduardo Luis <joao.luis@inktank.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [BUG] ceph-mon crashes
Date: Mon, 12 Nov 2012 22:20:55 +0100 [thread overview]
Message-ID: <50A16837.9090801@profihost.ag> (raw)
In-Reply-To: <50A15ED9.6090207@inktank.com>
Thanks i'm subscribed to the tracker now.
Stefan
Am 12.11.2012 21:40, schrieb Joao Eduardo Luis:
> On 11/12/2012 06:30 PM, Stefan Priebe wrote:
>> Hi Joao,
>>
>> Am 12.11.2012 18:05, schrieb Joao Eduardo Luis:
>>> Can you please confirm me that sometime between you issuing the out
>>> command and mon.b failing, you had yet another monitor (maybe mon.a)
>>> that was the leader but for some reason it was down by the time that
>>> mon.b failed?
>>>
>>> If so, could you provide the log for that monitor as well, given this
>>> log doesn't have some infos I'm looking for?
>> Not sure but here are the logs of the other two mons:
>> https://www.dropbox.com/s/jztsedvj1b2kjje/ceph-mon.a.log.1.gz
>>
>> https://www.dropbox.com/s/62jkfbbbgvs5o25/ceph-mon.c.log.1.gz
>>
>> Thanks,
>> Stefan
>
> Thanks Stefan,
>
> I'll be looking into this.
>
> For future reference, I created issue #3477 on the tracker:
> http://tracker.newdream.net/issues/3477
>
> -Joao
> --
> 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
>
prev parent reply other threads:[~2012-11-12 21:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-11 21:51 [BUG] ceph-mon crashes Stefan Priebe
2012-11-11 22:20 ` Joao Eduardo Luis
2012-11-11 22:22 ` Stefan Priebe
2012-11-11 23:26 ` Joao Eduardo Luis
2012-11-12 6:21 ` Stefan Priebe - Profihost AG
2012-11-12 14:58 ` Joao Eduardo Luis
2012-11-12 15:10 ` Stefan Priebe - Profihost AG
2012-11-12 17:05 ` Joao Eduardo Luis
2012-11-12 18:30 ` Stefan Priebe
2012-11-12 20:40 ` Joao Eduardo Luis
2012-11-12 21:20 ` Stefan Priebe [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=50A16837.9090801@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@vger.kernel.org \
--cc=joao.luis@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.