[Pacemaker] Corosync with puppet

Hugo Deprez hugo.deprez at gmail.com
Tue Apr 3 06:42:27 EDT 2012


Well maybe I am deploying the configuration files in two times which causes
this, I'll try again soon.

I though that the init script should be able to notify the user when it
encounter that kind of situation and not staying like zombie process.
But I don't know if this can be manage easily.



On 2 April 2012 17:07, Lars Marowsky-Bree <lmb at suse.com> wrote:

> On 2012-04-02T11:34:23, Hugo Deprez <hugo.deprez at gmail.com> wrote:
> > I am using a puppet mode in order to manage my cluster.
> > I get a weird thing with the start & stop of the corosync daemon.
> >
> > When I modify the corosync.conf file, puppet is asked to restart / reload
> > corosync, but it failed on the command :
> >
> > start-stop-daemon --stop --quiet --retry forever/QUIT/1 --pidfile
> > /var/run/corosync.pid
> >
> > this command doesn't seems working when corosync is running.
> >
> > Any idea what's wrong here ?
> There is only a certain amount of changes you can make during a rolling
> upgrade/configuration change, which apparently is what you're doing
> here. i.e., you can't just change the network configuration on a single
> node. Doing something like changing the logging functions is feasible.
> But maybe you're doing something entirely different, because you've sort
> of failed to elaborate what you mean by "failed" and "doesn't seem to be
> working" - what's the error, and what are you trying to do?
> (What Florian said may be a good choice, i.e., detach and reattach after
> a configuration change, if you can live with the brief period of
> exposure.)
> Regards,
>    Lars
> --
> Architect Storage/HA
> SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix
> Imendörffer, HRB 21284 (AG Nürnberg)
> "Experience is the name everyone gives to their mistakes." -- Oscar Wilde
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120403/0eea360c/attachment-0003.html>

More information about the Pacemaker mailing list