[Linux-HA] DRBD with monitor Operations won't start - as soon as I
delete the operations, it starts immediately
Thomas Glanzmann
thomas at glanzmann.de
Thu Jan 3 05:08:36 MST 2008
Hello,
I have heartbeat-2.1.3 and drbd-8.2.1. I start with a drbd setup which
is initialized and has a filesystem on it and a fresh heartbeat setup
(rm /var/lib/heartbeat/crm/*) on both nodes while they are powered off.
(ha-1) [~] cat /etc/ha.d/ha.cf
use_logd yes
bcast eth1
mcast eth0 239.0.0.2 694 1 0
node ha-1 ha-2
respawn hacluster /usr/lib/heartbeat/dopd
apiauth dopd uid=hacluster gid=haclient
crm on
(ha-1) [~] cat /etc/drbd.conf
global {
usage-count no;
}
common {
syncer {
rate 100M;
}
handlers {
outdate-peer "/usr/lib/heartbeat/drbd-peer-outdater";
}
}
resource postgres {
protocol C;
startup {
degr-wfc-timeout 120;
}
disk {
on-io-error pass_on;
fencing resource-only;
}
on ha-1 {
device /dev/drbd0;
disk /dev/sda5;
address 10.0.0.191:7788;
meta-disk internal;
}
on ha-2 {
device /dev/drbd0;
disk /dev/sda5;
address 10.0.0.192:7788;
meta-disk internal;
}
}
(ha-1) [~] cat postgres.xml
<configuration>
<crm_config>
<cluster_property_set id="cib-bootstrap-options">
<attributes>
</attributes>
</cluster_property_set>
</crm_config>
<resources>
<master_slave id="ms-drbd0">
<meta_attributes id="ma-ms-drbd0">
<attributes>
<nvpair id="ma-ms-drbd0-1" name="clone_max" value="2"/>
<nvpair id="ma-ms-drbd0-2" name="clone_node_max" value="1"/>
<nvpair id="ma-ms-drbd0-3" name="master_max" value="1"/>
<nvpair id="ma-ms-drbd0-4" name="master_node_max" value="1"/>
<nvpair id="ma-ms-drbd0-5" name="notify" value="yes"/>
<nvpair id="ma-ms-drbd0-6" name="globally_unique" value="false"/>
</attributes>
</meta_attributes>
<primitive id="drbd0" class="ocf" provider="heartbeat" type="drbd">
<instance_attributes id="ia-drbd0">
<attributes>
<nvpair id="ia-drbd0-1" name="drbd_resource" value="postgres"/>
</attributes>
</instance_attributes>
<operations>
<op id="op-ms-drbd2-1" name="monitor" interval="60s" timeout="60s" start_delay="30s" role="Master"/>
<op id="op-ms-drbd2-2" name="monitor" interval="60s" timeout="60s" start_delay="30s" role="Slave"/>
</operations>
</primitive>
</master_slave>
<group id="postgres-cluster">
<primitive class="ocf" provider="heartbeat" type="Filesystem" id="fs0">
<instance_attributes id="ia-fs0">
<attributes>
<nvpair id="ia-fs0-1" name="fstype" value="ext3"/>
<nvpair name="directory" id="ia-fs0-2" value="/srv/postgres"/>
<nvpair id="ia-fs0-3" name="device" value="/dev/drbd0"/>
</attributes>
</instance_attributes>
<operations>
<op id="fs0-monitor0" name="monitor" interval="60s" timeout="120s" start_delay="1m"/>
</operations>
</primitive>
<primitive class="ocf" provider="heartbeat" type="IPaddr2" id="ip0">
<instance_attributes id="ia-ip0">
<attributes>
<nvpair id="ia-ip0-1" name="ip" value="10.0.0.193"/>
<nvpair id="ia-ip0-2" name="cidr_netmask" value="25"/>
<nvpair id="ia-ip0-3" name="nic" value="eth0"/>
</attributes>
</instance_attributes>
<operations>
<op id="ip0-monitor0" name="monitor" interval="60s" timeout="120s" start_delay="1m"/>
</operations>
</primitive>
</group>
</resources>
<constraints>
<rsc_location id="drbd0-placement-1" rsc="ms-drbd0">
<rule id="drbd0-rule-1" score="-INFINITY">
<expression id="exp-01" value="ha-1" attribute="#uname" operation="ne"/>
<expression id="exp-02" value="ha-2" attribute="#uname" operation="ne"/>
</rule>
</rsc_location>
<rsc_order id="postgres_promotes_ms-drbd0" from="postgres-cluster" action="start" to="ms-drbd0" to_action="promote"/>
<rsc_colocation id="postgres_on_drbd0" to="ms-drbd0" to_role="master" from="postgres-cluster" score="infinity"/>
</constraints>
</configuration>
When I load the postgres.xml usning
cibadmin -U -x postgres.xml
I see the following status:
(ha-2) [~] crm_mon -r -1
============
Last updated: Thu Jan 3 12:53:51 2008
Current DC: ha-2 (095256ab-361c-4b1e-9a8b-8bed74c4a7fb)
2 Nodes configured.
2 Resources configured.
============
Node: ha-2 (095256ab-361c-4b1e-9a8b-8bed74c4a7fb): online
Node: ha-1 (330da1b6-5f99-480a-b071-a144a98e1248): online
Full list of resources:
Master/Slave Set: ms-drbd0
drbd0:0 (heartbeat::ocf:drbd): Started ha-2
drbd0:1 (heartbeat::ocf:drbd): Started ha-1
Resource Group: postgres-cluster
fs0 (heartbeat::ocf:Filesystem): Stopped
ip0 (heartbeat::ocf:IPaddr2): Stopped
Please note drbd0:0 and drbd0:1 are started but none of the two gets
promoted as Master. The other ressources don't come up as a result.
In my syslog I see the following:
Jan 3 12:52:34 ha-2 pengine: [5879]: notice: RecurringOp: ha-1^I drbd0:1_monitor_60000
Jan 3 12:52:34 ha-2 pengine: [5879]: info: master_color: ms-drbd0: Promoted 1 instances of a possible 1 to master
Jan 3 12:52:34 ha-2 pengine: [5879]: notice: StartRsc: ha-2^IStart fs0
Jan 3 12:52:34 ha-2 pengine: [5879]: notice: RecurringOp: ha-2^I fs0_monitor_60000
Jan 3 12:52:34 ha-2 pengine: [5879]: notice: StartRsc: ha-2^IStart ip0
Jan 3 12:52:34 ha-2 pengine: [5879]: notice: RecurringOp: ha-2^I ip0_monitor_60000
Jan 3 12:52:34 ha-2 crmd: [5870]: info: do_lrm_rsc_op: Performing op=drbd0:0_notify_0 key=54:4:579f4c1f-38d6-4030-b8fb-c5191f735ca9)
Jan 3 12:52:34 ha-2 lrmd: [5867]: info: rsc:drbd0:0: notify
Jan 3 12:52:34 ha-2 pengine: [5879]: info: process_pe_message: Transition 4: PEngine Input stored in: /var/lib/heartbeat/pengine/pe-input-32.bz2
Jan 3 12:52:34 ha-2 drbd[6119]: [6130]: DEBUG: postgres notify: pre for promote - counts: active 0 - starting 2 - stopping 0
Jan 3 12:52:34 ha-2 crmd: [5870]: info: process_lrm_event: LRM operation drbd0:0_notify_0 (call=7, rc=0) complete
Jan 3 12:52:34 ha-2 tengine: [5878]: info: match_graph_event: Action drbd0:0_pre_notify_promote_0 (54) confirmed on ha-2 (rc=0)
Jan 3 12:52:35 ha-2 tengine: [5878]: info: process_te_message: Processing (N)ACK lrm_invoke-lrmd-1199361154-5 from ha-1
Jan 3 12:52:35 ha-2 tengine: [5878]: info: match_graph_event: Action drbd0:1_monitor_60000 (13) confirmed on ha-1 (rc=0)
Jan 3 12:52:35 ha-2 tengine: [5878]: info: match_graph_event: Action drbd0:1_pre_notify_promote_0 (62) confirmed on ha-1 (rc=0)
Jan 3 12:52:35 ha-2 tengine: [5878]: info: te_pseudo_action: Pseudo action 29 fired and confirmed
Jan 3 12:52:35 ha-2 tengine: [5878]: info: te_pseudo_action: Pseudo action 26 fired and confirmed
Jan 3 12:52:35 ha-2 tengine: [5878]: notice: run_graph: ====================================================
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: run_graph: Transition 4: (Complete=6, Pending=0, Fired=0, Skipped=0, Incomplete=13)
Jan 3 12:52:35 ha-2 tengine: [5878]: ERROR: te_graph_trigger: Transition failed: terminated
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Graph 4 (19 actions in 19 synapses): batch-limit=30 jobs, network-delay=60000ms
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 0 is pending (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: [Action 8]: Pending (id: drbd0:0_promote_0, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 9]: Pending (id: drbd0:0_monitor_60000, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 26]: Completed (id: ms-drbd0_promote_0, type: pseduo, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 1 is pending (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: [Action 9]: Pending (id: drbd0:0_monitor_60000, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 8]: Pending (id: drbd0:0_promote_0, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 2 was confirmed (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 3 is pending (priority: 1000000)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: [Action 55]: Pending (id: drbd0:0_post_notify_promote_0, loc: ha-2, priority: 1000000)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 30]: Pending (id: ms-drbd0_post_notify_promote_0, type: pseduo, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 4 was confirmed (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 5 was confirmed (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 6 is pending (priority: 1000000)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: [Action 63]: Pending (id: drbd0:1_post_notify_promote_0, loc: ha-1, priority: 1000000)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 30]: Pending (id: ms-drbd0_post_notify_promote_0, type: pseduo, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 7 was confirmed (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 8 is pending (priority: 1000000)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: [Action 27]: Pending (id: ms-drbd0_promoted_0, type: pseduo, priority: 1000000)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 8]: Pending (id: drbd0:0_promote_0, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 9 was confirmed (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 10 was confirmed (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 11 is pending (priority: 1000000)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: [Action 30]: Pending (id: ms-drbd0_post_notify_promote_0, type: pseduo, priority: 1000000)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 27]: Pending (id: ms-drbd0_promoted_0, type: pseduo, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 12 is pending (priority: 1000000)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: [Action 31]: Pending (id: ms-drbd0_confirmed-post_notify_promote_0, type: pseduo, priority: 1000000)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 30]: Pending (id: ms-drbd0_post_notify_promote_0, type: pseduo, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 55]: Pending (id: drbd0:0_post_notify_promote_0, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 63]: Pending (id: drbd0:1_post_notify_promote_0, loc: ha-1, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 13 is pending (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: [Action 42]: Pending (id: postgres-cluster_start_0, type: pseduo, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 31]: Pending (id: ms-drbd0_confirmed-post_notify_promote_0, type: pseduo, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 14 is pending (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: [Action 43]: Pending (id: postgres-cluster_running_0, type: pseduo, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 38]: Pending (id: fs0_start_0, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 40]: Pending (id: ip0_start_0, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 42]: Pending (id: postgres-cluster_start_0, type: pseduo, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 15 is pending (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: [Action 38]: Pending (id: fs0_start_0, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 42]: Pending (id: postgres-cluster_start_0, type: pseduo, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 16 is pending (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: [Action 39]: Pending (id: fs0_monitor_60000, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 crmd: [5870]: info: do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_IPC_MESSAGE origin=route_message ]
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 38]: Pending (id: fs0_start_0, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 17 is pending (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: [Action 40]: Pending (id: ip0_start_0, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 38]: Pending (id: fs0_start_0, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_graph: Synapse 18 is pending (priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: [Action 41]: Pending (id: ip0_monitor_60000, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: WARN: print_elem: * [Input 40]: Pending (id: ip0_start_0, loc: ha-2, priority: 0)
Jan 3 12:52:35 ha-2 tengine: [5878]: info: notify_crmd: Transition 4 status: te_complete - <null>
As soon as I delete the two Monitor Operations using:
cibadmin -o resources -D -X '<op id="op-ms-drbd2-1" name="monitor" interval="60s" timeout="60s" start_delay="30s" role="Master"/>'
cibadmin -o resources -D -X '<op id="op-ms-drbd2-2" name="monitor" interval="60s" timeout="60s" start_delay="30s" role="Slave"/>'
The cluster comes magically to live:
Jan 3 12:57:03 ha-2 cib: [5866]: info: log_data_element: cib:diff: - <cib epoch="2" num_updates="18">
Jan 3 12:57:03 ha-2 tengine: [5878]: info: update_abort_priority: Abort priority upgraded to 1000000
Jan 3 12:57:03 ha-2 cib: [5866]: info: log_data_element: cib:diff: - <configuration>
Jan 3 12:57:03 ha-2 cib: [5866]: info: log_data_element: cib:diff: - <resources>
Jan 3 12:57:03 ha-2 cib: [5866]: info: log_data_element: cib:diff: - <master_slave id="ms-drbd0">
Jan 3 12:57:03 ha-2 cib: [5866]: info: log_data_element: cib:diff: - <primitive id="drbd0">
Jan 3 12:57:03 ha-2 cib: [5866]: info: log_data_element: cib:diff: - <operations>
Jan 3 12:57:03 ha-2 cib: [5866]: info: log_data_element: cib:diff: - <op id="op-ms-drbd2-1" name="monitor" interval="60s" timeout="60s" start_delay="30s" role="Master"/>
Jan 3 12:57:03 ha-2 cib: [5866]: info: log_data_element: cib:diff: - </operations>
Jan 3 12:57:03 ha-2 cib: [5866]: info: log_data_element: cib:diff: - </primitive>
Jan 3 12:57:03 ha-2 cib: [5866]: info: log_data_element: cib:diff: - </master_slave>
Jan 3 12:57:03 ha-2 cib: [5866]: info: log_data_element: cib:diff: - </resources>
Jan 3 12:57:03 ha-2 cib: [5866]: info: log_data_element: cib:diff: - </configuration>
Jan 3 12:57:03 ha-2 cib: [5866]: info: log_data_element: cib:diff: - </cib>
Jan 3 12:57:04 ha-2 cib: [5866]: info: log_data_element: cib:diff: + <cib epoch="3" num_updates="1"/>
Jan 3 12:57:04 ha-2 crmd: [5870]: info: do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_IPC_MESSAGE origin=route_message ]
Jan 3 12:57:04 ha-2 crmd: [5870]: info: do_state_transition: All 2 cluster nodes are eligible to run resources.
Jan 3 12:57:04 ha-2 pengine: [5879]: info: determine_online_status: Node ha-2 is online
Jan 3 12:57:04 ha-2 pengine: [5879]: info: determine_online_status: Node ha-1 is online
Jan 3 12:57:04 ha-2 pengine: [5879]: info: unpack_find_resource: Internally renamed drbd0:0 on ha-1 to drbd0:1
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: clone_print: Master/Slave Set: ms-drbd0
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: native_print: drbd0:0^I(heartbeat::ocf:drbd):^IStarted ha-2
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: native_print: drbd0:1^I(heartbeat::ocf:drbd):^IStarted ha-1
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: group_print: Resource Group: postgres-cluster
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: native_print: fs0^I(heartbeat::ocf:Filesystem):^IStopped
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: native_print: ip0^I(heartbeat::ocf:IPaddr2):^IStopped
Jan 3 12:57:04 ha-2 pengine: [5879]: info: master_promotion_order: Merging weights for ms-drbd0
Jan 3 12:57:04 ha-2 pengine: [5879]: info: master_color: Promoting drbd0:0
Jan 3 12:57:04 ha-2 pengine: [5879]: info: master_color: ms-drbd0: Promoted 1 instances of a possible 1 to master
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: DemoteRsc: ha-2^IDemote drbd0:0
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: NoRoleChange: Leave resource drbd0:0^I(ha-2)
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: PromoteRsc: ha-2^IPromote drbd0:0
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: DemoteRsc: ha-1^IDemote drbd0:1
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: NoRoleChange: Leave resource drbd0:1^I(ha-1)
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: RecurringOp: ha-1^I drbd0:1_monitor_60000
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: DemoteRsc: ha-2^IDemote drbd0:0
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: NoRoleChange: Leave resource drbd0:0^I(ha-2)
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: PromoteRsc: ha-2^IPromote drbd0:0
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: DemoteRsc: ha-1^IDemote drbd0:1
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: NoRoleChange: Leave resource drbd0:1^I(ha-1)
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: RecurringOp: ha-1^I drbd0:1_monitor_60000
Jan 3 12:57:04 ha-2 pengine: [5879]: info: master_color: ms-drbd0: Promoted 1 instances of a possible 1 to master
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: StartRsc: ha-2^IStart fs0
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: RecurringOp: ha-2^I fs0_monitor_60000
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: StartRsc: ha-2^IStart ip0
Jan 3 12:57:04 ha-2 pengine: [5879]: notice: RecurringOp: ha-2^I ip0_monitor_60000
Jan 3 12:57:04 ha-2 crmd: [5870]: info: do_state_transition: State transition S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS cause=C_IPC_MESSAGE origin=route_message ]
...
(ha-1) [~] crm_mon -1 -r
============
Last updated: Thu Jan 3 13:06:51 2008
Current DC: ha-2 (095256ab-361c-4b1e-9a8b-8bed74c4a7fb)
2 Nodes configured.
2 Resources configured.
============
Node: ha-2 (095256ab-361c-4b1e-9a8b-8bed74c4a7fb): online
Node: ha-1 (330da1b6-5f99-480a-b071-a144a98e1248): online
Full list of resources:
Master/Slave Set: ms-drbd0
drbd0:0 (heartbeat::ocf:drbd): Master ha-2
drbd0:1 (heartbeat::ocf:drbd): Started ha-1
Resource Group: postgres-cluster
fs0 (heartbeat::ocf:Filesystem): Started ha-2
ip0 (heartbeat::ocf:IPaddr2): Started ha-2
Could somone please tell me what is going on here? What is wrong with
the two Monitor Operations and why does the cluster choke on it? But
what I don't get is that Dominik (CCed) has the exact same configuration
and for him it works. But I am not sure if he has 2.1.3 on his
production system.
Thomas
More information about the Linux-HA
mailing list