0.55 init script Issue?

0.55 init script Issue?

[Mike Dawson]

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

Re: 0.55 init script Issue?

[Franck Marchand]

Hi,

Since I upgraded from 0.54 to 0.55. I got some issues but It was my
configuration which was not "perfect". Anyways ... now when mds starts
it stays up for less than one minute and crashes. So I can't use
cephfs of my cluster.

I use  ubuntu precise packages on my cluster.

Anyone had the same problem ?

Franck

Re: 0.55 init script Issue?

[James Page]

-----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-----

Re: 0.55 init script Issue?

[Dan Mick]

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

Re: 0.55 init script Issue?

[David Zafman]

Keep in mind that some of the init.d stuff doesn't work with a ceph-deploy installed system.  Not clear to me if we need to fix ceph-deploy or for those type of setups only upstart should be used/available.

David

On Dec 5, 2012, at 11:41 AM, Dan Mick <dan.mick@inktank.com> wrote:

> 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
> --
> 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

Re: 0.55 init script Issue?

[James Page]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 05/12/12 19:41, Dan Mick wrote:
> 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.

Maybe it might be better if the ceph init script and the ceph upstart
configuration did not namespace clash; how about shifting the name of
the ceph upstart configuration to ceph-all?



- -- 
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/

iQIcBAEBCAAGBQJQv6vlAAoJEL/srsug59jDFO8P/jtC9TFAWLuFJoS/RC5nEwdO
x4OEdwYbRgE6ac5GK8ufMuqfonOVzDZ0jGxWzDrLSPQ3Ekow+E3wZFSgQN1ujhDT
0QeuAqseyMO++3Foe3HlcSAtp2IGr1VkgyLVNrnkn+rK/C8UOQnISeCvT30WFTEJ
xpr+DSiv2ZjH6fogb+p+fK7lD9anywR92pM65jNpPRnMaBZ49Rjbz8Xf3+yw8EHH
DkOvFjPnIw8pWc0FPfgbFOZNksOQ+UoIhsJJ2I5fVfLhsdcNjC+ETePi0W4VU7mL
FZLaUlGxgeDLCvgjXZ8fQ9T0sNJuYQ7H/4A0uLWnf3uNVMsE5MLff4msgAuotxle
l6w0lC+GzlHiRe6XRMgHwKq/Ifs/oZPgdGh5V6+zOERrZrl1+Z1EiD2MQkVzxk/M
7+06V/GlKLfv/hqrGOr1JtFI3AY+p+DJttq4+UN5HmxIFeaS19rSJxBxc7TqliH9
SiaoyhC6IBm8duEYHyuHfjnVksMNA/SOD4xyxGj/KLAS9IwvQhvOnaHfpQgMR7Bl
6zRyE+kisT3aC1UyvRiWCAg+8TzhQN46oMpE1JZQTJsbW2dtdXI/Jl8vDk+I8hX2
Qola8AzSHc80tp3p51PN+83V3iqHKvXeK8G36FnJm+tKufDPVe3WnE9ig5emRDez
it86WnE+jBLtA8QlZRm8
=XIJq
-----END PGP SIGNATURE-----

Re: 0.55 init script Issue?

[Gregory Farnum]

On Wed, Dec 5, 2012 at 12:17 PM, James Page <james.page@ubuntu.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 05/12/12 19:41, Dan Mick wrote:
>> 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.
>
> Maybe it might be better if the ceph init script and the ceph upstart
> configuration did not namespace clash; how about shifting the name of
> the ceph upstart configuration to ceph-all?

Yeah, this or something very similar is definitely the correct
solution. Sage recently added the "ceph" upstart job, and we didn't
put it through sufficient verification prior to release in order to
notice this issue. Users who aren't using upstart (I expect that's all
of them) should just delete the job after running the package install.
We'll certainly sort this out prior to the next release; I'm not sure
if we want to roll a v0.55.1 right away or not.
-Greg

Re: 0.55 init script Issue?

[Sage Weil]

