"crmd:error: plugin_dispatch:”
you’re using the plugin on a rhel6 based install.
don’t do that. you’ll need to use pacemaker with cman instead.
this happens automatically is you use 'pcs cluster create ...'
> On 14 Dec 2015, at 6:46 PM, Sahil Aggarwal wrote:
>
> Hello Team Pacemaker/Corosyn
On 16 Oct 2014, at 7:56 pm, Sahil Aggarwal wrote:
> Sorry, i didn't get your point and i am again re-iterating the problem:
>
> Two Node cluster Node A , Node B .
>
> Service X running on Node A, Node B is DC.
>
> We are using stack corosync with Pacemaker.
> Failure Timeout is 10 sec .
> T
On 16 Oct 2014, at 6:33 pm, Sahil Aggarwal wrote:
> Hello ,
>
> Yes that log might be due to that reason but , it should not ignore the
> resource as it is not taking any action for that resource i..e. not starting
> the resource .
it doesn't know that at the time
>
> and second thing
>
You don't think that might be a little short?
Any failure that happened more than 10s is going to be ignored, leading to the
pengine message you saw.
On 16 Oct 2014, at 12:21 am, Sahil Aggarwal wrote:
> failure timeout for resource is 10s.
>
> On Wed, Oct 15, 2014 at 2:51 AM, Andrew Beekhof
On 15 Oct 2014, at 4:23 am, Sahil Aggarwal wrote:
>
> Hello Team Pacemaker,
>
> I am facing a constant issue with Pacemaker, it does not restart the Service
> even when he knows that the Service is down. It generates a message saying
> "Ignoring Expired Failure" for the service.
What is th
