Hello Jason,
> [1] Though I don't understand why 'resource_samba_storage_monitor_0
> keeps giving Error.
your monitor action should do the following:
If resource is running => exit 0
If resource is stopped => exit 7
Otherwise => exit 1
I think the "rc=9" refers to a "exit 9" but it definitely doesn't refer
to a "exit 0" as it should be. So something is wrong with your monitor
implemenation. Adress that first.
You can cleanup the resource by calling:
crm_resource -C -r resource_samba_storage -H node1.domain.com
Btw. if the monitor operation only fails on one node but succeeds on the
other node, than there you have your "resource stickiness".
> [2] to satisy ocf-tester. Once I figure out how parameters,
> validate-all and promote/demote/notify work, I'll implement something
> better than 'exit 0'...
I think there is no need to. If you search the recent archives of this
month you see two "OCF resource agents" written by me. Both of them work
without these.
About the resource stickiness. Did you create your resources using the
gui? If that is the case ... I saw the same problem with heartbeat-2.1.3
but I never found out the reason behind that but stopped using the gui.
Could you please send me the output of "cibadmin -Q"?
Thomas
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
