All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joao Eduardo Luis <joao.luis@inktank.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [BUG] ceph-mon crashes
Date: Mon, 12 Nov 2012 17:05:43 +0000	[thread overview]
Message-ID: <50A12C67.50702@inktank.com> (raw)
In-Reply-To: <50A1114A.5070200@profihost.ag>

On 11/12/2012 03:10 PM, Stefan Priebe - Profihost AG wrote:
> Am 12.11.2012 15:58, schrieb Joao Eduardo Luis:
>> Hi Stefan,
>>
>>
>> Any chance you can get me a larger chunk of the log from the monitor
>> that was the leader by the time you issued those commands until the
>> point the monitor crashed (from the excerpt you provided, that should be
>> mon.b)?
> 
> Sure:
> https://www.dropbox.com/s/8e604bihk56m0yd/ceph-mon.b.log.1.gz
> 
> Greets,
> Stefan

Hi Stefan,


Thanks for the log.

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?


  -Joao

  reply	other threads:[~2012-11-12 17:05 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 [this message]
2012-11-12 18:30               ` Stefan Priebe
2012-11-12 20:40                 ` Joao Eduardo Luis
2012-11-12 21:20                   ` Stefan Priebe

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=50A12C67.50702@inktank.com \
    --to=joao.luis@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=s.priebe@profihost.ag \
    /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.