Heartbeat & configuração
Estou encontrado dificuldades para configurar o Heartbeat 1.2.3-9sarge6
no Debian 3.1 r3. Nas duas maquinas que uso no processo é apresentada a
seguinte mensagem:
#/etc/init.d/heartbeat start
...
Starting High-Availability services:
2006/09/21_11:25:22 CRITICAL: Resource drbddisk::drbd0 is active, and
should not be!
2006/09/21_11:25:22 CRITICAL: Non-idle resources can affect data integrity!
2006/09/21_11:25:22 info: If you don't know what this means, then get help!
2006/09/21_11:25:22 info: Read the docs and/or source to
/usr/lib/heartbeat/ResourceManager for more details.
CRITICAL: Resource drbddisk::drbd0 is active, and should not be!
CRITICAL: Non-idle resources can affect data integrity!
info: If you don't know what this means, then get help!
info: Read the docs and/or the source to
/usr/lib/heartbeat/ResourceManager for
more details.
2006/09/21_11:25:22 CRITICAL: Non-idle resources will affect resource
takeback!
2006/09/21_11:25:22 CRITICAL: Non-idle resources may affect data integrity!
Heartbeat failure [rc=6]. Failed.
heartbeat: 2006/09/21_11:25:22 ERROR: Heartbeat not started:
configuration error.
heartbeat: 2006/09/21_11:25:22 ERROR: Configuration error, heartbeat not
started.
...
No caso, o primeiro recurso listado é o drbd, mas quando o primeiro
recurso listado era, por exemplo, o IP, a mesma estrutura da mensagem
era mostrada.
o haresources tem os seguintes comandos:
micro1 drbddisk::drbd0 apache2 IPaddr::10.209.5.43/16/eth0
micro2 drbddisk::drbd1 samba IPaddr::10.209.5.36/16/eth0
o ha.cf tem os seguintes comandos:
logfacility daemon
logfile /var/log/ha-log
node micro1 micro2
keepalive 1
deadtime 10
ucast eth1 192.168.0.1
ping 10.209.5.254
ping_group 10.209.5.254
auto_failback off
respawn hacluster /usr/lib/heartbeat/ipfail
apiauth ipfail gid=haclient uid=hacluster
o hosts tem o seguinte:
127.0.0.1 localhost.localdomain localhost micro2
10.209.5.43 micro1.mec.gov.br micro1
10.209.5.36 micro2.mec.gov.br micro2
192.168.0.1 micro1
192.168.0.2 micro2
O que pode estar ocasionando esse problema.
Reply to: