> you could probably find the "stop" action in the > RA and replace it with (e.g.) "logger 'AIEEEEE ***I did not > want this***'" and then see what gets logged. > > --
Well, that worked, in the sense that the resource now fails over. I replaced the start and stop actions in the RA with logger commands. Now when I do 'crm node standby' on the primary, I get the following in the messages log (since there are two drbd resources): Dec 5 12:23:49 ha09b root: STOP action disabled Dec 5 12:23:51 ha09b root: STOP action disabled Dec 5 12:24:22 ha09b root: START action disabled Dec 5 12:24:25 ha09b root: START action disabled The resource then fails over, though it takes maybe 30 seconds to complete. I confirmed that /proc/drbd now shows the correct status on both nodes. I was able to repeat this back and forth a few times just to be sure. When one node is offline, crm_mon shows that the resources are stopped (which they actaully are NOT). Sigh. The RA is clearly not working right, but I don't know if that is the root cause of the failover problems or just a symptom of it. Now what? --Eric Disclaimer - December 5, 2012 This email and any files transmitted with it are confidential and intended solely for General Linux-HA mailing list. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
