26.06.2013, 06:41, "Andrew Beekhof" :
> On 26/06/2013, at 3:01 AM, Denis Witt
> wrote:
>
>> On Tue, 25 Jun 2013 17:12:15 +0200
>> Denis Witt wrote:
>>> ./configure runs fine, but make didn't. I don't remember the exact
>>> error message and before I could run it again I have to solve my
>>
On 26/06/2013, at 3:01 AM, Denis Witt
wrote:
> On Tue, 25 Jun 2013 17:12:15 +0200
> Denis Witt wrote:
>
>> ./configure runs fine, but make didn't. I don't remember the exact
>> error message and before I could run it again I have to solve my
>> OCFS2-Problem. But I'll try again and post it he
- Original Message -
> From: "Denis Witt"
> To: pacemaker@oss.clusterlabs.org
> Cc: "Jake Smith"
> Sent: Tuesday, June 25, 2013 11:47:36 AM
> Subject: Re: [Pacemaker] ERROR: Wrong stack o2cb
>
> On Tue, 25 Jun 2013 11:37:15 -0400 (EDT)
> Jake Smith wrote:
>
> > You probably already
On Tue, 25 Jun 2013 17:12:15 +0200
Denis Witt wrote:
> ./configure runs fine, but make didn't. I don't remember the exact
> error message and before I could run it again I have to solve my
> OCFS2-Problem. But I'll try again and post it here.
Hi Andrew,
last time I didn't had rpm installed and
On Tue, 25 Jun 2013 11:37:15 -0400 (EDT)
Jake Smith wrote:
> You probably already know but you're going to get failed "not
> installed" from test4 always unless you install the same packages
> there.
>
> Do you have logs from test4-node[1|2] that are generating the not
> installed for o2cb? The
On Tue, 25 Jun 2013 17:31:49 +0200
emmanuel segura wrote:
> If you use ocfs with pacemaker, you don't need to configure ocfs in
> legacy mode using /etc/ocfs2/cluster.conf
Hi,
I just added the cluster.conf to be able to run tunefs.ocfs2. It
doesn't matter if it is present or not, the error is t
- Original Message -
> From: "Denis Witt"
> To: pacemaker@oss.clusterlabs.org
> Sent: Tuesday, June 25, 2013 11:08:36 AM
> Subject: [Pacemaker] ERROR: Wrong stack o2cb
>
> Hi List,
>
> I'm having trouble getting OCFS2 running. If I run everything by hand
> the OCFS-Drive works quite w
Hello Denis
If you use ocfs with pacemaker, you don't need to configure ocfs in legacy
mode using /etc/ocfs2/cluster.conf
Thanks
Emmanuel
2013/6/25 Denis Witt
> Hi List,
>
> I'm having trouble getting OCFS2 running. If I run everything by hand
> the OCFS-Drive works quite well, but cluster in
Hi List,
I'm having trouble getting OCFS2 running. If I run everything by hand
the OCFS-Drive works quite well, but cluster integration doesn't work
at all.
The Status:
Last updated: Tue Jun 25 17:00:49 2013
Last change: Tue Jun 25 16:58:03 2013 via crmd on test4
Stack: openais
Curr
On Tue, 25 Jun 2013 10:39:30 +1000
Andrew Beekhof wrote:
> > @andrew: I know I owe you some informations about the Problem we
> > discussed earlier on this list but at the moment i'm unable to
> > compile the current Pacemaker Version, Sorry.
> Details?
Hi Andrew,
./configure runs fine, but
On 06/25/2013 07:29 AM, andreas graeper wrote:
> hi,
> maybe again and again the same question, please excuse.
>
> two nodes (n1 active / n2 passive) and `service corosync stop` on active.
> does the node, that is going down, tells the other that he has gone,
> before he actually disconnect ?
> so
Hi all!
I am setting up a new cluster on OracleLinux 6.4 (well, it is CentOS 6.4).
I went through http://clusterlabs.org/quickstart-redhat.html
Then I installed DRBD 8.4.2 from elrepo.
This setup is unusable :-( with DRBD 8.4.2.
I created three DRBD resources:
cat /proc/drbd
version: 8.4.2 (api:1
On Tue, 25 Jun 2013 20:24:00 +1000
Andrew Beekhof wrote:
> On 25/06/2013, at 5:56 PM, Jacek Konieczny wrote:
>
> > On Tue, 25 Jun 2013 10:50:14 +0300
> > Vladislav Bogdanov wrote:
> >> I would recommend qb 1.4.4. 1.4.3 had at least one nasty bug which
> >> affects pacemaker.
> >
> > Just tried
Andrew,
Does Pacemaker support GPU processes?
R,
CB
The information contained in this transmission may contain privileged and
confidential information.
It is intended only for the use of the person(s) named above.
If you are not the intended recipient, you are hereby notified that any review,
Il 25/06/2013 12.32, Andrew Beekhof ha scritto:
> On 25/06/2013, at 5:37 PM, Francesco Namuri wrote:
>
>> Hi,
>> after an update to the new debian stable, from pacemaker 1.0.9.1 to
>> 1.1.7 I'm getting some strange errors on syslog:
> Thats a hell of a jump there.
Yes,
I know... :)
thank you for
hi,
maybe again and again the same question, please excuse.
two nodes (n1 active / n2 passive) and `service corosync stop` on active.
does the node, that is going down, tells the other that he has gone, before
he actually disconnect ?
so that there is no reason for n2 to kill n1 ?
on n2 after n1.
On 25/06/2013, at 5:37 PM, Francesco Namuri wrote:
> Hi,
> after an update to the new debian stable, from pacemaker 1.0.9.1 to
> 1.1.7 I'm getting some strange errors on syslog:
Thats a hell of a jump there.
Can you attach /var/lib/pengine/pe-input-64.bz2 from SERVERNAME1 please?
I'll be able
On 25/06/2013, at 6:32 PM, Lars Marowsky-Bree wrote:
> On 2013-06-25T10:16:58, Andrey Groshev wrote:
>
>> Ok, I recently became engaged in the PСMK, so for me it is a surprize.
>> The more so in all the major linux distributions version 1.1.х.
>
> Pacemaker has very strong regression and syst
On 25/06/2013, at 5:56 PM, Jacek Konieczny wrote:
> On Tue, 25 Jun 2013 10:50:14 +0300
> Vladislav Bogdanov wrote:
>> I would recommend qb 1.4.4. 1.4.3 had at least one nasty bug which
>> affects pacemaker.
>
> Just tried that. It didn't help.
Can you turn on the blockbox please?
Details at h
On 2013-06-25T10:16:58, Andrey Groshev wrote:
> Ok, I recently became engaged in the PСMK, so for me it is a surprize.
> The more so in all the major linux distributions version 1.1.х.
Pacemaker has very strong regression and system tests, and barring
accidents, it is usually very safe to always
25.06.2013, 09:32, "Andrey Groshev" :
> 22.06.2013, 21:32, "Lars Marowsky-Bree" :
>
>> On 2013-06-21T14:30:42, Andrey Groshev wrote:
>>> I was wrong - the resource starts in 15 minutes.
>>> I found a matching entry in the log at the same time:
>>> grep '11:59.*900' /var/log/cluster/coros
25.06.2013 10:50, Vladislav Bogdanov wrote:
> 25.06.2013 09:59, Jacek Konieczny wrote:
>> On Tue, 25 Jun 2013 16:43:54 +1000
>> Andrew Beekhof wrote:
>>>
>>> Ok, I was just checking Pacemaker was built for the running version
>>> of libqb.
>>
>> Yes it was. corosync 2.2.0 and libqb 0.14.0 both on
On Tue, 25 Jun 2013 10:50:14 +0300
Vladislav Bogdanov wrote:
> I would recommend qb 1.4.4. 1.4.3 had at least one nasty bug which
> affects pacemaker.
Just tried that. It didn't help.
Jacek
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
htt
On Tue, 25 Jun 2013 08:59:19 +0200
Jacek Konieczny wrote:
> On Tue, 25 Jun 2013 16:43:54 +1000
> Andrew Beekhof wrote:
> >
> > Ok, I was just checking Pacemaker was built for the running version
> > of libqb.
>
> Yes it was. corosync 2.2.0 and libqb 0.14.0 both on the build system
> and on the
25.06.2013 09:59, Jacek Konieczny wrote:
> On Tue, 25 Jun 2013 16:43:54 +1000
> Andrew Beekhof wrote:
>>
>> Ok, I was just checking Pacemaker was built for the running version
>> of libqb.
>
> Yes it was. corosync 2.2.0 and libqb 0.14.0 both on the build system and
> on the cluster systems.
I wo
Hi,
after an update to the new debian stable, from pacemaker 1.0.9.1 to
1.1.7 I'm getting some strange errors on syslog:
Jun 25 09:20:01 SERVERNAME1 cib: [4585]: info: cib_stats: Processed 29
operations (344.00us average, 0% utilization) in the last 10min
Jun 25 09:20:22 SERVERNAME1 lrmd: [4587]:
On Tue, 25 Jun 2013 16:43:54 +1000
Andrew Beekhof wrote:
>
> Ok, I was just checking Pacemaker was built for the running version
> of libqb.
Yes it was. corosync 2.2.0 and libqb 0.14.0 both on the build system and
on the cluster systems.
Hmm… I forgot libqb is a separate package… I guess I shou
27 matches
Mail list logo
