's repos. But when
> I need a newer or more stable version of a software, I have to use it.
>
> Best regards
> Andreas
>
>
>
> Von: andreas graeper [mailto:agrae...@googlemail.com]
> Gesendet: Freitag, 21. Juni 2013 15:00
> An: The Pacemaker cluster resourc
.
Best regards
Andreas
Von: andreas graeper [mailto:agrae...@googlemail.com]
Gesendet: Freitag, 21. Juni 2013 15:00
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] known problem with corosync 1.4.1 on centos64 ?
hi,
> old version :
i shall maintain a centos
i forgot to ask the more important:
i used cleanup for wiping out the rest, that was left after i stopped and
deleted a resource.
when the resource (unmanaged) is anyhow still there, than a cleanup would
let pacemaker try to manage that resource again and start all the other
depending ( order / co
hi,
> old version :
i shall maintain a centos63 with, except drbd (build from source), only
standard-repos are used.
for testing i installed newest centos64, but .. .
there is no chance to get rid of that centos63, but for learning/testing
what are the best distros ? not in general, but for use wi
On 2013-06-21T10:56:29, andreas graeper wrote:
> hi,
> when only i remove or add resources, corosync starts to eat up all cpu.
> drbd 8.4.1 (build from source)
> corosync 1.4.1
yes, corosync 1.4.1 had one such error, I recall. If you're building
from source, why are you sticking to such an old v
hi,
when only i remove or add resources, corosync starts to eat up all cpu.
drbd 8.4.1 (build from source)
corosync 1.4.1
pacemaker 1.1.8
crmsh 1.2.5 (this from extra repo, cause crm is missing in pacemaker-cli ?!
but it is not reason for trouble ! i use pcs except crm_mon )
pcs 0.9.26
when
pc