Hello Jason,
> 1) For the monitor action, I might suggest the docs be updated
> slightly. According to http://www.linux-ha.org/OCFResourceAgent, 0
> for 'running', 7 for 'stopped', and anything else is valid, but
> indicates an error.
> I have modified my script to only return '1' on error. However, the
> same issue persists (Error in resource_samba_storage_monitor_0).
can you check to run it manually. Your ressource agent doesn't seem to
need any arguments so you should be able to do that:
- stop heartbeat on node2
- Wait a while until you see the state again
- Call /path/to/resource_samba_storage monito && echo Okay || echo
Failed
I am pretty sure that this gives you a Failed. Than track it
down and get sure that it returns "Okay".
> 2) crm_resource -C does not seem to have any effect. I could not be
> looking in the right place though.
Get sure that you didn't misspelled the name of the service and the name
of the host. If you have your service running on node3 and call the
cleanup. The failled monitor transaction has to vanish from the output
of "crm_mon -1 -r".
> 3) The cibadmin -Q results are attached.
Thanks. Looks fine for me. What you could always try is the following it
wipes all states for sure:
- Stop heartbeat on both nodes
- Call "rm /var/lib/heartbeat/crm/*" on both nodes (that wipes
your linux ha config including any logged states)
- Start heartbeat on both nodes
- call cibadmin -U -X'
<configuration>
<resources>
<group id="group_samba">
<primitive id="resource_samba_ip" class="ocf"
type="IPaddr" provider="heartbeat">
<instance_attributes
id="resource_samba_ip_instance_attrs">
<attributes>
<nvpair
id="a572b727-1aaf-43b5-b2c3-826305b6d533" name="ip" value="10.31.11.114"/>
<nvpair
id="3669be20-7782-432e-9504-ba65668186ca" name="nic" value="eth0"/>
<nvpair
id="14fbbd65-3019-43e9-8eb5-d9fb88deced2" name="cidr_netmask"
value="255.255.255.0"/>
<nvpair
id="941cbbab-490d-48e7-88a8-3d4d62ff79a5" name="broadcast"
value="10.31.11.255"/>
<nvpair
id="e44afc64-42cb-470e-b418-9a981991ee02" name="iflabel" value="vtqfs"/>
</attributes>
</instance_attributes>
<operations>
<op name="monitor" interval="60s"
timeout="120s" start_delay="1m" id="monitor-samba-ip"/>
</operations>
</primitive>
<primitive id="resource_samba_storage" class="lsb"
type="hb-vxvol" provider="heartbeat">
<operations>
<op name="monitor" interval="60s"
timeout="120s" start_delay="1m" id="monitor-samba-storage"/>
</operations>
</primitive>
<primitive id="resource_samba_daemon" class="lsb"
type="hb-samba" provider="heartbeat">
<operations>
<op name="monitor" interval="60s"
timeout="120s" start_delay="1m" id="monitor-samba-daemon"/>
</operations>
</primitive>
</group>
</resources>
</configuration>
'
Oh, and what I don't get at all is the following: In your CIB you did not had a
monitor action defined at all. At least with 2.1.3 means that your resource
isn't monitored at all with one exception: Right after it is started. Could it
be possible that your samba_storage RA does fork of another process in the
background and returns immediatly? If that is the case, adopt the RA to don't
do that. It should only return when the service is running. And running means
it should be in a state so that monitor returns 0. The Postgres RA is a good
example for this, I guess. I added monitor operations to your configuration.
Nevertheless you should upgrade to 2.1.3 as soon as possible.
Thomas
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
