Jason,
just to get sure that we're on the same page here:
- You have a two node cluster
- You have a resource that is running only on one node
- When you run the resource on node b, node a reports for that
resource a failed monitor?
If that is the case then something is horrible wrong. Because the
monitor operation for a resource should only run on a node that is
currently running the resource.
What I thought before is the following:
You start your resource, heartbeat tries to start your resource on node
a, the monitor that heartbeat starts right after it tried to start the
resource to verify that is everything all right, fails. So heartbeat
decides to run the resource on node b, calls monitor to verify
afterwards and everything is fine. And you end up with the failed
monitor on node a reported in "crm_mon -1 -r".
So might it be possible that your monitor action _always_ fails on node
a even if the service is correctly started on that node? Try to start
your service (with heartbeat stopped on both machines) and then try to
call your resouce agent with the monitor argument and see if it does the
right thing or does not.
Thomas
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