On Wed, 5 Dec 2012, Gregory Farnum wrote:
> On Wed, Dec 5, 2012 at 12:17 PM, James Page <james.page@ubuntu.com> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > On 05/12/12 19:41, Dan Mick wrote:
> >> 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.
> >
> > Maybe it might be better if the ceph init script and the ceph upstart
> > configuration did not namespace clash; how about shifting the name of
> > the ceph upstart configuration to ceph-all?
> 
> Yeah, this or something very similar is definitely the correct
> solution. Sage recently added the "ceph" upstart job, and we didn't
> put it through sufficient verification prior to release in order to
> notice this issue. Users who aren't using upstart (I expect that's all
> of them) should just delete the job after running the package install.
> We'll certainly sort this out prior to the next release; I'm not sure
> if we want to roll a v0.55.1 right away or not.

Let's push it to the testing branch, but make sure any other fixes are 
there before rolling a .1.. maybe tomorrow?

Thanks!
sage


> -Greg
> --
> 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
> 
> 

Re: 0.55 init script Issue?

[Matthew Via]

[-- Attachment #1: Type: text/plain, Size: 2716 bytes --]

On the subject of init script problems, for the 0.55 Ceph release on EL6, 
the init script has what looks like a typo on line 280, and in 
/sbin/mkcephfs on line 328:
  fs_type = "btrfs"

As far as I know, shell variable assignments must have not have a space
between variable and the = -- the init script and mkcephfs will not run
as is.  It'd be nice to have this fixed in .55.1 if released.

Thanks, Matthew

On 16:11 Wed 05 Dec     , Sage Weil wrote:
> On Wed, 5 Dec 2012, Gregory Farnum wrote:
> > On Wed, Dec 5, 2012 at 12:17 PM, James Page <james.page@ubuntu.com> wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA256
> > >
> > > On 05/12/12 19:41, Dan Mick wrote:
> > >> 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.
> > >
> > > Maybe it might be better if the ceph init script and the ceph upstart
> > > configuration did not namespace clash; how about shifting the name of
> > > the ceph upstart configuration to ceph-all?
> > 
> > Yeah, this or something very similar is definitely the correct
> > solution. Sage recently added the "ceph" upstart job, and we didn't
> > put it through sufficient verification prior to release in order to
> > notice this issue. Users who aren't using upstart (I expect that's all
> > of them) should just delete the job after running the package install.
> > We'll certainly sort this out prior to the next release; I'm not sure
> > if we want to roll a v0.55.1 right away or not.
> 
> Let's push it to the testing branch, but make sure any other fixes are 
> there before rolling a .1.. maybe tomorrow?
> 
> Thanks!
> sage
> 
> 
> > -Greg
> > --
> > 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
> > 
> > 
> --
> 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

[-- Attachment #2: Type: application/pgp-signature, Size: 488 bytes --]

Re: 0.55 init script Issue?

[Sage Weil]

On Wed, 5 Dec 2012, Matthew Via wrote:
> On the subject of init script problems, for the 0.55 Ceph release on EL6, 
> the init script has what looks like a typo on line 280, and in 
> /sbin/mkcephfs on line 328:
>   fs_type = "btrfs"
> 
> As far as I know, shell variable assignments must have not have a space
> between variable and the = -- the init script and mkcephfs will not run
> as is.  It'd be nice to have this fixed in .55.1 if released.

Definitely, thanks!  This is pushed to the testing branch.  We should be 
able to build a 0.55.1 tomorrow.

Thanks!
sage



> 
> Thanks, Matthew
> 
> On 16:11 Wed 05 Dec     , Sage Weil wrote:
> > On Wed, 5 Dec 2012, Gregory Farnum wrote:
> > > On Wed, Dec 5, 2012 at 12:17 PM, James Page <james.page@ubuntu.com> wrote:
> > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > Hash: SHA256
> > > >
> > > > On 05/12/12 19:41, Dan Mick wrote:
> > > >> 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.
> > > >
> > > > Maybe it might be better if the ceph init script and the ceph upstart
> > > > configuration did not namespace clash; how about shifting the name of
> > > > the ceph upstart configuration to ceph-all?
> > > 
> > > Yeah, this or something very similar is definitely the correct
> > > solution. Sage recently added the "ceph" upstart job, and we didn't
> > > put it through sufficient verification prior to release in order to
> > > notice this issue. Users who aren't using upstart (I expect that's all
> > > of them) should just delete the job after running the package install.
> > > We'll certainly sort this out prior to the next release; I'm not sure
> > > if we want to roll a v0.55.1 right away or not.
> > 
> > Let's push it to the testing branch, but make sure any other fixes are 
> > there before rolling a .1.. maybe tomorrow?
> > 
> > Thanks!
> > sage
> > 
> > 
> > > -Greg
> > > --
> > > 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
> > > 
> > > 
> > --
> > 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
> 

