Re: wackamole high cpu utilization on FreeBSD 4.8

>On Nov 17, 2003, at 9:06 PM, Bill Plein wrote:
>>Nov 17 19:15:52 db1 wackamole[41914]: error receiving wackatrl session
>>Nov 17 19:15:52 db1 named[29126]: deleting interface [66.151.149.110].53
>>Nov 17 19:15:52 db1 wackamole[41914]: error receiving wackatrl session
>>Nov 17 19:16:22 db1 last message repeated 513398 times
>>Nov 17 19:18:23 db1 last message repeated 2039749 times
>>Nov 17 19:28:25 db1 last message repeated 10119748 times
>>Nov 17 19:38:25 db1 last message repeated 10116695 times
>>Nov 17 19:48:26 db1 last message repeated 10123830 times
>>Nov 17 19:58:27 db1 last message repeated 10133955 times
>>Nov 17 20:08:28 db1 last message repeated 10107217 times
>>Nov 17 20:15:52 db1 last message repeated 7470197 times
>
>What OS and version are you running?
>
>That message happens when the wackatrl control socket becomes readable, 
>but accepting on it returns an error.  Can you shut it down and delete the 
>/var/run/wack.it file and make sure it isn't touched by any other 
>program?  Then start things back up again.
>
>Are you using the wackatrl tool for anything and can you correlate these 
>problems with its use?


Well, it is reproducing rather rapidly. After wackamole goes out of 
control, I kill it, and delete /var/run/wack.it. There is nothing that is 
touching it (single wackamole and spread instance on each node).

Is there a wackatrl command that can let me test this socket?


--
Bill Plein
SquadEngine.com