Mailing List Archive: Linux-HA: Pacemaker

Upstart resources

1 2

View All

Index | Next | Previous | View Threaded

andrew at beekhof

Feb 27, 2012, 4:14 AM

Post #26 of 32 (411 views)
Permalink

Re: Upstart resources [In reply to]

On Mon, Feb 27, 2012 at 11:07 PM, Ante Karamatic <ivoks [at] ubuntu> wrote:
> On 27.02.2012 11:37, Andrew Beekhof wrote:
>
>> I know, but whatever the admin specifies should over-rule the package
>> maintainer's defaults.
>
> I agree and that's how upstart works.
>
>> From what you're saying, this is not possible with Upstart. Which is bad.
>
> I said it's an option, not that it's not possible :) /etc/init/ssh.conf
> defines ssh service/job. /etc/init/ssh.override is an override file that
> overrides everything from .conf. There is a catch, and that's that
> there's no 'norespawn' option.
>
> So, if a package maintainer defined 'respawn' in .conf, you can't really
> disable it without removing 'respawn' from job file. On the other hand,
> you can override default respawn behavior (ssh service):
>
> echo "respawn limit 1 1" >> /etc/init/ssh.override

Yep, basically what systemd wanted us to do.
The problem is that if you take that service away from the cluster
(permanently or otherwise), the override to make pacemaker happy
shouldn't be applied.

So apart from it being horribly ugly, it doesn't give the right behaviour.
Only when some higher level daemon starts the service and knows
otherwise should norespawn be active.

>
> That would stop respawning if service fails more than once within the
> second.
>
> I'd say that non-existing 'norespawn' option is a bug.
>
> Best regards
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

andrew at beekhof

Feb 28, 2012, 11:21 PM

Post #27 of 32 (391 views)
Permalink

Re: Upstart resources [In reply to]

2012/2/27 Ante KaramatiÄ‡ <ante.karamatic [at] canonical>:
> On 27.02.2012 12:27, Florian Haas wrote:
>
>> Alas, to the best of my knowledge the only way to change a specific
>> job's respawn policy is by modifying its job definition. Likewise,
>> that's the only way to enable or disable starting on system boot. So
>> there is a way to overrule the package maintainer's default -- hacking
>> the job definition.
>
> I've explained '(no)respawn' in the other mail. Manual starting/stopping
> is done by:
>
> echo 'manual' >> /etc/init/${service}.override
>
> That's all you need to forbid automatic starting or stopping the service.
>

Not really appropriate for a cluster daemon to be doing though IMHO

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

florian at hastexo

Feb 28, 2012, 11:36 PM

Post #28 of 32 (386 views)
Permalink

Re: Upstart resources [In reply to]

2012/2/27 Ante KaramatiÄ‡ <ante.karamatic [at] canonical>:
> On 27.02.2012 12:27, Florian Haas wrote:
>
>> Alas, to the best of my knowledge the only way to change a specific
>> job's respawn policy is by modifying its job definition. Likewise,
>> that's the only way to enable or disable starting on system boot. So
>> there is a way to overrule the package maintainer's default -- hacking
>> the job definition.
>
> I've explained '(no)respawn' in the other mail. Manual starting/stopping
> is done by:
>
> echo 'manual' >> /etc/init/${service}.override
>
> That's all you need to forbid automatic starting or stopping the service.

Oh thanks! I didn't know that, much to my dismay.

Cheers,
Florian

--
Need help with High Availability?
http://www.hastexo.com/now

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

florian at hastexo

Feb 28, 2012, 11:38 PM

Post #29 of 32 (386 views)
Permalink

Re: Upstart resources [In reply to]

On Wed, Feb 29, 2012 at 8:21 AM, Andrew Beekhof <andrew [at] beekhof> wrote:
> 2012/2/27 Ante KaramatiÄ‡ <ante.karamatic [at] canonical>:
>> On 27.02.2012 12:27, Florian Haas wrote:
>>
>>> Alas, to the best of my knowledge the only way to change a specific
>>> job's respawn policy is by modifying its job definition. Likewise,
>>> that's the only way to enable or disable starting on system boot. So
>>> there is a way to overrule the package maintainer's default -- hacking
>>> the job definition.
>>
>> I've explained '(no)respawn' in the other mail. Manual starting/stopping
>> is done by:
>>
>> echo 'manual' >> /etc/init/${service}.override
>>
>> That's all you need to forbid automatic starting or stopping the service.
>>
>
> Not really appropriate for a cluster daemon to be doing though IMHO

Of course it wouldn't be the cluster daemon doing this but the admin,
but how is that so fundamentally worse
compared to doing, say "chkconfig mysql off"?

Having to keep a service from starting a daemon on boot is something
that is fairly standard in Pacemaker environments these days.

