Well you all seem like a friendly enough bunch as I lurk about the list,
so here goes...
I've read some fine Linux-HA (V2) tutorials and have begun experimenting
with Linux-HA on a 2 node setup. Installation of heartbeat went well
and I even glimpsed ip failover in action. Now I am attempting to use
ocf to launch a test daemon of mine, by mimicing the apache scripts
d/l'd with V2.
>From log debug o/p, I see ocf_run launching my daemon, but then see a
timeout in ha-log:
tengine[23602]: 2008/01/02_17:56:46 WARN: print_elem: Action missed
its timeout[Action 6]: In-flight (id: server1_start_0, loc: c001n02,
priority: 0)
I'll be the first to admit, this app is not production qual. It simply
forks a child that sits and waits on a listen. I could not imagine
there was more needed for this experiment but maybe there is.
o/p from crm_verify also reveals:
crm_verify[26701]: 2008/01/02_19:40:11 WARN: unpack_rsc_op:
Processing failed op server2_start_0 on c001n02: Timed Out
crm_verify[26701]: 2008/01/02_19:40:11 WARN: unpack_rsc_op:
Compatability handling for failed op server2_start_0 on c001n02
crm_verify[26701]: 2008/01/02_19:40:11 WARN: native_color: Resource
server2 cannot run anywhere
Here is the related portion of the cib.xml:
<primitive id="server2" class="heartbeat" type="server">
<instance_attributes id="ia2_s2">
<attributes>
<nvpair id="s2" name="1" value="value2"/>
</attributes>
</instance_attributes>
</primitive>
.
.
.
<constraints>
<rsc_location id="run_ip_resource_2" rsc="server2">
<rule id="pref_run_ip_resource_2" score="100">
<expression id="e2" attribute="#hostname" operation="eq"
value="c001n02"/>
</rule>
</rsc_location>
</constraints>
The type "server", as I alluded, mimics the apache scripts provided in
the heartbeat d/l. I launch the app using ocf_run, via the server
script deposited in /usr/lib/ocf/resource.d/heartbeat/server.
Can someone give me a clue why the timeout occurs ?
Thanks alot,
lew
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems