[Linux-HA] A problem with a "simple" configuration

Andrew Beekhof beekhof at gmail.com
Mon Jul 11 06:54:44 MDT 2005


On 7/11/05, Or Goshen <oberonc at gmail.com> wrote:
> On 7/11/05, Andrew Beekhof <beekhof at gmail.com> wrote:
> > On 7/11/05, Or Goshen <oberonc at gmail.com> wrote:
> > > Hello
> > >
> > > First I'll give you some background :
> > > heartbeat 1.99.5
> > > 2 machines each has 2 ports (eth0, eth1),
> > > machine one (M1): eth0 = 192.168.2.241, eth1 = 10.0.0.2
> > > machine two (M2): eth0 = 192.168.2.242, eth1 = 10.0.0.3
> > > failover ip = 192.168.2.240
> > >
> > > eth1 on both machines is connected thru a single crossed over network cable.
> > > and each is capable of pinging the other.
> > >
> > > there is a stable machine whose ip is X.X.X.X .
> > >
> > > ha.cf (same on both machines) :
> > > ####################### Begin
> > > logfacility daemon                           # Log to syslog as
> > > facility "daemon"
> > > node lbtest-master lbtest-slave              # List our cluster members
> > > keepalive 1                                  # Send one heartbeat each second
> > > deadtime 10                                  # Declare nodes dead
> > > after 10 seconds
> > > bcast eth1                                   # Broadcast heartbeats on eth0
> > > ping X.X.X.X                              # Ping our router to monitor
> > > ethernet connectivity
> > > auto_failback no                             # Don't fail back to paul
> > > automatically
> > > respawn hacluster /usr/lib/heartbeat/ipfail  # Failover on network failures
> > > ###################### End
> > >
> > > haresources (same on both machines) :
> > > ###################### Begin
> > > lbtest-master 192.168.2.240
> > > ###################### End
> > >
> > > authkeys (same on both machines) :
> > > ###################### Begin
> > > auth 1
> > > 1 crc
> > > ###################### End
> > >
> > > After executing "/etc/init.d/heartbeat start" I have the following problems :
> > > 1. nothing related to heartbeat is written to /var/log/daemon.log
> > > (syslog is configured correctly)
> >
> > what happens when you run this:
> >   logger -p daemon.info -t logging_test hello
> 
> actually nothing, so I did "killall -HUP syslog-ng" and now I can see
> that this line :
> "Jul 11 23:37:50 (none) heartbeat: [5791]: debug: Setting repeating
> timer for 5000 ms"
> keeps being written to the log till all space on the HD is taken.
> 

No idea about the message (except that in CVS its an error but "#if 0"'d out)

the (none) in the log is suspicious though... what does uname -n say?

it looks like heartbeat isnt even starting so its not surprising
resources are active.

> >
> > does it appear in /var/log/daemon.log?
> >



More information about the Linux-HA mailing list