[Pacemaker] What is the reason which the node in which failure has not occurred carries out "lost"?
Yusuke Iida
yusk.iida at gmail.com
Mon Mar 10 21:59:01 EDT 2014
Hi, Andrew
I attach CLI file which loaded.
Although loaded xml does not exist as a file, I think from a log that
they are the following forms.
This log is extracted from the following reports.
https://drive.google.com/file/d/0BwMFJItoO-fVWEw4Qnp0aHIzSm8/edit?usp=sharing
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1365 ) info:
cib_perform_op: Diff: +++ 0.3.0 (null)
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1438 ) info:
cib_perform_op: -- /configuration
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1431 ) info:
cib_perform_op: + /cib: @epoch=3, @num_updates=0
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1387 ) info:
cib_perform_op: ++ /cib: <configuration/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <crm_config>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <cluster_property_set
id="cib-bootstrap-options">
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="no-quorum-policy"
value="ignore" id="cib-bootstrap-options-no-quorum-policy"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="stonith-enabled"
value="false" id="cib-bootstrap-options-stonith-enabled"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="startup-fencing"
value="false" id="cib-bootstrap-options-startup-fencing"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="stonith-timeout"
value="60s" id="cib-bootstrap-options-stonith-timeout"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="crmd-transition-delay"
value="2s" id="cib-bootstrap-options-crmd-transition-delay"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </cluster_property_set>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </crm_config>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nodes>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <node id="3232261508" uname="vm02"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <node id="3232261507" uname="vm01"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </nodes>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <resources>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <primitive id="prmDummy" class="ocf"
provider="heartbeat" type="Dummy">
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <!--#primitive prmDummy1
ocf:heartbeat:Dummy-->/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <!--#location rsc_location-group1-1
group1 # rule 200: #uname eq vm01 # rule 100: #uname eq vm02-->/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <instance_attributes
id="prmDummy-instance_attributes">
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgctl"
value="/usr/bin/pg_ctl" id="prmDummy-instance_attributes-pgctl"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="start_opt" value="-p
5432 -h 192.168.xxx.xxx" id="prmDummy-instance_attributes-start_opt"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="psql"
value="/usr/bin/psql" id="prmDummy-instance_attributes-psql"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgdata"
value="/var/lib/pgsql/data" id="prmDummy-instance_attributes-pgdata"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgdba"
value="postgres" id="prmDummy-instance_attributes-pgdba"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgport" value="5432"
id="prmDummy-instance_attributes-pgport"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgdb"
value="template1" id="prmDummy-instance_attributes-pgdb"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </instance_attributes>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <operations>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <op name="start" interval="0s"
timeout="60s" on-fail="restart" id="prmDummy-start-0s"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <op name="monitor" interval="30s"
timeout="60s" on-fail="restart" id="prmDummy-monitor-30s"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <op name="stop" interval="0s"
timeout="60s" on-fail="block" id="prmDummy-stop-0s"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </operations>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </primitive>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <primitive id="prmDummy2" class="ocf"
provider="heartbeat" type="Dummy">
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <instance_attributes
id="prmDummy2-instance_attributes">
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgctl"
value="/usr/bin/pg_ctl" id="prmDummy2-instance_attributes-pgctl"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="start_opt" value="-p
5432 -h 192.168.xxx.xxx"
id="prmDummy2-instance_attributes-start_opt"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="psql"
value="/usr/bin/psql" id="prmDummy2-instance_attributes-psql"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgdata"
value="/var/lib/pgsql/data"
id="prmDummy2-instance_attributes-pgdata"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgdba"
value="postgres" id="prmDummy2-instance_attributes-pgdba"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgport" value="5432"
id="prmDummy2-instance_attributes-pgport"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgdb"
value="template1" id="prmDummy2-instance_attributes-pgdb"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </instance_attributes>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <operations>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <op name="start" interval="0s"
timeout="60s" on-fail="restart" id="prmDummy2-start-0s"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <op name="monitor" interval="30s"
timeout="60s" on-fail="restart" id="prmDummy2-monitor-30s"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <op name="stop" interval="0s"
timeout="60s" on-fail="block" id="prmDummy2-stop-0s"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </operations>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </primitive>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <primitive id="prmDummy3" class="ocf"
provider="heartbeat" type="Dummy">
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <instance_attributes
id="prmDummy3-instance_attributes">
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgctl"
value="/usr/bin/pg_ctl" id="prmDummy3-instance_attributes-pgctl"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="start_opt" value="-p
5432 -h 192.168.xxx.xxx"
id="prmDummy3-instance_attributes-start_opt"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="psql"
value="/usr/bin/psql" id="prmDummy3-instance_attributes-psql"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgdata"
value="/var/lib/pgsql/data"
id="prmDummy3-instance_attributes-pgdata"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgdba"
value="postgres" id="prmDummy3-instance_attributes-pgdba"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgport" value="5432"
id="prmDummy3-instance_attributes-pgport"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgdb"
value="template1" id="prmDummy3-instance_attributes-pgdb"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </instance_attributes>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <operations>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <op name="start" interval="0s"
timeout="60s" on-fail="restart" id="prmDummy3-start-0s"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <op name="monitor" interval="30s"
timeout="60s" on-fail="restart" id="prmDummy3-monitor-30s"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <op name="stop" interval="0s"
timeout="60s" on-fail="block" id="prmDummy3-stop-0s"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </operations>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </primitive>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <primitive id="prmDummy4" class="ocf"
provider="heartbeat" type="Dummy">
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <instance_attributes
id="prmDummy4-instance_attributes">
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgctl"
value="/usr/bin/pg_ctl" id="prmDummy4-instance_attributes-pgctl"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="start_opt" value="-p
5432 -h 192.168.xxx.xxx"
id="prmDummy4-instance_attributes-start_opt"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="psql"
value="/usr/bin/psql" id="prmDummy4-instance_attributes-psql"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgdata"
value="/var/lib/pgsql/data"
id="prmDummy4-instance_attributes-pgdata"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgdba"
value="postgres" id="prmDummy4-instance_attributes-pgdba"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgport" value="5432"
id="prmDummy4-instance_attributes-pgport"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="pgdb"
value="template1" id="prmDummy4-instance_attributes-pgdb"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </instance_attributes>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <operations>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <op name="start" interval="0s"
timeout="60s" on-fail="restart" id="prmDummy4-start-0s"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <op name="monitor" interval="30s"
timeout="60s" on-fail="restart" id="prmDummy4-monitor-30s"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <op name="stop" interval="0s"
timeout="60s" on-fail="block" id="prmDummy4-stop-0s"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </operations>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </primitive>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </resources>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <constraints/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <rsc_defaults>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <meta_attributes id="rsc-options">
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="resource-stickiness"
value="INFINITY" id="rsc-options-resource-stickiness"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ <nvpair name="migration-threshold"
value="1" id="rsc-options-migration-threshold"/>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </meta_attributes>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </rsc_defaults>
Mar 07 13:24:14 [2523] vm01 cib: ( xml.c:1394 ) info:
cib_perform_op: ++ </configuration>
Regards,
Yusuke
2014-03-11 10:26 GMT+09:00 Andrew Beekhof <andrew at beekhof.net>:
>
> On 7 Mar 2014, at 5:35 pm, Yusuke Iida <yusk.iida at gmail.com> wrote:
>
>> Hi, Andrew
>> 2014-03-07 11:43 GMT+09:00 Andrew Beekhof <andrew at beekhof.net>:
>>> I don't understand... crm_mon doesn't look for changes to resources or constraints and it should already be using the new faster diff format.
>>>
>>> [/me reads attachment]
>>>
>>> Ah, but perhaps I do understand afterall :-)
>>>
>>> This is repeated over and over:
>>>
>>> notice: crm_diff_update: [cib_diff_notify] Patch aborted: Application of an update diff failed (-206)
>>> notice: xml_patch_version_check: Current num_updates is too high (885 > 67)
>>>
>>> That would certainly drive up CPU usage and cause crm_mon to get left behind.
>>> Happily the fix for that should be: https://github.com/beekhof/pacemaker/commit/6c33820
>>
>> I think that refreshment of cib is no longer repeated when a version
>> has a difference.
>> Thank you cope.
>>
>> Now, I see another problem.
>>
>> If "crm configure load update" is performed, with crm_mon started,
>> information will no longer be displayed.
>> Information will be displayed if crm_mon is restarted.
>>
>> I executed the following commands and took the log of crm_mon.
>> # crm_mon --disable-ncurses -VVVVVV >crm_mon.log 2>&1
>>
>> I am observing the cib information inside crm_mon after load was performed.
>>
>> Two configuration sections exist in cib after load.
>>
>> It seems that this is the next processing, and it remains since it
>> failed in deletion of the configuration section.
>> trace: cib_native_dispatch_internal: cib-reply
>> <change operation="delete" path="/configuration"/>
>>
>> A little following is the debugging log acquired by old pacemaker.
>> It is not found in order that <(null) > may try to look for
>> path=/configuration from the document tree of top.
>> Should not path be path=/cib/configuration essentially?
>
> Yes. Could you send me the cib as well as the update you're trying to load?
>
>>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: <(null)>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: <cib
>> epoch="2" num_updates="6" admin_epoch="0"
>> validate-with="pacemaker-1.2" crm_feature_set="3.0.9"
>> cib-last-written="Tue Mar 4 11:32:36 2014"
>> update-origin="rhel64rpmbuild" update-client="crmd" have-quorum="1"
>> dc-uuid="3232261524">
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: <configuration>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: <crm_config>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> <cluster_property_set id="cib-bootstrap-options">
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> <nvpair id="cib-bootstrap-options-dc-version" name="dc-version"
>> value="1.1.10-2dbaf19"/>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> <nvpair id="cib-bootstrap-options-cluster-infrastructure"
>> name="cluster-infrastructure" value="corosync"/>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> </cluster_property_set>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: </crm_config>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: <nodes>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> <node id="3232261524" uname="rhel64rpmbuild"/>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: </nodes>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: <resources/>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: <constraints/>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: </configuration>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: <status>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> <node_state id="3232261524" uname="rhel64rpmbuild" in_ccm="true"
>> crmd="online" crm-debug-origin="do_state_transition" join="member"
>> expected="member">
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> <lrm id="3232261524">
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> <lrm_resources/>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: </lrm>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> <transient_attributes id="3232261524">
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> <instance_attributes id="status-3232261524">
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> <nvpair id="status-3232261524-shutdown" name="shutdown" value="0"/>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> <nvpair id="status-3232261524-probe_complete" name="probe_complete"
>> value="true"/>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> </instance_attributes>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG:
>> </transient_attributes>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: </node_state>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: </status>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: </cib>
>> notice Mar 04 11:33:10 __xml_find_path(1294):0: IDEBUG: </(null)>
>>
>>
>> Is this the already recognized problem?
>>
>> I attach the report at the time of this occurring, and the log of crm_mon.
>>
>> - crm_report
>> https://drive.google.com/file/d/0BwMFJItoO-fVWEw4Qnp0aHIzSm8/edit?usp=sharing
>> - crm_mon.log
>> https://drive.google.com/file/d/0BwMFJItoO-fVRDRMTGtUUEdBc1E/edit?usp=sharing
>>
>> Regards,
>> Yusuke
>>
>>
>> --
>> ----------------------------------------
>> METRO SYSTEMS CO., LTD
>>
>> Yusuke Iida
>> Mail: yusk.iida at gmail.com
>> ----------------------------------------
>>
>> _______________________________________________
>> 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
>
>
> _______________________________________________
> 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
>
--
----------------------------------------
METRO SYSTEMS CO., LTD
Yusuke Iida
Mail: yusk.iida at gmail.com
----------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.crm
Type: application/octet-stream
Size: 2508 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140311/ea1e129b/attachment-0003.obj>
More information about the Pacemaker
mailing list