Hi Jiaju,
2012/12/18 Jiaju Zhang :
> On Mon, 2012-12-17 at 10:40 +0900, Yuichi SEINO wrote:
>> Hi Jiaju,
>>
>> >> >>
>> >> >> Perhaps, this problem didn't happen before the following commit.
>> >> >> https://github.com/jjzhang/booth/commit/4b00d46480f45a205f2550ff0760c8b372009f7f
>> >> >
>> >> >
> >
> > Any cib change throws the system load up for 10-20 seconds, and then
> > things start timing out, despite having set the timeouts well in excess of
> > the
> > time it takes for pacemaker to mark the resource as timed out.
>
> Hmm, unless your CIB (the configuration) is really huge, that
I may be doing the impossible trying to get a pacemaker+corosync cluster to
work on Centos 5.8 building from source. I have some system constraints I
cannot ignore.
Corosync finds the nodes just fine. (kslinux1, kslinux2) SELinux and the
firewall is turned off.
Pacemakerd starts just fine on
- Original Message -
> From: "Attila Megyeri"
> To: "The Pacemaker cluster resource manager"
>
> Sent: Thursday, December 20, 2012 3:07:06 PM
> Subject: Re: [Pacemaker] Clone resource as a dependency
> Thanks Jake,
> I did not try with the collocation constraint as the clone was
> runn
Thanks Jake,
I did not try with the collocation constraint as the clone was running on all
nodes, but I will give it a try – not sure whether this would work with a clone.
I am using pacemaker 1.1.6 on a debian system, the critical RAs are from latest
github. The cluster is assymetric.
The conf
A collocation constraint as well as the order so it must run on the same node
as a running clone might do it. Not quite sure with the clone though.
Doc reference would require some more info such as what version of pacemaker,
etc.
Including configuration helps get answers quicker.
HTH
Is this so difficult or so trivial, that no one responded? :)
I would appreciate a reference to some documentation as well.
Thank you,
Attila
From: Attila Megyeri [mailto:amegy...@minerva-soft.com]
Sent: Wednesday, December 19, 2012 10:05 AM
To: The Pacemaker cluster resource manager
Subject: [P
- Original Message -
> From: "Jay Janssen"
> To: pacemaker@oss.clusterlabs.org
> Sent: Tuesday, December 18, 2012 1:19:18 PM
> Subject: [Pacemaker] crm shell
>
>
>
> Having learned pretty much everything I know about pacemaker (which
> isn't a lot) using the crm shell, I am dismayed t
Hi,
On Tue, Dec 18, 2012 at 02:19:18PM -0500, Jay Janssen wrote:
> Having learned pretty much everything I know about pacemaker (which isn't a
> lot) using the crm shell, I am dismayed to find it isn't included in
> pacemaker 1.1.8.
>
> Since when is it a good development practice to deprecat
On Thu, Dec 20, 2012 at 11:43:20AM +, James Harper wrote:
> > Hi,
> >
> > On Tue, Dec 18, 2012 at 10:58:18AM +, James Harper wrote:
> > > For the following failure:
> > >
> > > Failed actions:
> > > p_lvm_iscsi:0_monitor_1 (node=bitvs6, call=57, rc=-2,
> > > status=Timed Out): unkn
> Hi,
>
> On Tue, Dec 18, 2012 at 10:58:18AM +, James Harper wrote:
> > For the following failure:
> >
> > Failed actions:
> > p_lvm_iscsi:0_monitor_1 (node=bitvs6, call=57, rc=-2,
> > status=Timed Out): unknown exec error
> >
> > Is this the ra itself returning a "Timed Out" error, or
Thanks Soni,
I will discuss it with my professor.
Thanks,
Felipe
On Thu, Dec 20, 2012 at 12:26 AM, Soni Maula Harriz <
soni.har...@sangkuriang.co.id> wrote:
> bonding in network
--
*--
-- Felipe Oliveira Gutierrez
-- felipe.o.gutier...@gmail.com
-- https://sites.google.com/site/lipe82/Home
Hi,
On Tue, Dec 18, 2012 at 10:58:18AM +, James Harper wrote:
> For the following failure:
>
> Failed actions:
> p_lvm_iscsi:0_monitor_1 (node=bitvs6, call=57, rc=-2, status=Timed
> Out): unknown exec error
>
> Is this the ra itself returning a "Timed Out" error, or is it
> the clus
13 matches
Mail list logo
