Le Monday 24 October 2011 14:02:21 Joey L, vous avez écrit : > Okay..I was able to get my server back to its original problem state: > here is what i have installed: > > root@deb1:/etc/ha.d# dpkg -l |grep pacemaker > ii pacemaker 1.0.9.1+hg15626-1 > HA cluster resource manager > root@deb1:/etc/ha.d# dpkg -l |grep heartbeat > ii heartbeat 1:3.0.3-2 > Subsystem for High-Availability Linux > ii libheartbeat2 1:3.0.3-2 > Subsystem for High-Availability Linux (libraries) > ii libheartbeat2-dev 1:3.0.3-2 > Subsystem for High-Availability Linux (development files) > root@deb1:/etc/ha.d# dpkg -l |grep corosync > ii corosync 1.2.1-4 > Standards-based cluster framework (daemon and modules) > ii libcorosync-dev 1.2.1-4 > Standards-based cluster framework (developer files) > ii libcorosync4 1.2.1-4 > Standards-based cluster framework (libraries) > > Can not really tell if i am using heartbeat 1 or 2...it looks like it > is 2 by the lib files but debian package says ver. 1.
I'd say version 3 (1:3.0.3-2).
But you have heartbeat and corosync installed, you must choose only one (I'd
choose corosync).
> When i run the corosync command, i get this :
> root@deb1:/etc/ha.d# crm_mon --one-shot
> ============
> Last updated: Mon Oct 24 07:57:32 2011
> Stack: openais
> Current DC: deb1 - partition with quorum
> Version: 1.0.9-74392a28b7f31d7ddc86689598bd23114f58978b
> 2 Nodes configured, 2 expected votes
> 1 Resources configured.
> ============
>
> Online: [ deb1 deb2 ]
>
>
> Failed actions:
> failover-ip_start_0 (node=deb1, call=3, rc=1, status=complete):
> unknown error
> failover-ip_start_0 (node=deb2, call=41, rc=1, status=complete):
> unknown error
>
>
> when i run the command you said earlier, i get this:
[...]
cibadmin is less readable than crm configure show.
Here is mine, truncated and anonymised to show only one IPaddr resource :
root@node1:~# crm configure show
node node1 \
attributes standby="off"
node node2 \
attributes standby="off"
primitive res_IPaddr2_res1 ocf:heartbeat:IPaddr2 \
params ip="A.B.C.D" \
operations $id="res_IPaddr2_res1-operations" \
op start interval="0" timeout="20" \
op stop interval="0" timeout="20" \
op monitor interval="10" timeout="20" start-delay="0"
property $id="cib-bootstrap-options" \
expected-quorum-votes="2" \
dc-version="1.0.11-6e010d6b0d49a6b929d17c0114e9d2d934dc8e04" \
no-quorum-policy="ignore" \
cluster-infrastructure="openais" \
last-lrm-refresh="1316614496" \
stonith-enabled="false"
No clone primitive.
Side note : With 2 nodes and 2 votes, you'd better configure no-quorum-
policy="ignore", else, your resources won't start with only one node (and
then, why using a cluster !). The default config is good with at least 3
nodes.
> hope this helps..will try to get a clean syslog for you.
> thanks much for your efforts.
Yes, the syslog, while very verbose, can certainly tell us why the resource
does not start.
Are you sure that the IP address you configure in your failover-ip resource
can be brought up ? It's not already used or in another network ?
signature.asc
Description: This is a digitally signed message part.
