Sounds like your RA returns e.g. OCF_ERR_ARGS or similar where it
shouldnt.
Try starting the resource with crm_resource and add -VV which should
show you the code as it's being run.
On 22/07/19 13:55 +0200, Ulrich Windl wrote:
Hi!
Playing with some new RA that won't start, I found this in crm_resource's man:
-Y, --why
Show why resources are not running, optionally filtered by
--resource and/or --node
When I tried it, all I got was:
# crm_resource -r prm_idredir_test -Y
Resource prm_idredir_test is not running
8-( Not quite what I expected. ANothger command gave me:
prm_idredir_test_start_0 on h02 'invalid parameter' (2): call=76,
status=complete, exitreason='', last-rc-change='Mon Jul 22 13:06:45 2019',
queued=0ms, exec=27ms
Unfortunately the last resource cleanup was significantly_after_ the time
logged above, and it seems the CRM did not even tre-try to start the RA.
Could this be a bug in SLES12 SP4
(pacemaker-1.1.19+20181105.ccd6b5b10-3.10.1.x86_64)?
Regards,
Ulrich
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
