Mailing List Archive: Wackamole dropping out

> You should be able to get it via the following:
>=20
> cvs -d :pserver:anonymous@commedia.cnds.jhu.edu:/storage/cvs \
> checkout wackamole
>=20
> That will get you the latest commited version.
>=20
> Then you can keep updates fresh in your checked out copy by cd'ing to =
it,
> and doing 'cvs update'

Ah, right, we're talking at cross purposes - that is indeed what I did, =
and the version I got says "Version 1.3.0 Released 2002-Jan-20" in the =
welcome text displayed when the program is run, but on checking, the =
source code is dated July as you say.

So, back to square one. Got the latest version, and it's not working. =
Any suggested diagnostic routines?

Regards,

Geoff Campbell
Internetworking Ltd.
+44(0)1267-253747

Right, found the answer to the problem below, and it's well worth =
documenting.

RedHat (v7.1 and v7.3, so quite probably others, too) put the host name =
as an alias to the 127.0.0.1 localhost entry in /etc/hosts. Wackamole =
takes great exception to this, and stops working in a number of varied =
and interesting ways, not least those documented below. Remove the =
alias from /etc/hosts, and all is well.

Regards,

Geoff Campbell
Internetworking Ltd.
+44(0)1267-253747
=20

> -----Original Message-----
> From: wackamole-users-admin@lists.backhand.org
> [mailto:wackamole-users-admin@lists.backhand.org]On Behalf Of Geoff
> Campbell
> Sent: 01 August 2002 16:12
> To: wackamole-users@lists.backhand.org
> Subject: [Wackamole-users] Wackamole dropping out
>=20
>=20
> Curious one, this.
>=20
> Set up a pair of servers to run a pair of virtual IP addresses=20
> under Wackamole, on a Mandrake 8.1 distribution of Linux, pretty=20
> much the simplest Wackamole configuration possible. This all=20
> worked perfectly, and I ran a whole suite of tests to confirm it=20
> was doing what it should.
>=20
> Then, for reasons I won't bore you with, the servers had to be=20
> reinstalled with RedHat 7.3. Installation went fine, I blew all=20
> machines back to the stone-age and reinstalled from scratch,=20
> compiled and configured Spread and Wackamole as per the previous=20
> installation without problems. However, Wackamole is now sulking.
>=20
> The two boxes are www1 and www2, with real IP addresses=20
> 10.0.0.121 and 122 respectively, and two virtual IP addresses=20
> 10.0.0.141 and 142. When I bring www1 up, it comes up as=20
> expected with both virtual IP addresses. Bringing www2 up, it=20
> then grabs IP address 10.0.0.142, and looking at the ARP cache on=20
> a local machine shows the IP addresses on the correct ethernet=20
> adapters. However, the eth0:2 entry on www1 hasn't been dropped,=20
> as it used to under Mandrake.
>=20
> More seriously, if I kill www1, either by killing the wackamole=20
> process or by chopping the power to the machine, the wackamole=20
> process on www2 drops out, too, and all virtual IP addresses =
disappear.
>=20
> I'm getting no messages in any of the log files to give me any=20
> sort of clue.
>=20
> Has anyone else seen this, or does anyone have any ideas what=20
> might be going on?
>=20
> Regards,
>=20
> Geoff Campbell
> Internetworking Ltd.
> +44(0)1267-253747
> =20
>=20
>=20
> _______________________________________________
> wackamole-users mailing list
> wackamole-users@lists.backhand.org
> http://lists.backhand.org/mailman/listinfo/wackamole-users