Re: [Pacemaker] CMAN and Pacemaker

Thanks for the fix, its working on this cluster, I'll test it in the morning on few more boxes. systemd, what was wrong with system V startup scripts fil On 01/06/2012 01:13 AM, Andrew Beekhof wrote: > On Fri, Jan 6, 2012 at 4:20 PM, Fil wrote: >> :( weird huh > > It looks like they

Re: [Pacemaker] CMAN and Pacemaker

On Fri, Jan 6, 2012 at 4:20 PM, Fil wrote: > :(   weird huh It looks like they broke the handling of Type=forking What I especially loved about spending the afternoon debugging systemd is that there is zero information to go on. Pure guesswork. Switch over to Type=simple (and add -f to ExecS

Re: [Pacemaker] CMAN and Pacemaker

:( weird huh On 01/05/2012 11:54 PM, Andrew Beekhof wrote: > Urgh, I updated my system and now I get the same behaviour as you :-( > > On Fri, Jan 6, 2012 at 3:50 PM, Andrew Beekhof wrote: >> Did you disable cman's quorum timeout as per: >> >> http://www.clusterlabs.org/doc/en-US/Pacema

Re: [Pacemaker] CMAN and Pacemaker

yes On 01/05/2012 11:50 PM, Andrew Beekhof wrote: > Did you disable cman's quorum timeout as per: > > http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch08s02s02.html > ? > > On Thu, Jan 5, 2012 at 5:15 PM, Fil wrote: >> I am doing exactly the same thing: >> >> s

Re: [Pacemaker] CMAN and Pacemaker

Urgh, I updated my system and now I get the same behaviour as you :-( On Fri, Jan 6, 2012 at 3:50 PM, Andrew Beekhof wrote: > Did you disable cman's quorum timeout as per: >   > http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch08s02s02.html > ? > > On Thu, Jan 5, 2

Re: [Pacemaker] CMAN and Pacemaker

Did you disable cman's quorum timeout as per: http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_Scratch/ch08s02s02.html ? On Thu, Jan 5, 2012 at 5:15 PM, Fil wrote: > I am doing exactly the same thing: > > systemctl start cman.service > systemctl start pacemaker.service >

Re: [Pacemaker] [Problem]It is judged that a stopping resource is starting.

Hi Andrew, Thank you for comment. > But it should have a subsequent stop action which would set it back to > being inactive. > Did that not happen in this case? Yes. Log of "verify_stopped" is only recorded. The stop handling of resource that failed in probe was not carried out. --

Re: [Pacemaker] [Question] About the rotation of the pe-file.

Hi Andrew, Thank you for comments. > Could you try with: > > while(max >= 0 && sequence > max) { > The problem is not settled by this correction. The rotation is carried out with a value except 0. Best Regards, Hideo Yamauchi. --- On Fri, 2012/1/6, Andrew Beekhof wrote: > On Thu

Re: [Pacemaker] [Problem]It is judged that a stopping resource is starting.

On Tue, Dec 27, 2011 at 6:15 PM, wrote: > Hi All, > > When Pacemaker stops when there is the resource that failed in probe > processing, crmd outputs the following error message. > > >  Dec 28 00:07:36 rh57-1 crmd: [3206]: ERROR: verify_stopped: Resource X > was active at shutdown.  You may

Re: [Pacemaker] [Question] About the rotation of the pe-file.

On Thu, Jan 5, 2012 at 12:35 PM, wrote: > Hi All, > > Stored pe files usually begin with the zeroth. > However, when I make pe-input-series-max=2, the rotation is carried out > between 1 and 2, but is not performed with 0. > > Is it specifications that is not rotated with 0? > > I confirmed that

[Pacemaker] [PATCH 2/2] extra: add logrotate configuration snippet

--- extra/Makefile.am |2 +- extra/logrotate/Makefile.am |5 + extra/logrotate/pacemaker.conf.in |7 +++ 3 files changed, 13 insertions(+), 1 deletions(-) create mode 100644 extra/logrotate/Makefile.am create mode 100644 extra/logrotate/pacemaker.conf.in

[Pacemaker] [PATCH 1/2] extra: add rsyslog configuration snippet

--- configure.ac|4 extra/Makefile.am |2 +- extra/rsyslog/Makefile.am |5 + extra/rsyslog/pacemaker.conf.in | 39 +++ 4 files changed, 49 insertions(+), 1 deletions(-) create mode 100644 extra/rsys

[Pacemaker] [PATCH 0/2] rsyslog/logrotate configuration snippets

Hi everyone, apologies for sending patches to the user list -- my subscription request is still pending on pcmk-devel, so here goes. One of the most commonly voiced criticisms against Pacemaker is that it floods people's logs. And while I contend that the rather verbose logging that Pacemaker off

[Pacemaker] setup multimaster drbd with ocfs without o2cb and controld

Hello, I want setup follow: 2 servers with multimaster drbd and ocfs filesystem and mount it. *system: gentoo, 2.6.39, pacemaker-1.1.5 *Setup pacemaker: # misc settings property no-quorum-policy="ignore" property stonith-enabled="false" rsc_defaults resource-stickiness="200" # drbd setup prim

[Pacemaker] Large cluster

Hi all, I have a task that I think can logically be implemented using a pacemaker/corosync cluster with many nodes (e.g. 15) and maybe thousand or more resources. Most of the resources are parametrized processes controlled by a custom resource agent. The resources are added and removed dynamically

Re: [Pacemaker] ACL setup

On 01/05/12 13:23, Larry Brigman wrote: > On Wed, Jan 4, 2012 at 8:50 PM, Gao,Yan > wrote: > > > [root@sweng0096 ~]# crm configure property enable-acl=true > > [root@sweng0096 ~]# crm > > crm(live)# > > role monitor \ > >> read xpath:"/cib" >

Re: [Pacemaker] [ANNOUNCE] The Booth Cluster Ticket Manager - part of multi-site support in pacemaker

Hi Jiaju I tried booth and I found this error crm_ticket: invalid option -- 'n' Is that right -n option in pacemaker tools? I think -v option is right. then send the attated patch file. check the file please. Best Regards, Taihun (2011/12/05 15:18), Jiaju Zhang wrote: Hello everyone, I'm