From: Chris Dunlop <chris@onthe.net.au>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Mon losing touch with OSDs
Date: Sat, 23 Feb 2013 12:10:29 +1100 [thread overview]
Message-ID: <20130223011029.GA9243@onthe.net.au> (raw)
In-Reply-To: <20130223005026.GA8844@onthe.net.au>
On Sat, Feb 23, 2013 at 11:50:26AM +1100, Chris Dunlop wrote:
> On Fri, Feb 22, 2013 at 04:25:39PM -0800, Sage Weil wrote:
>> Hi Chris-
>>
>> Can you confirm that both ceph-osd daemons are running v0.56.3 (i.e.,
>> they were restarted after the upgrade)?
>
> Not absolutely, but the indications are good: the osd.1 process
> was started Feb 16 08:38:43 2013, 20 minutes before I sent my
> email saying it had been upgraded. The osd.0 process was
> restarted more recently to kick things along after the most
> recent problem, however my command line history shows a "apt-get
> upgrade" followed by a "service ceph restart".
I can't see anything in the logs indicating the various daemon version
numbers.
Unless I'm blind and it's already there, perhaps a good idea for every
daemon to log it's version number when it starts?
Chris
next prev parent reply other threads:[~2013-02-23 1:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 3:29 Mon losing touch with OSDs Chris Dunlop
2013-02-15 4:57 ` Sage Weil
2013-02-15 22:05 ` Chris Dunlop
2013-02-17 23:41 ` Chris Dunlop
2013-02-18 1:44 ` Sage Weil
2013-02-19 3:02 ` Chris Dunlop
2013-02-20 2:07 ` Chris Dunlop
2013-02-22 3:06 ` Chris Dunlop
2013-02-22 21:57 ` Sage Weil
2013-02-22 23:35 ` Chris Dunlop
2013-02-22 23:43 ` Sage Weil
2013-02-23 0:08 ` Chris Dunlop
2013-02-23 0:13 ` Sage Weil
2013-02-23 0:25 ` Sage Weil
2013-02-23 0:50 ` Chris Dunlop
2013-02-23 1:10 ` Chris Dunlop [this message]
2013-02-23 0:57 ` Chris Dunlop
2013-02-23 1:30 ` Sage Weil
2013-02-23 1:49 ` Chris Dunlop
2013-02-23 1:52 ` Sage Weil
2013-02-23 2:02 ` Chris Dunlop
2013-03-01 2:02 ` Chris Dunlop
2013-03-01 5:00 ` Sage Weil
2013-03-08 3:12 ` Chris Dunlop
2013-03-08 22:47 ` Chris Dunlop
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=20130223011029.GA9243@onthe.net.au \
--to=chris@onthe.net.au \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@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.