From: James Page <james.page@ubuntu.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 18:04:40 +0000 [thread overview]
Message-ID: <50BF8CB8.5060708@ubuntu.com> (raw)
In-Reply-To: <50BF7314.2020809@gammacode.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Mike
On 05/12/12 16:15, Mike Dawson wrote:
> 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 ===
I'd not noticed this either but it looks like there is both an upstart
configuration called 'ceph' (service ceph start) and an init script
called ceph (/etc/init.d/ceph start); this does not sound right to me
and I can't see what the ceph upstart configuration is actually doing
other than generating an event (which nothing is listening to).
The packages should ship one or the other IMHO.
- --
James Page
Ubuntu Core Developer
Debian Maintainer
james.page@ubuntu.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQIcBAEBCAAGBQJQv4y3AAoJEL/srsug59jDlnYP/AwOyWOSaScKFGiOnZHp7zpq
3QyKC4AGzIN7IH33kMJecu0diFaeJrlfZ/U6yv4jduVeUOpVf7ZUwma3d5WGOkg5
B1e5uTBYMabdZdZ2XnHRfChrDueMo4+Y+DinETeB8diL8xzP9vitCaAJxpavT5UQ
qKhO5ZwGSL9zWhtsN5QKc/qYv0ZbonUivMxKm+Imzgc6uuka7Z0JR+ETr9VJml4D
LOBM3dZKzF4ryPqpfeSGbI8W566qHm9MSIvBEcNNxUys+qjDMd/kLoP+SwYblD0H
sjDohj1xdnRIDf4y5FUh50HHl9Dy8NjGnA9X8bwDspiykNgU4kc2d6wHHpKMPMzA
6IywpifEZ9dD65Gbbqep8qQiXsjQDY/2V+c1RFDHripRg3AaXuPnZIxPGw7RevTJ
MMnYABVTT1jhfdpC0pzeIgdd5v55/1r30H4YyMV59pTIeuje6e+og2wXrhgky41N
fQl6tAY93cBV9/E5AjKtic/KpsYLSSU3BV/ivfUgHEb/UavX+wzGeBmZimrjSTZ0
8DUlpeJ9jBT5I+A6Y6u29HqKZFJuZo4AP8CXoRfhJrMfmn5Apu4zoB78raozKow9
JEERlL8SREXHIAREWbHO8Yk/RFkK9idpmQIh0/9FG0Ri76/Vyn1ayk44p7nzjTlZ
thcHGhvxsPEPFI+FWehI
=Lqnr
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-12-05 18:04 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 [this message]
2012-12-05 19:41 ` Dan Mick
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=50BF8CB8.5060708@ubuntu.com \
--to=james.page@ubuntu.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.