Rabbitmq OCF RA: Pacemaker reports a slave running and does nothing to the resource, but lrmd logs contain a periodic error from the 2nd monitor

Note, that is a floating issue, there is no 100% repro steps.

Pacemaker sometimes reports a slave running and does nothing to the resource, but lrmd logs contain a periodic error from the 2nd monitor and the rabbitmq app is not running w/o any recovery for a long time. Here is an example I caught by running a jepsen test against a rabbit cluster:

lrmd.log:
Apr 5 15:18:12 n1 lrmd: INFO: p_rabbitmq-server[11463]: get_monitor(): master exists and rabbit app is not running. Exiting to be restarted by pacemaker
Apr 5 15:18:12 n1 lrmd: ERROR: p_rabbitmq-server[11463]: get_monitor(): get_status() returns generic error 1
Apr 5 15:18:12 n1 lrmd: INFO: p_rabbitmq-server[11463]: get_monitor(): ensuring this slave does not get promoted.
Apr 5 15:18:12 n1 lrmd: INFO: p_rabbitmq-server[11463]: master_score(): Updating master score attribute with 0
... snip ...
Apr 5 15:18:49 n1 lrmd: INFO: p_rabbitmq-server[12636]: get_monitor(): master exists and rabbit app is not running. Exiting to be restarted by pacemaker
... snip (reoccurs every 35 sec as expected) ...
 Apr 5 15:27:30 n1 lrmd: INFO: p_rabbitmq-server[27111]: get_monitor(): master exists and rabbit app is not running. Exiting to be restarted by pacemaker
 Apr 5 15:28:08 n1 lrmd: INFO: p_rabbitmq-server[28063]: get_monitor(): master exists and rabbit app is not running. Exiting to be restarted by pacemaker
 Apr 5 15:28:33 n1 lrmd: INFO: p_rabbitmq-server[29010]: get_monitor(): master exists and rabbit app is not running. Exiting to be restarted by pacemaker

pacemaker.log:
 Apr 05 15:13:17 [30970] n1 crmd: notice: process_lrm_event: Operation p_rabbitmq-server_monitor_35000: unknown error (node=n1, call=171, rc=1, cib-update=27, confirmed=false)
 ... snip (no more logs about error exit code!) ...
 Apr 05 15:28:34 [30970] n1 crmd: notice: process_lrm_event: Operation p_rabbitmq-server_monitor_35000: unknown error (node=n1, call=174, rc=1, cib-update=30, confirmed=false)

So, pacemaker doesn't restart it, and doesn't "notice" errors.
But it recovers automagically ~15 min later!
 Apr 05 15:28:36 [30970] n1 crmd: info: do_lrm_rsc_op: Performing key=3:107:0:fd9993ea-2897-4c53-ae4c-bc30faf66315 op=p_rabbitmq-server_stop_0

The solution is to stop the rabbitmq server process instead of hoping on the being restarted by a Pacemaker...