You must configure a monitor operation for the resource. It will report the status of the resource back to the cluster.
Also mkae sure you have tested your resource script with the ocf-tester program -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of heartbeat Sent: Wednesday, 17 September 2008 12:33 PM To: linux-ha Subject: [Linux-HA] About OCF Resource Agents Hi all, Originally, I thought the "monitor" action would be called by heartbeat periodically, and heartbeat would then send the return code to other nodes in the heartbeat cluster. So the nodes can get the status of the software service, and if the software service crashed other nodes can take over that software service. I wrote a test OCF Resource Agents called "myagent", it did nothing but log the action call message such as "monitor my test agent!","stop my test agent!","start my test agent!". But I found the monitor action was not called by the heartbeat periodically. It just would be called when the heartbeat started. So I just can't understand about these. If the monitor action is not called periodically, how can the nodes know if the software service being monitored runs normally. If the software service crashed suddenly, can the heartbeat nodes detected? How can I keep the high availability of a software service with heartbeat? Thanks in advance. This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
