Thank you very much for your reply sir. But I am sorry, I did not responded after i correct it. I managed it with the pingd resource it self. I am going to try it with ping resource also. i have already sownloaded the resource since it is not available out of box in my '2.99' version available in ubuntu repo.
Thanks and Regards, Jayakrishnan. L Visit: www.foralllinux.blogspot.com www.jayakrishnan.bravehost.com ---------- Forwarded message ---------- From: Andrew Beekhof <and...@beekhof.net> Date: Tue, Mar 23, 2010 at 10:44 PM Subject: Re: [Pacemaker] Problem with pingd. To: pacemaker@oss.clusterlabs.org On Tue, Mar 23, 2010 at 6:11 PM, Andrew Beekhof <and...@beekhof.net> wrote: > Hard to say with no logs. > > But you should be using ocf:pacemaker:ping instead of ocf:heartbeat:pingd > Oh, I see the logs now. But the part about using ocf:pacemaker:ping stands. pingd has proven to be quite troublesome and is easily replaced by your system's ping utility (which is mor elikely to be correct) and a small script (ie. ocf:pacemaker:ping). > > > On Tue, Feb 23, 2010 at 9:21 AM, Jayakrishnan > <jayakrishnan...@gmail.com>wrote: > >> Sir, >> Thank you for your advice but still my resources cant run anywhere as per >> crm_verify -LV. >> My slony resources are dependent of vir-ip. vir-ip can't start on any node >> as per this configuration... please check it.. >> ------------------------ >> >> node $id="3952b93e-786c-47d4-8c2f-a882e3d3d105" node2 \ >> attributes standby="off" >> node $id="ac87f697-5b44-4720-a8af-12a6f2295930" node1 \ >> attributes standby="off" >> primitive pgsql lsb:postgresql-8.4 \ >> meta target-role="Started" resource-stickness="inherited" \ >> op monitor interval="15s" timeout="25s" on-fail="standby" >> primitive pingd ocf:heartbeat:pingd \ >> params name="pingd" host-list="192.168.10.1 192.168.10.69" >> multiplier="100" \ >> >> op monitor interval="15s" timeout="5s" >> primitive slony-fail lsb:slony_failover \ >> meta target-role="Started" >> primitive slony-fail2 lsb:slony_failover2 \ >> meta target-role="Started" >> primitive vir-ip ocf:heartbeat:IPaddr2 \ >> params ip="192.168.10.10" nic="eth0" cidr_netmask="24" >> broadcast="192.168.10.255" \ >> op monitor interval="15s" timeout="25s" on-fail="standby" \ >> meta target-role="Started" >> clone pgclone pgsql \ >> meta notify="true" globally-unique="false" interleave="true" >> target-role="Started" >> clone pingclone pingd \ >> meta globally-unique="false" clone-max="2" clone-node-max="1" >> location vir-ip-with-pingd vir-ip \ >> rule $id="vir-ip-with-pingd-rule" -inf: not_defined pingd or pingd >> number:lte 0 >> >> colocation ip-with-slony inf: slony-fail vir-ip >> colocation ip-with-slony2 inf: slony-fail2 vir-ip >> order ip-b4-slony2 inf: vir-ip slony-fail2 >> order slony-b4-ip inf: vir-ip slony-fail >> property $id="cib-bootstrap-options" \ >> dc-version="1.0.5-3840e6b5a305ccb803d29b468556739e75532d56" \ >> cluster-infrastructure="Heartbeat" \ >> no-quorum-policy="ignore" \ >> stonith-enabled="false" \ >> last-lrm-refresh="1266912039" >> >> rsc_defaults $id="rsc-options" \ >> resource-stickiness="INFINITY" >> >> >> -------------------------------------------- >> the log files are also attached... >> >> In crm_mon >> >> ============ >> Last updated: Tue Feb 23 13:49:41 2010 >> Stack: Heartbeat >> Current DC: node1 (ac87f697-5b44-4720-a8af-12a6f2295930) - partition with >> quorum >> >> Version: 1.0.5-3840e6b5a305ccb803d29b468556739e75532d56 >> 2 Nodes configured, unknown expected votes >> 5 Resources configured. >> ============ >> >> Online: [ node2 node1 ] >> >> Clone Set: pgclone >> Started: [ node2 node1 ] >> >> Clone Set: pingclone >> Started: [ node2 node1 ] >> --------------------------------------------------------------- >> >> Sir, >> What could be the issue [?] >> >> With thanks, >> Jayakrishnan. L >> >> >> On Tue, Feb 23, 2010 at 1:32 PM, Andrew Beekhof <and...@beekhof.net>wrote: >> >>> On Tue, Feb 23, 2010 at 8:51 AM, Jayakrishnan <jayakrishnan...@gmail.com> >>> wrote: >>> > Sir, >>> > Could you explain that a bit more. I have been reading the same >>> document for >>> > 2 days and cant specify the type as integer. It is showing as >>> > >>> > "Parsing error, do you want tot edit it again" >>> >>> [08:18 AM] r...@f12 ~ # crm configure help location >>> Signon to CIB failed: connection failed >>> Init failed, could not perform requested operations >>> ERROR: cannot parse xml: no element found: line 1, column 0 >>> >>> `location` defines the preference of nodes for the given >>> resource. The location constraints consist of one or more rules >>> which specify a score to be awarded if the rule matches. >>> >>> Usage: >>> ............... >>> location <id> <rsc> {node_pref|rules} >>> >>> node_pref :: <score>: <node> >>> >>> rules :: >>> rule [id_spec] [$role=<role>] <score>: <expression> >>> [rule [id_spec] [$role=<role>] <score>: <expression> ...] >>> >>> id_spec :: $id=<id> | $id-ref=<id> >>> score :: <number> | <attribute> | [-]inf >>> expression :: <simple_exp> [bool_op <simple_exp> ...] >>> bool_op :: or | and >>> simple_exp :: <attribute> [type:]<binary_op> <value> >>> | <unary_op> <attribute> >>> | date <date_expr> >>> type :: string | version | number >>> binary_op :: lt | gt | lte | gte | eq | ne >>> unary_op :: defined | not_defined >>> >>> date_expr :: lt <end> >>> | gt <start> >>> | in_range start=<start> end=<end> >>> | in_range start=<start> <duration> >>> | date_spec <date_spec> >>> duration|date_spec :: >>> hours=<value> >>> | monthdays=<value> >>> | weekdays=<value> >>> | yearsdays=<value> >>> | months=<value> >>> | weeks=<value> >>> | years=<value> >>> | weekyears=<value> >>> | moon=<value> >>> ............... >>> Examples: >>> ............... >>> location conn_1 internal_www 100: node1 >>> >>> location conn_1 internal_www \ >>> rule 50: #uname eq node1 \ >>> rule pingd: defined pingd >>> >>> location conn_2 dummy_float \ >>> rule -inf: not_defined pingd or pingd lte 0 >>> ............... >>> >>> >>> Though this last example is wrong: >>> >>> location conn_2 dummy_float \ >>> rule -inf: not_defined pingd or pingd number:lte 0 >>> >>> _______________________________________________ >>> Pacemaker mailing list >>> Pacemaker@oss.clusterlabs.org >>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>> >> >> >> >> -- >> Regards, >> >> Jayakrishnan. L >> >> Visit: www.jayakrishnan.bravehost.com >> >> >> _______________________________________________ >> Pacemaker mailing list >> Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> > _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker -- Regards, Jayakrishnan. L Visit: www.jayakrishnan.bravehost.com
<<33A.gif>>
_______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker