Sooo.. I've been toying with setting up heartbeat a bit, and this is how
far I get: 


bash-2.05b# /etc/init.d/heartbeat start
Starting High-Availability services:
                                                           [FAILED]
heartbeat: 2005/08/03_09:30:37 info: Neither logfile nor logfacility
found.
heartbeat: 2005/08/03_09:30:37 info: Logging defaulting
to /var/log/ha-log
heartbeat: 2005/08/03_09:30:37 info: **************************
heartbeat: 2005/08/03_09:30:37 info: Configuration validated. Starting
heartbeat 1.2.3
heartbeat: 2005/08/03_09:30:37 ERROR: Bad nodename
in /usr/local/etc/ha.d/haresources [Filesystem::/dev/drbd0::ext3]
heartbeat: 2005/08/03_09:30:37 ERROR: Configuration error, heartbeat not
started.


--- Here's content of my haresources: 

openfiler 192.168.1.110 r0
Filesystem::/dev/drbd0::ext3



Of course, I am "winging" it here, as I don't understand the concept
enough to make sense from the syntax in the first place. 

Am I right, though, that the heartbeat is only started on one machine,
and all the configuration files for heartbeat pertain to that one
machine? 

Greets & thanks for your help, 
Rainer







On Tue, 2005-08-02 at 12:40 -0400, Diego Julian Remolina wrote:
> I sent you two files: DRBD-Howto and Heartbeat-Howto
> 
> Check the e-mail again.
> 
> Diego
> 
> On Tuesday 02 August 2005 11:30, Rainer Rohde, E3T IT-Systems wrote:
> > Thank you much! Now I got it to work and I am closer in understanding
> > the concept!
> >
> > Now, if you had a similar mini-howto to add "heartbeat" to the mix I'd
> > be set... :)
> >
> > Cheers,
> > Rainer
> >
> > On Tue, 2005-08-02 at 10:36 -0400, Diego Julian Remolina wrote:
> > > > ^^ is the above now a funtioning mirror? Or do I have to
> > > > mount /dev/drbd0 on the Secondary as well?
> > > >
> > > >
> > > > ^^ is the above now a funtioning mirror? Or do I have to
> > > > mount /dev/drbd0 on the Secondary as well?
> > >
> > > It looks good, but the only way for you to be totally convinced it is
> > > working is as follows (if you do not have heartbeat configured yet).
> > >
> > > 1. On openfiler while being drbd primary:
> > > touch /mnt/disk/file_created_on_openfiler
> > > umount /mnt/disk
> > >
> > > 2. On openfiler2 currently in secondary state:
> > > drbdadm primary YOUR_DRBD_DEVICE_NAME
> > > cat /proc/drbd and make sure that openfiler2 is now showing:
> > > 0: cs:Connected st:Primary/Secondary ld:Consistent
> > > which means that openfiler2 is now acting as drbd primary
> > > Now mount
> > > mkdir /mnt/disk
> > > mount /dev/drbd0 /mnt/disk
> > > ls /mnt/disk
> > > You should see the file:  file_created_on_openfiler
> > > So now create one from openfiler2:
> > > touch /mnt/disk/file_created_on_openfiler2
> > > umount /mnt/disk
> > >
> > > 3. Back on openfiler, make it be drbd primary:
> > > drbdadm primary YOUR_DRBD_DEVICE_NAME
> > > cat /proc/drbd and make sure that openfiler is now showing:
> > > 0: cs:Connected st:Primary/Secondary ld:Consistent
> > > now
> > > mount /dev/drbd0 /mnt/disk
> > > ls /mnt/disk
> > >
> > > Now you should see the two files:
> > > file_created_on_openfiler
> > > file_created_on_openfiler2
> > >
> > > Voila, you just switched machines and wrote to their own file systems
> > > which got replicated to the other machine trhough drbd.
> > >
> > > Note you can NOT have a drbd device mounted on the secondary machine
> > > while it is on drbd Secondary state, not even read only.  The only way
> > > you can mount it is when the device shows as drbd primary on that
> > > machine.
> > >
> > > HTH,
> > >
> > > Diego
> > >
> > > -------------------------------------------------
> > > This mail sent through IMP: http://horde.org/imp/
> >
> > Rainer A. Rohde
> > Linux Support
> >
> > E3T IT-Systems GmbH | www.e3t.net
> > Tel.: 0651-840710 | Fax: 0651-84071-119 | r.rohde@e3t.net
Rainer A. Rohde  
Linux Support

E3T IT-Systems GmbH | www.e3t.net
Tel.: 0651-840710 | Fax: 0651-84071-119 | r.rohde@e3t.net