see any of
them.
No luck with pcs as well.
Don't have this problem on Ubuntu 14.04.
Does anybody know why this thing could happen ?
Thank you!
Regards,
Sergey Arlashin
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clu
Is it
something that normally can happen? Or is it happening because of the shortage
of computing power which i described earlier? : )
How can I prevent a thing like this from happening? Is it a case which normally
is supposed to be solved by STONITH?
Thanks
Sorry, my fault. Forgot to include /usr/lib/lcrso/pacemaker.lcrso in my deb
package.
--
Best regards,
Sergey Arlashin
On Jan 7, 2015, at 2:18 PM, Sergey Arlashin
wrote:
> After installing 1.1.12 on one of my nodes in staging environment I see the
> following error in corosy
using).
--
Best regards,
Sergey Arlashin
On Jan 7, 2015, at 5:22 AM, Andrew Beekhof wrote:
>
>> On 7 Jan 2015, at 7:58 am, Sergey Arlashin
>> wrote:
>>
>> And one more question - can pacemaker 1.1.12 be used together with corosync
>> 1.4.7 ?
>
>
And one more question - can pacemaker 1.1.12 be used together with corosync
1.4.7 ? Or do I need to install corosync 2.x ?
--
Best regards,
Sergey Arlashin
On Jan 6, 2015, at 11:04 AM, Sergey Arlashin
wrote:
> Thank you!
> I'll try 1.1.12.
>
> --
> Best regard
Thank you!
I'll try 1.1.12.
--
Best regards,
Sergey Arlashin
On Jan 6, 2015, at 3:23 AM, Andrew Beekhof wrote:
> Yeah, I can imagine 1.1.6 behaving like this.
> I'd highly recommend 1.1.12
>
>> On 5 Jan 2015, at 5:14 pm, Sergey Arlashin
>> wrote:
>>
Pacemaker 1.1.6
It runs on Ubuntu 12.04 LTS 64bit.
Linux lb-node1 3.11.0-23-generic #40~precise1-Ubuntu SMP Wed Jun 4 22:06:36 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
--
Best regards,
Sergey Arlashin
On Jan 5, 2015, at 7:59 AM, Andrew Beekhof wrote:
> pacemaker version? it lo
rocesses with ps I found out that on all my nodes
there are zombie corosync procs like:
root 13892 0.0 0.0 0 0 ?ZDec26 0:04 [corosync]
root 21793 0.0 0.0 0 0 ?ZDec26 0:00 [corosync]
root 27009 1.3 1.0 714292 10784 ?
