Hi!
My old RAs include /usr/lib/ocf/resource.d/heartbeat/.ocf-shellfuncs. Recently
I discovered /usr/lib/ocf/lib/heartbeat/ocf-shellfuncs.
(I wonder whether the latter shouldn't be /usr/lib/ocf/ocf-shellfuncs simply)
So what is the recommended path to use for include? If RAs continue to use the
Hi!
As suggested I'm considering to replace all "ocf_log err ..." preceeding an
error exit code with "ocf_exit_reason ..." in my OCF RA.
However I have a question: Is it OK to call ocf_exit_reason more than once
before actually exiting? I assume the last message being used will be the one
displ
>>> Ken Gaillot schrieb am 22.07.2019 um 18:14 in
>>> Nachricht
:
> On Mon, 2019-07-22 at 15:45 +0200, Ulrich Windl wrote:
>> Hi!
>>
>> My RA actually sends OCF_ERR_ARGS if checking the args detects a
>> problem.
>> But as the error can be resolved sometimes without changing the args
>> (eg.
>>
Gentle Reminder!!
On Wed, Jul 17, 2019 at 1:14 PM Rohit Saini
wrote:
> Gentle Reminder!!
>
> On Mon, Jul 15, 2019 at 12:10 PM Rohit Saini <
> rohitsaini111.fo...@gmail.com> wrote:
>
>> Hi All,
>>
>> I know pacemaker booth is being used for geographical redundancy.
>> Currently I am using pacemak
On Mon, 2019-07-22 at 15:45 +0200, Ulrich Windl wrote:
> Hi!
>
> My RA actually sends OCF_ERR_ARGS if checking the args detects a
> problem.
> But as the error can be resolved sometimes without changing the args
> (eg.
> providing some resource by other means), I suspect CRM does not
> handle that
Hi!
My RA actually sends OCF_ERR_ARGS if checking the args detects a problem.
But as the error can be resolved sometimes without changing the args (eg.
providing some resource by other means), I suspect CRM does not handle that
properly. Even after a resource cleanup.
My RA logs any parameter che
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_
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