bug in Release( entry *VE ) RH 7.3

Ezra Nugroho <[email protected]> 06 Jun 2003 15:08:20 -0500
Newsgroups gmane.comp.apache.mod-wackamole.general
Message-ID <[email protected]>
I have a pair of servers running wackamole-2.0.0.
They both work fine if they were serving one virtual ip, however if
there are more, funny things start to happen.

Ok, two boxes, first (64.255.110.66) and second (64.255.110.70).
They both are serving test (64.255.110.80 and 64.255.110.81).

When first started wackamole, it imediatelly captures the two VIP, 

eth0    :64.255.110.66
eth0:1  :64.255.110.80
eth0:2  :64.255.110.81

When second go up, it captured 64.255.110.80

eth0    :64.255.110.70
eth0:1  :64.255.110.80

At that time wackamole at first declares that
"INTERFACE ETH0:1 64.255.110.80 DOWN"


All the above makes sense, wackamole has balanced the VIP assignments
accross two servers. However, apparently when wackamole brought eth0:1
on first, it accidentally took eth0:2 down without telling spread.
Wackamole things that all VIP are acquired, but they are not!

Could it be a bug in the Release( entry *VE ) function, particularly for
RHN 7.3?

Did someone run into this problem before?

Thanks