On Tuesday 11 February 2003 19:22, Ariz Jacinto wrote: > someone from plug did ask me for this config. > post ko na rin dito coz others may find it useful: > > > what the heck is LinuxHA anyway? > > - it's like when your web server is down then > automatically another web server will > take its place. it's also like a _UPS_ > for services. >
sorry for asking but is this similar to heartbeat? > (applicable also to smtp, imap, samba, > postgres, proxy, ltsp, etc) > > > > > (1) The first thing you'll need is two computers, > having 1 NIC for each. > > *You need _not_ have identical hardware in both machines. > but they should have identical _services_ ( httpd, mysqld, smtp). > > > > (2) IPadd Assignments > > - Master Node 1 (node_1.linux.com.ph): 192.168.1.11 > - Slave Node 2 (node_2.linux.com.ph): 192.168.1.22 > - Cluster's IP: 192.168.1.33 > > > *node names should be the same with the output of the command > > shell> uname -n > > for each machine. > > > > > (3) Install LinuHA's "heartbeat" > > - http://www.linux-ha.org/download/ > > > > (4) Copy the following 3 config files > to /etc/ha.d of _all the nodes > (node_1.linux.com.ph & node_2.linux.com.ph) > *they should all have identical config files > > - ha.cf > - haresources > - authkeys > > > > --------- haresources --------------------- > > > node_1.linux.com.ph 192.168.1.33 > > > ------------------------------------------- > ------------- ha.cf ----------------------- > > > debugfile /var/log/ha-debug > logfile /var/log/ha-log > logfacility local0 > keepalive 1 > deadtime 5 > initdead 60 > udpport 694 > udp eth0 > mcast eth0 225.0.0.1 694 1 1 > node node_1.linux.com.ph > node node_2.linux.com.ph > > > ------------------------------------------ > ------- authkeys ------------------------- > > > auth 1 > 1 crc > > > ------------------------------------------ > > > > > > (5) Start the LinuxHA's daemon > > shell> service heartbeat start > > > > > (6) Test: > > Telnet, ftp, http, etc the cluster and verify > that you're on "node_1.linux.com.ph" > > Take down node_1.linux.com.ph. > (ie Kill power, kill heartbeat, yank UTP) > > Now ping the cluster's IP (192.168.1.33). > Approximately 1-10 seconds later it should > start responding again. > > you can Telnet, ftp, http, etc the cluster and verify > that you're now on "node_2.linux.com.ph" > > If it happens but takes more like 30 seconds, > something is wrong. view the log file for debugging. > > > > > goodluck!!!! > > > > > > > _ > Philippine Linux Users Group. Web site and archives at > http://plug.linux.org.ph To leave: send "unsubscribe" in the body to > [EMAIL PROTECTED] > > Fully Searchable Archives With Friendly Web Interface at > http://marc.free.net.ph > > To subscribe to the Linux Newbies' List: send "subscribe" in the body to > [EMAIL PROTECTED] _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