Re: 0.55 init script Issue?

[Sage Weil]

On Wed, 5 Dec 2012, Sage Weil wrote:
> On Wed, 5 Dec 2012, Gregory Farnum wrote:
> > On Wed, Dec 5, 2012 at 12:17 PM, James Page <james.page@ubuntu.com> wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA256
> > >
> > > On 05/12/12 19:41, Dan Mick wrote:
> > >> 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.
> > >
> > > Maybe it might be better if the ceph init script and the ceph upstart
> > > configuration did not namespace clash; how about shifting the name of
> > > the ceph upstart configuration to ceph-all?
> > 
> > Yeah, this or something very similar is definitely the correct
> > solution. Sage recently added the "ceph" upstart job, and we didn't
> > put it through sufficient verification prior to release in order to
> > notice this issue. Users who aren't using upstart (I expect that's all
> > of them) should just delete the job after running the package install.
> > We'll certainly sort this out prior to the next release; I'm not sure
> > if we want to roll a v0.55.1 right away or not.
> 
> Let's push it to the testing branch, but make sure any other fixes are 
> there before rolling a .1.. maybe tomorrow?

I've pushed this to the testing branch.  If someone wants to verify the 
packages built at 

	http://gitbuilder.ceph.com/ceph-deb-precise-x86_64-basic/ref/testing/

are fixed, that would be fabulous!

sage


> Thanks!
> sage
> 
> 
> > -Greg
> > --
> > 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
> > 
> > 
> --
> 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
> 
> 

Re: 0.55 init script Issue?

[Dan Mick]

It did not delete the previously-installed /etc/init/ceph.conf; I'm 
guessing we need a postinstall fragment to do that fixup?

On 12/06/2012 05:35 AM, Sage Weil wrote:
> On Wed, 5 Dec 2012, Sage Weil wrote:
>> On Wed, 5 Dec 2012, Gregory Farnum wrote:
>>> On Wed, Dec 5, 2012 at 12:17 PM, James Page <james.page@ubuntu.com> wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA256
>>>>
>>>> On 05/12/12 19:41, Dan Mick wrote:
>>>>> 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.
>>>>
>>>> Maybe it might be better if the ceph init script and the ceph upstart
>>>> configuration did not namespace clash; how about shifting the name of
>>>> the ceph upstart configuration to ceph-all?
>>>
>>> Yeah, this or something very similar is definitely the correct
>>> solution. Sage recently added the "ceph" upstart job, and we didn't
>>> put it through sufficient verification prior to release in order to
>>> notice this issue. Users who aren't using upstart (I expect that's all
>>> of them) should just delete the job after running the package install.
>>> We'll certainly sort this out prior to the next release; I'm not sure
>>> if we want to roll a v0.55.1 right away or not.
>>
>> Let's push it to the testing branch, but make sure any other fixes are
>> there before rolling a .1.. maybe tomorrow?
>
> I've pushed this to the testing branch.  If someone wants to verify the
> packages built at
>
> 	http://gitbuilder.ceph.com/ceph-deb-precise-x86_64-basic/ref/testing/
>
> are fixed, that would be fabulous!
>
> sage
>
>
>> Thanks!
>> sage
>>
>>
>>> -Greg
>>> --
>>> 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
>>>
>>>
>> --
>> 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
>>
>>

