Re: Update time for beacon
At 10:35 PM 9/29/2004 +0200, jehan procaccia wrote:
> Mitch Kutzko wrote:
>
> >Hi, Derek -- It should be back, now, and you should show up if you haven't
> >stopped your Beacon yet.
> >
> >We're tracking a TCP connection bug (which may or may nore be related to
> >Fedora Core 2 -- We're not sure at this point) which causes that Central
> >Server Beacon to fall over periodically due to a number of odd-state,
> >unclosed connections. It doesn't appear to affect "regular" Beacons, just
> >whichever Beacon is running as the Central Server.
> >
> >
> I happen to be in the same situation, running a beacon centralserver on
> a Fedora core 2 system , and I am also facing irregular results from my
> server. I am struggling with firewall (iptables) rules, but not found a
> correct configuration yet ... but maybe the problem is not firewall
> configuration but "TCP connection bug" you mentionned above ?
> If you have any advices, conlusions on this suspicious "bug?" , please
> let me know, I will also if I finally update my doc on installing a
> beacon client & server on FC2 :
> http://www.int-evry.fr/mci/user/procacci/Doc/Beacon/beacon.html
Hi, Jehan -- I suspect the problem you're dealing with now is firewall
related.
The TCP bug appears to cause the Central Server to fall over periodically
(perhaps once in three or four days), but other than the ip_conntrack table
on the Central Server overflowing and locking up further connections (to
the central server), everything else appears to run fine. The "regular"
clients don't appear to be affected, as you can see from their uptime entries.
Hope this helps!
Mitch
--
Mitch Kutzko | mitch@dast.nlanr.net | mitch@ncsa.uiuc.edu | 217-333-1199
Project: http://dast.nlanr.net/ | Personal: http://hobbes.ncsa.uiuc.edu/