From: Dan Mick <dan.mick@inktank.com>
To: Mike Dawson <mdawson@gammacode.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: 0.55 init script Issue?
Date: Wed, 05 Dec 2012 11:41:08 -0800 [thread overview]
Message-ID: <50BFA354.7040308@inktank.com> (raw)
In-Reply-To: <50BF7314.2020809@gammacode.com>
The story as best I know it is that we're trying to transition to and
use upstart where possible, but that the upstart config does not (yet?)
try to do what the init.d config did. That is, it doesn't support
options to the one script, but rather separates daemons into separate
services, and does not reach out to remote machines to start daemons, etc.
The intent is that init.d/ceph is left for non-Upstart distros, AFAICT.
Tv had some design notes here:
http://www.mail-archive.com/ceph-devel@vger.kernel.org/msg09314.html
We need better documentation/rationale here at least.
On 12/05/2012 08:15 AM, Mike Dawson wrote:
> All,
>
> After upgrading from 0.54 to 0.55, the command "service ceph start"
> fails. But "/etc/init.d/ceph start" works. This is the case for start.
> stop, etc. Here is an example:
>
> root@node2:~# /etc/init.d/ceph stop
> === mon.a ===
> Stopping Ceph mon.a on node2...kill 2505...done
> === osd.0 ===
> Stopping Ceph osd.0 on node2...kill 5042...done
> === osd.1 ===
> Stopping Ceph osd.1 on node2...kill 5116...done
> === osd.17 ===
> Stopping Ceph osd.17 on node2...kill 5275...done
>
>
> root@node2:~# service ceph start
> start: Job is already running: ceph
>
>
> root@node2:~# /etc/init.d/ceph start
> === mon.a ===
> Starting Ceph mon.a on node2...
> starting mon.a rank 0 at 172.16.1.2:6789/0 mon_data
> /var/lib/ceph/mon/ceph-a fsid 4951e786-945e-47b6-b1b1-4043b6cc3b55
> === osd.0 ===
> Starting Ceph osd.0 on node2...
> starting osd.0 at :/0 osd_data /var/lib/ceph/osd/ceph-0 /dev/sda6
> === osd.1 ===
> Starting Ceph osd.1 on node2...
> starting osd.1 at :/0 osd_data /var/lib/ceph/osd/ceph-1 /dev/sda7
> === osd.17 ===
> Starting Ceph osd.17 on node2...
> starting osd.17 at :/0 osd_data /var/lib/ceph/osd/ceph-17 /dev/sda8
>
>
> This is Ubuntu 12.10 with packages from debian-testing. One other user
> on IRC confirmed the same behavior. Is this a known issue?
>
>
> Thanks,
> Mike Dawson
>
> --
> 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
next prev parent reply other threads:[~2012-12-05 19:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 16:15 0.55 init script Issue? Mike Dawson
2012-12-05 17:19 ` Franck Marchand
2012-12-05 18:04 ` James Page
2012-12-05 19:41 ` Dan Mick [this message]
2012-12-05 19:57 ` David Zafman
2012-12-05 20:17 ` James Page
2012-12-05 20:39 ` Gregory Farnum
2012-12-06 0:11 ` Sage Weil
2012-12-06 1:34 ` Matthew Via
2012-12-06 13:28 ` Sage Weil
2012-12-06 13:35 ` Sage Weil
2012-12-07 21:38 ` Dan Mick
2012-12-10 9:13 ` James Page
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=50BFA354.7040308@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=mdawson@gammacode.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.