On Thu, Aug 25, 2011 at 01:26:38PM -0400, Nick Khamis wrote: > Hello Everyone, > > I am new to LHA, so please bare with me. That being said, I do get the > general idea... > > A good place to begin is with the configuration files: > > <ldirectord.cf> > > #Global Directives > #checktimeout=10 > checkinterval=2 > autoreload=no > logfile="local0" > quiescent=yes > virtual = 192.168.2.100:3306 > service = mysql > real = 192.168.2.103:3306 gate > real = 192.168.2.104:3306 gate > checktype = negotiate > login = "ldirector" > passwd = "pass" > database = "ldirectordb" > request = "SELECT * FROM connectioncheck" > scheduler = wrr > > > <ha.cf> > > logfacility local0 > bcast eth2 > mcast eth2 225.0.0.1 694 1 0
This does not make any sense. Why would you want to use several communication schemes on the same link. What you should do is use several links, like bcast ethx mcast eth2 ... ucast eth3 ... > auto_failback off > node lb1 Are you sure this is a single node cluster? > respawn hacluster /usr/local/heartbeat/lib/heartbeat/ipfail > apiauth ipfail gid=haclient uid=hacluster > > > <harresources> > > lb1 \ > ldirectord::ldirectord.cf \ > LVSSyncDaemonSwap::master \ > IPaddr2::192.168.2.100/24/eth2/192.168.2.255 > > > Heartbeat is starting fine, ldirectord does not seem to start > automatically upon starting hearbeat. Look into the logs for why. > Regardless, with both heartbeat > and ldirectord running there is no > mention of the VIP 192.168.2.100 > > lb1 / # ip addr sh eth2 > > 2: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast > state UP qlen 1000 > link/ether 08:00:27:24:b4:fd brd ff:ff:ff:ff:ff:ff > inet 192.168.2.102/24 brd 192.168.2.255 scope global eth2 > inet6 fe80::a00:27ff:fe24:b4fd/64 scope link > valid_lft forever preferred_lft forever > > Your help is greatly appreciated, and thanks in advance. > > Nick. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