Re: 0.55 init script Issue?

[James Page]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 06/12/12 13:35, Sage Weil wrote:
>>> Yeah, this or something very similar is definitely the correct
>>>>> solution. Sage recently added the "ceph" upstart job, and
>>>>> we didn't put it through sufficient verification prior to
>>>>> release in order to notice this issue. Users who aren't
>>>>> using upstart (I expect that's all of them) should just
>>>>> delete the job after running the package install. We'll
>>>>> certainly sort this out prior to the next release; I'm not
>>>>> sure if we want to roll a v0.55.1 right away or not.
>>> 
>>> Let's push it to the testing branch, but make sure any other
>>> fixes are there before rolling a .1.. maybe tomorrow?
> I've pushed this to the testing branch.  If someone wants to verify
> the packages built at
> 
> http://gitbuilder.ceph.com/ceph-deb-precise-x86_64-basic/ref/testing/
>
>  are fixed, that would be fabulous!

I think the radosgw init script and upstart configuration are going to
conflict in a similar way to the ceph one.

I've been working on integrating the upstart configurations into the
Ubuntu distro packaging of ceph; it is possible to install multiple
upstart configurations into single binary packages using dh_installinit:

    dh_installinit --no-start
    # Install upstart configurations using dh_installinit
    for conf in `ls -1 src/upstart/ceph-*.conf | grep -v mds`; do \
        name=`basename $$conf | cut -d . -f 1`; \
        cp $$conf debian/ceph.$$name.upstart; \
        dh_installinit -pceph --upstart-only --no-start --name=$$name; \
    done
    for conf in `ls -1 src/upstart/ceph-mds*.conf`; do \
        name=`basename $$conf | cut -d . -f 1`; \
        cp $$conf debian/ceph-mds.$$name.upstart; \
        dh_installinit -pceph-mds --upstart-only --no-start
- --name=$$name; \
    done
    for conf in `ls -1 src/upstart/radosgw*.conf`; do \
        name=`basename $$conf | cut -d . -f 1`; \
        cp $$conf debian/radosgw.$$name.upstart; \
        dh_installinit -pradosgw --upstart-only --no-start
- --name=$$name; \
    done


- -- 
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/

iQIcBAEBCAAGBQJQxafNAAoJEL/srsug59jDGloP/0NK8RAFLLGcwHBOGqPSiOSr
e61NAus6zM0gRHdY0GxPLLzh8XfcoJtpiOdJE2PeC0YbNX7SRLnlHBc3uh3nRv0+
LF5RfzN0MASpk5miCVIpZCNhRVbg+tte1k3tEbZEgwsFavmhXdXzL7bwaKDKVuRp
Y8/XENu6qF2tSt1A1P5ABOqetjrZi78Z6bNSBS20N2PIZHAXwdb2MdFPKO600n2w
jVPjXh/nfCuPpmehE+ZVP/1y/7jLvtgYTIppg8bHNG0X4TI6aarHh3fiypti+UNu
y/fQvx48ktkCtaF7nfoIx+Kr1qWO9xcuHYZy/35a9woJIyBWGTHS4yT/UYG202gM
JjelhXu0BM4WrmTf9bdFo2iK55MNtKOEPOAjmy4FZbVtBc1iUNtyBOJGDSv5Ls+0
uwDImZbg1W8VqtnioQRrhNUelgV3SLYoWfzOjAsHMoS25/WsLwvnRm8XExD2223l
SQOfcwXjTDldRRc04wohr2Rc1/vuTEFGt94cLVf67UutEDgN4T8LK2Za+RV/D6/e
GmrofhClKQUIeHm3WaD3P2oJJZIG+MOeNG0+Y1JB4aOgL+ZUtuLTQo3xa8fhvhDA
mRcYrCvUwS+k70OcSh2GTpt9y+1mnk+qAB4JR3SclTVOUUh4i9KtYa+1F5+8NWwU
DsfC6VS1vdgPnBEcKw0d
=5jkr
-----END PGP SIGNATURE-----