I was so taken up by configuration parameters that i didn't checked
those parameters names was correctly typed
(i didn't use the console directly, but update a cib dump with
"configure load update /pat/mycib". So i didn't had the reflex to use
auto-completion).
I have to wait the full resync
On Jul 7, 2010, at 11:41 AM, Guillaume Chanaud wrote:
> I already tried the
>
> no_quorum-policy="ignore"
> which has no effect
>
> I just retried when reading your mail and resources doesn't migrate.
> In fact even if i boot only one server, this one won't promote the resources
> until the se
I already tried the
no_quorum-policy="ignore"
which has no effect
I just retried when reading your mail and resources doesn't migrate.
In fact even if i boot only one server, this one won't promote the resources
until the second is up...which is far from HA ;)
Guillaume
On Mon, Jul 05, 201
On Mon, Jul 05, 2010 at 12:41:05PM +0200, Guillaume Chanaud wrote:
> Hello,
>
> i searched the list, tried lots of things but nothing works, so i
> try to post here.
> I'd like to say my configuration worked on heartbeat2/crm, but since
> i migrated to corosync/pacemaker i have a problem.
> Here
I see you have {symmetric-cluster="true"} in your config. But you
haven't set up any location constraints.
Check the log (usually /var/log/messages unless specified otherwise)
with tailf while you're setting one node offline. It should give all the
relevant information about why the resources
Hello,
i searched the list, tried lots of things but nothing works, so i try to
post here.
I'd like to say my configuration worked on heartbeat2/crm, but since i
migrated to corosync/pacemaker i have a problem.
Here is my cib :
node filer1 \
attributes standby="off"
node filer2 \