Forum

quorum {

provider: corosync_votequorum

expected_votes: 2

}

Salut,



je n'ai pas eu le temps de tester.



Donc je laisse vide cette section?

crm configure property stonith-enabled=false

crm configure primitive FAILOVER-ADDR ocf:heartbeat:IPaddr2 params ip="192.168.56.200" nic="eth0" op monitor interval="10s" meta is-managed="true"

[root@info01 adrien]# rpm -qa | grep corosync; rpm -qa | grep pacemaker

corosync-2.0.0-3.mga2

lib64corosync4-2.0.0-3.mga2

pacemaker-1.1.7-2.mga2

[root@info01 adrien]# cat /etc/corosync/corosync.conf

# Please read the corosync.conf.5 manual page

aisexec {

user: root

group: root

}



totem {

version: 2



# cypto_cipher and crypto_hash: Used for mutual node authentication.

# If you choose to enable this, then do remember to create a shared

# secret with "corosync-keygen".

crypto_cipher: none

crypto_hash: none



# interface: define at least one interface to communicate

# over. If you define more than one interface stanza, you must

# also set rrp_mode.

interface {

# Rings must be consecutively numbered, starting at 0.

ringnumber: 0

# This is normally the *network* address of the

# interface to bind to. This ensures that you can use

# identical instances of this configuration file

# across all your cluster nodes, without having to

# modify this option.

bindnetaddr: 192.168.1.0

# However, if you have multiple physical network

# interfaces configured for the same subnet, then the

# network address alone is not sufficient to identify

# the interface Corosync should bind to. In that case,

# configure the *host* address of the interface

# instead:

bindnetaddr: 192.168.1.0

# When selecting a multicast address, consider RFC

# 2365 (which, among other things, specifies that

# 239.255.x.x addresses are left to the discretion of

# the network administrator). Do not reuse multicast

# addresses across multiple Corosync clusters sharing

# the same network.

mcastaddr: 226.94.1.1

# Corosync uses the port you specify here for UDP

# messaging, and also the immediately preceding

# port. Thus if you set this to 5405, Corosync sends

# messages over UDP ports 5405 and 5404.

mcastport: 4000

# Time-to-live for cluster communication packets. The

# number of hops (routers) that this ring will allow

# itself to pass. Note that multicast routing must be

# specifically enabled on most network routers.

ttl: 1

}

}



logging {

# Log the source file and line where messages are being

# generated. When in doubt, leave off. Potentially useful for

# debugging.

fileline: off

# Log to standard error. When in doubt, set to no. Useful when

# running in the foreground (when invoking "corosync -f")

to_stderr: no

# Log to a log file. When set to "no", the "logfile" option

# must not be set.

to_logfile: yes

logfile: /var/log/cluster/corosync.log

# Log to the system log daemon. When in doubt, set to yes.

to_syslog: yes

# Log debug messages (very verbose). When in doubt, leave off.

debug: off

# Log messages with time stamps. When in doubt, set to on

# (unless you are only logging to syslog, where double

# timestamps can be annoying).

timestamp: on

logger_subsys {

subsys: QUORUM

debug: off

}

}



quorum {

# Enable and configure quorum subsystem (default: off)

# see also corosync.conf.5 and votequorum.5

#provider: corosync_votequorum

}

# crm_mon

============

Last updated: Thu Aug 27 16:54:55 2009Stack: openais

Current DC: pcmk-1 - partition with quorum

Version: 1.1.5-bdd89e69ba545404d02445be1f3d72e6a203ba2f

2 Nodes configured, 2 expected votes

0 Resources configured.

============

Online: [ pcmk-1 pcmk-2 ]

[root@info01 service.d]# crm_mon

============

Last updated: Wed Jul 4 23:05:56 2012

Last change:

Current DC: NONE

0 Nodes configured, unknown expected votes

0 Resources configured.

============

Jul 4 23:50:09 info02 rsyslogd-2177: imuxsock lost 120 messages from pid 2245 due to rate-limiting

Jul 4 23:50:09 info02 pacemakerd[2245]: notice: update_node_processes: 0x2441330 Node 3372329152 now known as info01, was:

Jul 4 23:50:09 info02 cib[2251]: info: crm_new_peer: Node info01 now has id: 3372329152

Jul 4 23:50:09 info02 cib[2251]: info: crm_new_peer: Node 3372329152 is now known as info01

Jul 4 23:50:09 info02 stonith-ng[2252]: info: crm_new_peer: Node info01 now has id: 3372329152

Jul 4 23:50:09 info02 stonith-ng[2252]: info: crm_new_peer: Node 3372329152 is now known as info01

Réponse de 192.168.1.200 : octets=32 temps<1ms TTL=64

Réponse de 192.168.1.200 : octets=32 temps<1ms TTL=64

Réponse de 192.168.1.200 : octets=32 temps<1ms TTL=64

Réponse de 192.168.1.200 : octets=32 temps<1ms TTL=64

Délai d'attente de la demande dépassé.

Délai d'attente de la demande dépassé.

Délai d'attente de la demande dépassé.

Délai d'attente de la demande dépassé.

Délai d'attente de la demande dépassé.

Réponse de 192.168.1.200 : octets=32 temps<1ms TTL=64

Réponse de 192.168.1.200 : octets=32 temps<1ms TTL=64

Réponse de 192.168.1.200 : octets=32 temps<1ms TTL=64