On Fri, Jul 30, 2010 at 4:47 PM, Rick Day <r...@daybunch.com> wrote: > Can you tell me what tool is being used or exactly what is being checked > for?
Best to open up the script and have a look. I've not used it personally. > The problem is NFS is not running on node 2 when I bring it up so > if I knew what Pacemaker (nfs_monitor_0) is checking for I might be able > to solve my issue. > > Thanks, > Rick > >> Failed actions: >> > ? ?nfs_monitor_0 (node=SPDLFILE01, call=14, rc=5, status=complete): not >> > install >> > ed >> >> [snip] >> >> Some tool needed to determine the state of the resource is not available. >> So we assume the worst (that it is running). >> > > > On Fri, 2010-07-30 at 06:29 +0000, pacemaker-requ...@oss.clusterlabs.org > wrote: >> Send Pacemaker mailing list submissions to >> pacemaker@oss.clusterlabs.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> or, via email, send a message with subject or body 'help' to >> pacemaker-requ...@oss.clusterlabs.org >> >> You can reach the person managing the list at >> pacemaker-ow...@oss.clusterlabs.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of Pacemaker digest..." >> >> >> Today's Topics: >> >> 1. LRM operation monitor gives unknown error (Cory Coager) >> 2. overwrite quorum decision (Bernd Schubert) >> 3. Re: overwrite quorum decision (Andrew Beekhof) >> 4. Re: LRM operation monitor gives unknown error (Andrew Beekhof) >> 5. Re: Two node lsb:nfs failing starting second node (Andrew Beekhof) >> 6. Re: [PING] ping, pingd and CIB updates, pick your poison :) >> (Andrew Beekhof) >> 7. Re: [PING] ping, pingd and CIB updates, pick your poison :) >> (Andrew Beekhof) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 29 Jul 2010 09:56:59 -0400 >> From: Cory Coager <ccoa...@davisvision.com> >> To: pacemaker@oss.clusterlabs.org >> Subject: [Pacemaker] LRM operation monitor gives unknown error >> Message-ID: >> >> <22676_1280411819_4c5188ab_22676_7150_1_4c5188ab.7090...@davisvision.com> >> >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed >> >> Hi all, first time setup here. I'm having an issue with one specific >> service, bind. The service actually starts and stops fine through >> pacemaker but for whatever reason the monitor event always gives an >> unknown error for this service on both nodes. How can I fix this? >> >> I am running Ubuntu 10.04 x64. I'm trying to cluster drbd, nagios, bind >> and apache. My setup seems to work, services stop and start fine, I can >> failover fine just have this one small problem. >> >> >> crm_mon shows: >> bind_monitor_0 (node=node2, call=55, rc=1, status=complete): unknown error >> >> logs show: >> crmd: [1398]: info: process_lrm_event: LRM operation bind_monitor_0 >> (call=3, rc=1, cib-update=8, confirmed=true) unknown error >> >> config: >> node $id="2890c964-4ae7-4707-8f80-d66f682e286e" node1 >> node $id="4b7f43c4-d04f-4f92-ba60-be8a3abcbcd0" node2 >> primitive apache lsb:apache2 >> primitive bind lsb:bind9 >> primitive drbd0 ocf:heartbeat:drbd \ >> params drbd_resource="nagios" ignore_deprecation="true" \ >> op monitor interval="29s" role="Master" timeout="10s" \ >> op monitor interval="30s" role="Slave" timeout="10s" >> primitive fs_nagios ocf:heartbeat:Filesystem \ >> params fstype="ext4" directory="/mnt/nagios" device="/dev/drbd0" >> primitive nagios lsb:nagios3 >> group rg_nagios fs_nagios bind apache nagios \ >> meta target-role="Started" >> ms ms-drbd0 drbd0 \ >> meta clone-max="2" notify="true" globally-unique="false" >> target-role="Started" is-managed="true" >> location cli-prefer-rg_nagios rg_nagios \ >> rule $id="cli-prefer-rule-rg_nagios" inf: #uname eq node1 >> colocation rg_nagios-on-ms-drbd0 inf: rg_nagios ms-drbd0:Master >> order ms-drbd0-before-rg_nagios inf: ms-drbd0:promote rg_nagios:start >> property $id="cib-bootstrap-options" \ >> dc-version="1.0.8-042548a451fce8400660f6031f4da6f0223dd5dd" \ >> cluster-infrastructure="Heartbeat" \ >> stonith-enabled="false" \ >> last-lrm-refresh="1280350700" >> >> >> ~Cory Coager >> >> >> >> ------------------------------------------------------------------------ >> The information contained in this communication is intended >> only for the use of the recipient(s) named above. It may >> contain information that is privileged or confidential, and >> may be protected by State and/or Federal Regulations. If >> the reader of this message is not the intended recipient, >> you are hereby notified that any dissemination, >> distribution, or copying of this communication, or any of >> its contents, is strictly prohibited. If you have received >> this communication in error, please return it to the sender >> immediately and delete the original message and any copy >> of it from your computer system. If you have any questions >> concerning this message, please contact the sender. >> ------------------------------------------------------------------------ >> >> >> >> >> ------------------------------ >> >> Message: 2 >> Date: Thu, 29 Jul 2010 20:26:40 +0200 >> From: Bernd Schubert <bernd.schub...@fastmail.fm> >> To: pacemaker@oss.clusterlabs.org >> Subject: [Pacemaker] overwrite quorum decision >> Message-ID: <201007292026.41116.bernd.schub...@fastmail.fm> >> Content-Type: text/plain; charset="us-ascii" >> >> Hello all, >> >> is there a way to overwrite the quorum policy decision, lets say to >> "no quorum with n/2 - 1 nodes" or "no quorum if no access to any other node"? >> >> >> Thanks, >> Bernd >> >> >> >> >> >> ------------------------------ >> >> Message: 3 >> Date: Fri, 30 Jul 2010 08:19:05 +0200 >> From: Andrew Beekhof <and...@beekhof.net> >> To: The Pacemaker cluster resource manager >> <pacemaker@oss.clusterlabs.org> >> Subject: Re: [Pacemaker] overwrite quorum decision >> Message-ID: >> <aanlktinakplvame9xvyxqghkajmbt4xhkynfehagq...@mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> On Thu, Jul 29, 2010 at 8:26 PM, Bernd Schubert >> <bernd.schub...@fastmail.fm> wrote: >> > Hello all, >> > >> > is there a way to overwrite the quorum policy decision, lets say to >> > "no quorum with n/2 - 1 nodes" or "no quorum if no access to any other >> > node"? >> >> No. >> Quorum is defined as "n/2 + 1", if you don't have that many nodes, >> then you don't have quorum. Period. >> >> However, we do have a number of strategies for what to do when quorum is >> lost. >> Check out no-quorum-policy >> >> > >> > >> > Thanks, >> > Bernd >> > >> > >> > >> > _______________________________________________ >> > Pacemaker mailing list: Pacemaker@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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker >> > >> >> >> >> ------------------------------ >> >> Message: 4 >> Date: Fri, 30 Jul 2010 08:22:51 +0200 >> From: Andrew Beekhof <and...@beekhof.net> >> To: The Pacemaker cluster resource manager >> <pacemaker@oss.clusterlabs.org> >> Subject: Re: [Pacemaker] LRM operation monitor gives unknown error >> Message-ID: >> <aanlktikmu5pkxd1jnzow18afndimfa+zg37wjgqar...@mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> On Thu, Jul 29, 2010 at 3:56 PM, Cory Coager <ccoa...@davisvision.com> wrote: >> > Hi all, first time setup here. ?I'm having an issue with one specific >> > service, bind. ?The service actually starts and stops fine through >> > pacemaker >> > but for whatever reason the monitor event always gives an unknown error for >> > this service on both nodes. ?How can I fix this? >> >> Looks like your init scripts are not LSB compliant. >> >> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/ap-lsb.html >> >> > >> > I am running Ubuntu 10.04 x64. ?I'm trying to cluster drbd, nagios, bind >> > and >> > apache. ?My setup seems to work, services stop and start fine, I can >> > failover fine just have this one small problem. >> > >> > >> > crm_mon shows: >> > bind_monitor_0 (node=node2, call=55, rc=1, status=complete): unknown error >> > >> > logs show: >> > crmd: [1398]: info: process_lrm_event: LRM operation bind_monitor_0 >> > (call=3, >> > rc=1, cib-update=8, confirmed=true) unknown error >> > >> > config: >> > node $id="2890c964-4ae7-4707-8f80-d66f682e286e" node1 >> > node $id="4b7f43c4-d04f-4f92-ba60-be8a3abcbcd0" node2 >> > primitive apache lsb:apache2 >> > primitive bind lsb:bind9 >> > primitive drbd0 ocf:heartbeat:drbd \ >> > ? ? ? ?params drbd_resource="nagios" ignore_deprecation="true" \ >> > ? ? ? ?op monitor interval="29s" role="Master" timeout="10s" \ >> > ? ? ? ?op monitor interval="30s" role="Slave" timeout="10s" >> > primitive fs_nagios ocf:heartbeat:Filesystem \ >> > ? ? ? ?params fstype="ext4" directory="/mnt/nagios" device="/dev/drbd0" >> > primitive nagios lsb:nagios3 >> > group rg_nagios fs_nagios bind apache nagios \ >> > ? ? ? ?meta target-role="Started" >> > ms ms-drbd0 drbd0 \ >> > ? ? ? ?meta clone-max="2" notify="true" globally-unique="false" >> > target-role="Started" is-managed="true" >> > location cli-prefer-rg_nagios rg_nagios \ >> > ? ? ? ?rule $id="cli-prefer-rule-rg_nagios" inf: #uname eq node1 >> > colocation rg_nagios-on-ms-drbd0 inf: rg_nagios ms-drbd0:Master >> > order ms-drbd0-before-rg_nagios inf: ms-drbd0:promote rg_nagios:start >> > property $id="cib-bootstrap-options" \ >> > ? ? ? ?dc-version="1.0.8-042548a451fce8400660f6031f4da6f0223dd5dd" \ >> > ? ? ? ?cluster-infrastructure="Heartbeat" \ >> > ? ? ? ?stonith-enabled="false" \ >> > ? ? ? ?last-lrm-refresh="1280350700" >> > >> > >> > ~Cory Coager >> > >> > >> > >> > ------------------------------------------------------------------------ >> > The information contained in this communication is intended >> > only for the use of the recipient(s) named above. It may >> > contain information that is privileged or confidential, and >> > may be protected by State and/or Federal Regulations. If >> > the reader of this message is not the intended recipient, >> > you are hereby notified that any dissemination, >> > distribution, or copying of this communication, or any of >> > its contents, is strictly prohibited. If you have received >> > this communication in error, please return it to the sender >> > immediately and delete the original message and any copy >> > of it from your computer system. If you have any questions >> > concerning this message, please contact the sender. >> > ------------------------------------------------------------------------ >> > >> > >> > _______________________________________________ >> > Pacemaker mailing list: Pacemaker@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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker >> > >> >> >> >> ------------------------------ >> >> Message: 5 >> Date: Fri, 30 Jul 2010 08:27:18 +0200 >> From: Andrew Beekhof <and...@beekhof.net> >> To: The Pacemaker cluster resource manager >> <pacemaker@oss.clusterlabs.org> >> Subject: Re: [Pacemaker] Two node lsb:nfs failing starting second node >> Message-ID: >> <aanlktimmok57umpq=w9da=ioo58hv5hgwxsbnjpbg...@mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> On Wed, Jul 28, 2010 at 12:48 PM, Rick Day <r...@daybunch.com> wrote: >> [snip] >> >> > Failed actions: >> > ? ?nfs_monitor_0 (node=SPDLFILE01, call=14, rc=5, status=complete): not >> > install >> > ed >> >> [snip] >> >> Some tool needed to determine the state of the resource is not available. >> So we assume the worst (that it is running). >> >> >> >> ------------------------------ >> >> Message: 6 >> Date: Fri, 30 Jul 2010 08:29:11 +0200 >> From: Andrew Beekhof <and...@beekhof.net> >> To: The Pacemaker cluster resource manager >> <pacemaker@oss.clusterlabs.org> >> Cc: pacema...@clusterlabs.org >> Subject: Re: [Pacemaker] [PING] ping, pingd and CIB updates, pick your >> poison :) >> Message-ID: >> <aanlktinizgtevda2pb45m8hsvabpgs22af_mnx5wz...@mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> On Wed, Jul 28, 2010 at 8:45 AM, Thomas Guthmann <tguthm...@iseek.com.au> >> wrote: >> > Hey, >> > >> > As much as I like pacemaker I hate these ping tests which don't update the >> > CIB. After reading a lot on the mailing list I see that people are still a >> > lot confused. So can one of the main developers give an example that should >> > work like "how to check your connectivity" ? (the wiki still talk about >> > pingd for instance). I don't know if my rules are "by the rule book" : >> > >> > primitive ping ocf:pacemaker:ping \ >> > ? ? ? ?params host_list="192.168.1.100" dampen="121" attempts="3" >> > debug="true" \ >> > ? ? ? ?op monitor interval="10s" timeout="20s" >> > >> > location rule-connectivity DB \ >> > ? ? ? ?rule $id="rule-ping" -inf: not_defined pingd or pingd number:lte 0 >> > >> > My problem is that the CIB is not updated when I lost connectivity even >> > with >> > pacemaker:ping instead of obsolete pacemaker:pingd (that I used before). I >> > upgraded from corosync/pacemaker 1.2.1/1.0.8 to the latest 1.2.5/1.0.9-11 >> > but I still have the problem. Indeed, if my gateway (or a fake IP I'm using >> > for tests) is down I can see that ping is working correctly but >> > attrd_updater does _NOT_ update the CIB. >> >> How long did you wait? >> >> dampen="121" means that attrd will wait just over 2 minutes before >> updating the CIB >> >> > But if I do attrd_updated -R it >> > updates the value. Note: I used one node only to reduce the variables >> > during >> > the tests so it's not something due to concurrency. See logs below. I can >> > provide a hb_report if necessary. >> > >> > Any ideas ? Bug or PEBKAC ? >> > >> > Cheers, >> > Thomas >> > >> > --- >> > >> > Jul 28 15:36:05 db1 attrd_updater: [5133]: info: Invoked: attrd_updater -n >> > pingd -v 1 -d 121 >> > Jul 28 15:36:17 db1 attrd_updater: [5150]: info: Invoked: attrd_updater -n >> > pingd -v 1 -d 121 >> > Jul 28 15:36:29 db1 attrd_updater: [5165]: info: Invoked: attrd_updater -n >> > pingd -v 1 -d 121 >> > Jul 28 15:36:47 db1 ping[5169]: WARNING: 192.168.1.100 is inactive: PING >> > 192.168.1.100 (192.168.1.100) 56(84) bytes of data.#012#012--- >> > 192.168.1.100 >> > ping statistics ---#0123 packets transmitted, 0 received, +2 errors, 100% >> > packet loss, time 1999ms#012, pipe 2 >> > Jul 28 15:36:47 db1 attrd_updater: [5189]: info: Invoked: attrd_updater -n >> > pingd -v 0 -d 121 >> > Jul 28 15:37:05 db1 ping[5196]: WARNING: 192.168.1.100 is inactive: PING >> > 192.168.1.100 (192.168.1.100) 56(84) bytes of data.#012#012--- >> > 192.168.1.100 >> > ping statistics ---#0123 packets transmitted, 0 received, +1 errors, 100% >> > packet loss, time 1999ms >> > Jul 28 15:37:05 db1 attrd_updater: [5212]: info: Invoked: attrd_updater -n >> > pingd -v 0 -d 121 >> > Jul 28 15:37:23 db1 ping[5218]: WARNING: 192.168.1.100 is inactive: PING >> > 192.168.1.100 (192.168.1.100) 56(84) bytes of data.#012#012--- >> > 192.168.1.100 >> > ping statistics ---#0123 packets transmitted, 0 received, +1 errors, 100% >> > packet loss, time 1999ms >> > ... >> > ..... >> > ....... >> > Jul 28 15:56:01 db1 ping[7803]: WARNING: 192.168.1.100 is inactive: PING >> > 192.168.1.100 (192.168.1.100) 56(84) bytes of data.#012#012--- >> > 192.168.1.100 >> > ping statistics ---#0123 packets transmitted, 0 received, +1 errors, 100% >> > packet loss, time 1999ms >> > Jul 28 15:56:01 db1 attrd_updater: [7819]: info: Invoked: attrd_updater -n >> > pingd -v 0 -d 121 >> > >> > [r...@db1:~]# cibadmin -Ql | grep nvpair.*ping >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-host_list" name="host_list" >> > value="192.168.1.100"/> >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-dampen" name="dampen" >> > value="121"/> >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-attempts" name="attempts" >> > value="3"/> >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-debug" name="debug" >> > value="true"/> >> > ? ? ? ? ?<nvpair id="status-db1.xxx-pingd" name="pingd" value="1"/> >> > >> > # attrd_updater -R >> > # cibadmin -Ql | grep nvpair.*ping >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-host_list" name="host_list" >> > value="192.168.1.100"/> >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-dampen" name="dampen" >> > value="121"/> >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-attempts" name="attempts" >> > value="3"/> >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-debug" name="debug" >> > value="true"/> >> > ? ? ? ? ?<nvpair id="status-db2.xxx-pingd" name="pingd" value="0"/> >> > ? ? ? ? ?<nvpair id="status-db1.xxx-pingd" name="pingd" value="0"/> >> > >> > # >> > >> > _______________________________________________ >> > Pacemaker mailing list: Pacemaker@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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker >> > >> >> >> >> ------------------------------ >> >> Message: 7 >> Date: Fri, 30 Jul 2010 08:29:11 +0200 >> From: Andrew Beekhof <and...@beekhof.net> >> To: The Pacemaker cluster resource manager >> <pacemaker@oss.clusterlabs.org> >> Cc: pacema...@clusterlabs.org >> Subject: Re: [Pacemaker] [PING] ping, pingd and CIB updates, pick your >> poison :) >> Message-ID: >> <aanlktinizgtevda2pb45m8hsvabpgs22af_mnx5wz...@mail.gmail.com> >> Content-Type: text/plain; charset=ISO-8859-1 >> >> On Wed, Jul 28, 2010 at 8:45 AM, Thomas Guthmann <tguthm...@iseek.com.au> >> wrote: >> > Hey, >> > >> > As much as I like pacemaker I hate these ping tests which don't update the >> > CIB. After reading a lot on the mailing list I see that people are still a >> > lot confused. So can one of the main developers give an example that should >> > work like "how to check your connectivity" ? (the wiki still talk about >> > pingd for instance). I don't know if my rules are "by the rule book" : >> > >> > primitive ping ocf:pacemaker:ping \ >> > ? ? ? ?params host_list="192.168.1.100" dampen="121" attempts="3" >> > debug="true" \ >> > ? ? ? ?op monitor interval="10s" timeout="20s" >> > >> > location rule-connectivity DB \ >> > ? ? ? ?rule $id="rule-ping" -inf: not_defined pingd or pingd number:lte 0 >> > >> > My problem is that the CIB is not updated when I lost connectivity even >> > with >> > pacemaker:ping instead of obsolete pacemaker:pingd (that I used before). I >> > upgraded from corosync/pacemaker 1.2.1/1.0.8 to the latest 1.2.5/1.0.9-11 >> > but I still have the problem. Indeed, if my gateway (or a fake IP I'm using >> > for tests) is down I can see that ping is working correctly but >> > attrd_updater does _NOT_ update the CIB. >> >> How long did you wait? >> >> dampen="121" means that attrd will wait just over 2 minutes before >> updating the CIB >> >> > But if I do attrd_updated -R it >> > updates the value. Note: I used one node only to reduce the variables >> > during >> > the tests so it's not something due to concurrency. See logs below. I can >> > provide a hb_report if necessary. >> > >> > Any ideas ? Bug or PEBKAC ? >> > >> > Cheers, >> > Thomas >> > >> > --- >> > >> > Jul 28 15:36:05 db1 attrd_updater: [5133]: info: Invoked: attrd_updater -n >> > pingd -v 1 -d 121 >> > Jul 28 15:36:17 db1 attrd_updater: [5150]: info: Invoked: attrd_updater -n >> > pingd -v 1 -d 121 >> > Jul 28 15:36:29 db1 attrd_updater: [5165]: info: Invoked: attrd_updater -n >> > pingd -v 1 -d 121 >> > Jul 28 15:36:47 db1 ping[5169]: WARNING: 192.168.1.100 is inactive: PING >> > 192.168.1.100 (192.168.1.100) 56(84) bytes of data.#012#012--- >> > 192.168.1.100 >> > ping statistics ---#0123 packets transmitted, 0 received, +2 errors, 100% >> > packet loss, time 1999ms#012, pipe 2 >> > Jul 28 15:36:47 db1 attrd_updater: [5189]: info: Invoked: attrd_updater -n >> > pingd -v 0 -d 121 >> > Jul 28 15:37:05 db1 ping[5196]: WARNING: 192.168.1.100 is inactive: PING >> > 192.168.1.100 (192.168.1.100) 56(84) bytes of data.#012#012--- >> > 192.168.1.100 >> > ping statistics ---#0123 packets transmitted, 0 received, +1 errors, 100% >> > packet loss, time 1999ms >> > Jul 28 15:37:05 db1 attrd_updater: [5212]: info: Invoked: attrd_updater -n >> > pingd -v 0 -d 121 >> > Jul 28 15:37:23 db1 ping[5218]: WARNING: 192.168.1.100 is inactive: PING >> > 192.168.1.100 (192.168.1.100) 56(84) bytes of data.#012#012--- >> > 192.168.1.100 >> > ping statistics ---#0123 packets transmitted, 0 received, +1 errors, 100% >> > packet loss, time 1999ms >> > ... >> > ..... >> > ....... >> > Jul 28 15:56:01 db1 ping[7803]: WARNING: 192.168.1.100 is inactive: PING >> > 192.168.1.100 (192.168.1.100) 56(84) bytes of data.#012#012--- >> > 192.168.1.100 >> > ping statistics ---#0123 packets transmitted, 0 received, +1 errors, 100% >> > packet loss, time 1999ms >> > Jul 28 15:56:01 db1 attrd_updater: [7819]: info: Invoked: attrd_updater -n >> > pingd -v 0 -d 121 >> > >> > [r...@db1:~]# cibadmin -Ql | grep nvpair.*ping >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-host_list" name="host_list" >> > value="192.168.1.100"/> >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-dampen" name="dampen" >> > value="121"/> >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-attempts" name="attempts" >> > value="3"/> >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-debug" name="debug" >> > value="true"/> >> > ? ? ? ? ?<nvpair id="status-db1.xxx-pingd" name="pingd" value="1"/> >> > >> > # attrd_updater -R >> > # cibadmin -Ql | grep nvpair.*ping >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-host_list" name="host_list" >> > value="192.168.1.100"/> >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-dampen" name="dampen" >> > value="121"/> >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-attempts" name="attempts" >> > value="3"/> >> > ? ? ? ? ? ?<nvpair id="ping-instance_attributes-debug" name="debug" >> > value="true"/> >> > ? ? ? ? ?<nvpair id="status-db2.xxx-pingd" name="pingd" value="0"/> >> > ? ? ? ? ?<nvpair id="status-db1.xxx-pingd" name="pingd" value="0"/> >> > >> > # >> > >> > _______________________________________________ >> > Pacemaker mailing list: Pacemaker@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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker >> > >> >> >> >> ------------------------------ >> >> _______________________________________________ >> Pacemaker mailing list >> Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> >> End of Pacemaker Digest, Vol 32, Issue 56 >> ***************************************** >> > > > > _______________________________________________ > Pacemaker mailing list: Pacemaker@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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > _______________________________________________ Pacemaker mailing list: Pacemaker@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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