Florian

--
Need help with High Availability?
http://www.hastexo.com/now

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

andrew at beekhof

Feb 28, 2012, 11:49 PM

Post #30 of 32 (387 views)
Permalink

Re: Upstart resources [In reply to]

On Wed, Feb 29, 2012 at 6:38 PM, Florian Haas <florian [at] hastexo> wrote:
> On Wed, Feb 29, 2012 at 8:21 AM, Andrew Beekhof <andrew [at] beekhof> wrote:
>> 2012/2/27 Ante KaramatiÄ‡ <ante.karamatic [at] canonical>:
>>> On 27.02.2012 12:27, Florian Haas wrote:
>>>
>>>> Alas, to the best of my knowledge the only way to change a specific
>>>> job's respawn policy is by modifying its job definition. Likewise,
>>>> that's the only way to enable or disable starting on system boot. So
>>>> there is a way to overrule the package maintainer's default -- hacking
>>>> the job definition.
>>>
>>> I've explained '(no)respawn' in the other mail. Manual starting/stopping
>>> is done by:
>>>
>>> echo 'manual' >> /etc/init/${service}.override
>>>
>>> That's all you need to forbid automatic starting or stopping the service.
>>>
>>
>> Not really appropriate for a cluster daemon to be doing though IMHO
>
> Of course it wouldn't be the cluster daemon doing this but the admin,

I think the number of people that would think to do this after adding
an upstart service to the cluster approaches zero.

> but how is that so fundamentally worse
> compared to doing, say "chkconfig mysql off"?
>
> Having to keep a service from starting a daemon on boot is something
> that is fairly standard in Pacemaker environments these days.

But this isn't "start at boot", this is preventing respawn after
pacemaker starts it.

>
> Florian
>
> --
> Need help with High Availability?
> http://www.hastexo.com/now
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

daff at pseudoterminal

Feb 29, 2012, 10:38 AM

Post #31 of 32 (384 views)
Permalink

Re: Upstart resources [In reply to]

On 27/02/12 13:09, Ante KaramatiÄ‡ wrote:
> On 27.02.2012 12:27, Florian Haas wrote:
>
>> Alas, to the best of my knowledge the only way to change a specific
>> job's respawn policy is by modifying its job definition. Likewise,
>> that's the only way to enable or disable starting on system boot. So
>> there is a way to overrule the package maintainer's default -- hacking
>> the job definition.
>
> I've explained '(no)respawn' in the other mail. Manual starting/stopping
> is done by:
>
> echo 'manual' >> /etc/init/${service}.override
>
> That's all you need to forbid automatic starting or stopping the service.

Does this work in Ubuntu 10.04? As far as I remember the discussion on
this problem in Launchpad, the consensus was something like "too late
for Lucid".

Andreas

Attachments:

signature.asc (0.26 KB)

jsmith at argotec

Mar 12, 2012, 12:13 PM

Post #32 of 32 (365 views)
Permalink

Re: Upstart resources [In reply to]

----- Original Message -----
> From: "Andreas Ntaflos" <daff [at] pseudoterminal>
> To: "The Pacemaker cluster resource manager" <pacemaker [at] oss>
> Sent: Wednesday, February 29, 2012 1:38:08 PM
> Subject: Re: [Pacemaker] Upstart resources
>
> On 27/02/12 13:09, Ante KaramatiÄ‡ wrote:
> > On 27.02.2012 12:27, Florian Haas wrote:
> >
> >> Alas, to the best of my knowledge the only way to change a
> >> specific
> >> job's respawn policy is by modifying its job definition. Likewise,
> >> that's the only way to enable or disable starting on system boot.
> >> So
> >> there is a way to overrule the package maintainer's default --
> >> hacking
> >> the job definition.
> >
> > I've explained '(no)respawn' in the other mail. Manual
> > starting/stopping
> > is done by:
> >
> > echo 'manual' >> /etc/init/${service}.override
> >
> > That's all you need to forbid automatic starting or stopping the
> > service.
>
> Does this work in Ubuntu 10.04? As far as I remember the discussion
> on
> this problem in Launchpad, the consensus was something like "too late
> for Lucid".

From what I read (upstart.ubuntu.com/cookbook) when I needed to disable Upstart jobs in 10.04:

With version 0.6.7 - rename job config to not end with ".conf" or comment "start on" line with #
^^^ this is a little misleading since 10.04 (Lucid) has v0.6.5-8 but the above seems to work fine

The ".override" file option described above is listed as available since v1.3 (this option seems much clearer/cleaner/obvious). Version 1.3 isn't released in Ubuntu until 11.10 (Oneiric) according to packages.ubuntu.com

Unless I'm missing something...

Jake

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

1 2

View All

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads