Mailing List Archive: wackamole core dump

This is a multi-part message in MIME format.

------=_NextPart_000_028C_01C2C4DC.647AE4E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

i would like to setup wackamole as a simple failover mechanism for a =
stateless web server running linux 2.2.16.
the web servers have IP addresses 192.168.0.1 and 192.168.0.2 =
respectively
i setup the following wackmole.conf on each:

Spread =3D 4803
SpreadRetryInterval =3D 5s
Group =3D wack1
Control =3D /var/run/wack.it
Prefer None
VirtualInterfaces {
{ eth0:10.1.1.2/32 }
}
Arp-Cache =3D 90s
Notify {
eth0:10.1.1.5/32
eth0:10.1.1.4/32
eth0:10.1.1.6/32
eth0:192.168.0.0/24 throttle 128
arp-cache
}
balance {
AcquisitionsPerRound =3D all
interval =3D 4s
}
mature =3D 5s

My first question is -- would that suffice for a failover scenario, or =
should the .2 backup web server have a virtual interface of =
eth0:0.0.0.0/32 (as per a change log i read)?
This of course is all theoretical since my real problem seems to be that =
wackamole seg faults when i try to start it. If i create a secondary =
interface (eth2 for eg) change references to eth2 for virtual interface =
it does not core dump. I can attach the core if you are interested, but =
it is 7.6megs...
spread seems to run fine (according to spmonitor and spuser passes =
messages back and forth), although i do start it with a spread -n =
hostname.
thx for your time.
------=_NextPart_000_028C_01C2C4DC.647AE4E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>i would like to setup wackamole as a =
simple=20
failover mechanism for a stateless web server running linux=20
2.2.16.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>the web servers have IP addresses =
192.168.0.1=20
and 192.168.0.2 respectively</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>i setup the following wackmole.conf on=20
each:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Spread =3D 4803<BR>SpreadRetryInterval =
=3D 5s<BR>Group=20
=3D wack1<BR>Control =3D /var/run/wack.it</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Prefer None</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>VirtualInterfaces=20
{<BR>        { eth0:10.1.1.2/32=20
}<BR>}</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Arp-Cache =3D 90s</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Notify=20
{<BR>       =20
eth0:10.1.1.5/32<BR>       =20
eth0:10.1.1.4/32<BR>       =20
eth0:10.1.1.6/32<BR>       =20
eth0:192.168.0.0/24 throttle =
128<BR>       =20
arp-cache<BR>}<BR>balance =
{<BR>        =20
AcquisitionsPerRound =3D =
all<BR>        =20
interval =3D 4s<BR>}<BR>mature =3D 5s</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>My first question is -- would that =
suffice for=20
a failover scenario, or should the .2 backup web server have a virtual =
interface=20
of eth0:0.0.0.0/32 (as per a change log i read)?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>This of course is all theoretical since =
my real=20
problem seems to be that wackamole seg faults when i try to =
start it.=20
If i create a secondary interface (eth2 for eg) change references to =
eth2 for=20
virtual interface it does not core dump. I can attach the core if you =
are=20
interested, but it is 7.6megs...</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>spread seems to run fine (according to =
spmonitor=20
and spuser passes messages back and forth), although i do start it with =
a spread=20
-n hostname.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>thx for your =
time.</FONT></DIV></BODY></HTML>

------=_NextPart_000_028C_01C2C4DC.647AE4E0--