>>>crm configure primitive iptables lsb::iptables op monitor interval=10s
> o/p is
>
> ERROR: lsb:cups: could not parse meta-data:
> ERROR: lsb:iptables: could not parse meta-data:
> ERROR: lsb:iptables: could not parse meta-data:
> ERROR: lsb:iptables: no such resource agent
> Do you still want to
Hi!
We also had the strange effect that ocf:heartbeat:IPaddr2 monitors time out
when there was significant disk write activity (we used 30s timeouts). I always
expected these monitors to be in the buffer cache, so essentially they should
be executed without delay and quite efficiently. I never
2011/12/12, Andrew Beekhof :
> On Fri, Dec 9, 2011 at 7:46 PM, Aleksey V. Kashin
> wrote:
>>> How much do they have now?
>>
>> They have 12G RAM.
>
> That seems respectable.
>
>>
>>> How much is in use by the radius servers?
>>
>> total used free sharedbuffers
Hi!
As nobody answered (FAIR), I'm replying to my own message: As it turned out,
there's a comment somewhere in the LRM sources that states "this part isn't
implemented yet".
Once it is implemented (maybe even before), the CRM shell could benefit from a
"crm resource reload .." (currently ther
Hi,
On Mon, Dec 12, 2011 at 9:42 AM, sony thapa wrote:
>>
>> Hi,
>
> When I am trying to add lsb resource agent, through crm interface
>
>>>crm configure primitive iptables lsb::iptables op monitor interval=10s
> o/p is
>
> ERROR: lsb:cups: could not parse meta-data:
> ERROR: lsb:iptables: could
its a two node cluster with online updates.
grpSAPINSTresources is a group that runs on node2, while
grpSAPDBresources is another group that runs on node1.
clone-grpDlmO2cb and clone-grpSharedFS are clone resources that runs on
both nodes, and is a must for grpSAPDBresources and grpSAPINSTresource
