Hello,
I have succesfully configured a simple two-node cluster. The cluster manages
only two virtual IPs, so far.
I'd like to add another resource, which would be a simple application which
is started by "init.d-type" script, for example: /etc/init.d/app start.
After start it is running "daemon-like".
As I suppose I should use ocf:heartbeat:anything resource agent to manage
this application.
Unfortunately when trying to use it I get some unknown_errors and process
fails to start:
Jun 4 01:44:18 blue pengine: [24591]: info: unpack_config: Startup probes:
enabled
Jun 4 01:44:18 blue pengine: [24591]: notice: unpack_config: On loss of CCM
Quorum: Ignore
Jun 4 01:44:18 blue pengine: [24591]: info: unpack_config: Node scores:
'red' = -INFINITY, 'yellow' = 0, 'green' = 0
Jun 4 01:44:18 blue pengine: [24591]: info: unpack_domains: Unpacking
domains
Jun 4 01:44:18 blue pengine: [24591]: info: determine_online_status: Node
red is online
Jun 4 01:44:18 blue pengine: [24591]: WARN: unpack_rsc_op: Processing
failed op app_monitor_20000 on red: unknown error (1)
Jun 4 01:44:18 blue pengine: [24591]: WARN: unpack_rsc_op: Processing
failed op app_start_0 on red: unknown error (1)
Jun 4 01:44:18 blue pengine: [24591]: info: determine_online_status: Node
blue is online
Jun 4 01:44:18 blue pengine: [24591]: WARN: unpack_rsc_op: Processing
failed op app_monitor_20000 on blue: unknown error (1)
Jun 4 01:44:18 blue pengine: [24591]: WARN: unpack_rsc_op: Processing
failed op app_start_0 on blue: unknown error (1)
Jun 4 01:44:18 blue pengine: [24591]: notice: native_print:
res_IPaddr2_VIPAPP-112#011(ocf::heartbeat:IPaddr2):#011Started red
Jun 4 01:44:18 blue pengine: [24591]: notice: native_print:
res_IPaddr2_VIPAPP-118#011(ocf::heartbeat:IPaddr2):#011Started blue
Jun 4 01:44:18 blue pengine: [24591]: notice: native_print:
app#011(ocf::heartbeat:anything):#011Stopped
Jun 4 01:44:18 blue pengine: [24591]: info: get_failcount: app has failed
INFINITY times on red
Jun 4 01:44:18 blue pengine: [24591]: WARN: common_apply_stickiness:
Forcing app away from red after 1000000 failures (max=1000000)
Jun 4 01:44:18 blue pengine: [24591]: info: get_failcount: app has failed
INFINITY times on blue
Jun 4 01:44:18 blue pengine: [24591]: WARN: common_apply_stickiness:
Forcing app away from blue after 1000000 failures (max=1000000)
Jun 4 01:44:18 blue pengine: [24591]: info: native_color: Resource app
cannot run anywhere
Jun 4 01:44:18 blue pengine: [24591]: notice: LogActions: Leave resource
res_IPaddr2_VIPAPP-112#011(Started red)
Jun 4 01:44:18 blue pengine: [24591]: notice: LogActions: Leave resource
res_IPaddr2_VIPAPP-118#011(Started blue)
Jun 4 01:44:18 blue pengine: [24591]: notice: LogActions: Leave resource
app#011(Stopped)
My cluster configuration:
node blue
node red \
attributes standby="off"
primitive res_IPaddr2_VIPAPP-112 ocf:heartbeat:IPaddr2 \
params ip="172.16.112.67" \
operations $id="res_IPaddr2_VIPAPP-112-operations" \
op start interval="0" timeout="20" \
op stop interval="0" timeout="20" \
op monitor interval="10" timeout="20" start-delay="0"
primitive res_IPaddr2_VIPAPP-118 ocf:heartbeat:IPaddr2 \
params ip="172.16.118.5" \
operations $id="res_IPaddr2_VIPAPP-118-operations" \
op start interval="0" timeout="20" \
op stop interval="0" timeout="20" \
op monitor interval="10" timeout="20" start-delay="0"
primitive res_anything_1 ocf:heartbeat:anything \
params binfile="/etc/init.d/app" cmdline_options="start" \
operations $id="res_anything_1-operations" \
op start interval="0" timeout="20" \
op stop interval="0" timeout="20" \
op monitor interval="10" timeout="20" start-delay="0"
property $id="cib-bootstrap-options" \
expected-quorum-votes="2" \
stonith-enabled="false" \
dc-version="1.1.2-f059ec7ced7a86f18e5490b67ebf4a0b963bccfe" \
no-quorum-policy="ignore" \
cluster-infrastructure="openais"
What are the prerequisites to run process by ocf:heartbeat:anything? Should
I use some different agent? Maybe the only way is writing your own agent?
I'll be grateful for any help.
Regards,
Mateusz
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
