Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Wed, Aug 03, 2005 at 09:32:20AM +0200, Rainer Rohde, E3T IT-Systems wrote: > 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 > With heartbeat-1.2.3 on Debian sarge I have something like: node1 drbddisk::r0 Filesystem::/dev/drbd0::/mnt/drbd0::ext3 node2 where I understand the syntax to be nodename resource resource ... nodename where the nodenames are as specified in your ha.cf which means something along the lines that drbddisk::r0 and the mounted filesystem of it Filesystem::/dev/drbd0::/mnt/drbd0::ext3 are a resource group that must be failed over together, and the filsystem depends on the drbddisk. If I continue to add resources on that line then each added resource depends on the one to its left. At standby from node1 to node2 heartbeat will do something like node1# /etc/heartbeat/resource.d/Filesystem::/dev/drbd0::/mnt/drbd0::ext3 stop node1# /etc/heartbeat/resource.d/drbddisk::r0 stop node2# /etc/heartbeat/resource.d/drbddisk::r0 start node2# /etc/heartbeat/resource.d/Filesystem::/dev/drbd0::/mnt/drbd0::ext3 start so you can try out the steps you've specified very easily. on the system I'm looking at the mountpoint is not an optional parameter. those scripts in turn do something like node1# umount /mnt/drbd0 node1# drbdadm secondary r0 node2# drbdadm primary r0 node2# mount /dev/drbd0 /mnt/drbd0 You can find out the details by reading them. Hope this helps Regards, Paddy -- Perl 6 will give you the big knob. -- Larry Wall