Re: RPMs for spread/wackamole/etc and wackamole issues

Been watching the list for awhile, also read your book, Theo.

The book and websites are great on high-level architectural information, 
but I'm wondering where is a good source of nitty-gritty, down and dirty 
installation information?

Wanted to go to Atlanta Monday for apachecon 07, but couldn't get away 
from work. Good luck, Theo.

-Dan

----
Dan Zubey
Sr. Linux Administrator
Odysseyware, Inc.


Theo Schlossnagle wrote:
> 
> On Nov 9, 2007, at 6:22 PM, kevev kevev wrote:
> 
>> Spread+wackamole is BLAH! Use UCARP. It works. :o)
> 
> Eloquent.
> 
> We use CARP in a lot of places.  It's nice.  Not as "cool" as wackamole 
> from the concept side -- much more of a VRRP implementation.  UCARP 
> looks neat.  Freevrrp does pretty much the same thing as far as I can 
> tell.  When my OS doesn't support it on the driver level, I like to use 
> wackamole -- the protocol is much more loose and allows for some 
> "interesting" manipulations.
> 
> Each tool has its own strong points, so to each his own.
> 
>> On Nov 9, 2007 4:31 PM, Spangler, Tim <[email protected]> wrote:
>>>
>>> I hate to follow-up on a two month old problem, but I'm now seeing 
>>> something
>>> similar.
>>>
>>> I've been running several wackamole installs in production since 
>>> march, and
>>> recently came across following line in my messages file: wackamole[8532]
>>> "953 No such interface", which appears to be similar to the problem 
>>> in this
>>> message.
> 
> That message means that it was not about the shutdown the interface 
> because it couldn't find it.
> Is there a problem manifesting other than the log message?  Interfaces 
> plumbed that shouldn't be or interfaces that should be owned yet aren't 
> visible via ifconfig?
> 
> I'll look at merging back in some fixes to the ife-sockpacket stuff 
> (Linux specific ifconfig-like subsystem).  This code was adopted by 
> another project and evolved considerably -- I'll go peak at that and see 
> if any serious fixes were made.
> 
>>> Additionally, I'm running 2 wackamole clusters in the same subnet, 
>>> and have
>>> recently begun seeing the following errors on one of the sets of 
>>> clusters:
>>> In_my_component: unknown proc 192.168.252.25.  This IP address is from a
>>> machine in the other cluster, but spread is running on a different 
>>> port, so
>>> as far as I can tell, they shouldn't be able to see each other.
> 
> Make sure the ports are more than "2" apart. Spread uses port and 
> port+1, I believe.
> 
> For safety sake, I launch my spread rings at +10 +10 +10.
> so ring one will be :4803, ring two will be :4813, ring three will be :4823
> 
> -- 
> Theo Schlossnagle
> Esoteric Curio -- http://lethargy.org/
> OmniTI Computer Consulting, Inc. -- http://omniti.com/
> 
> 
> _______________________________________________
> wackamole-users mailing list
> [email protected]
> http://lists.backhand.org/mailman/listinfo/wackamole-users