On 11/30/2012 01:08 PM, Rodrigo Abrantes Antunes wrote:
> Hi, I'm new to heartbeat, just started to read about it a week ago. I'm
> using ubuntu, I installed heartbeat 2.1.4 in my two nodes. Here is ha.cf of
> them:
> 
>   logfacility local0
>   keepalive 2
>   deadtime 5
>   udpport 694
>   bcast   eth5
>   auto_failback on
>   node    node1
>   node    node2

I think you may need "crm no" as well.

What's your eth5 connected to?

>   And here is haresources (I'm testing only apache, the ip address don't
> matter):
>   node1 apache2
> 
>   I stoped heartbeat service in node1 and then apache started in node2 ,
> then I started heartbeat service in node1 and apache started in node1 but
> stayed active in node2. Shouldn't the one in node2 be stopped?

Yes it should be. Read the logs ("tail -f" on one console while stopping
heartbeat on another).

 Another
> question: If I stop apache service in one node it don't start in the other
> node, shouldn't it be started since apache is down? How heartbeat monitors
> the process to see if it is down or up?

No because in your configuration heartbeat doesn't monitor services.
Install mon and write a custom alert script that does
 /usr/share/heartbeat/hb_standby all
when process dies.

> What I want to ask is wich
> one is the best to syncronize ALL data between the 2 nodes including data
> that may be in use

Simple setup: put it all on one filesystem and put that on DRBD. See
http://www.drbd.org/users-guide-8.3/s-heartbeat-r1.html

Also recommended: drbdlinks.

HTH
-- 
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to