Re: reconnect question

On Mon, 2008-04-21 at 19:33 +0200, Yoann Vandoorselaere wrote:
> Hi,
> 
> Le jeudi 17 avril 2008 à 19:05 -0700, LC Bruzenak a écrit :
> > In testing, when the prelude-manager on my collection machine is stopped the
> > clients are unable to reconnect on their own.
> > I am forced to go restart those services in order to reestablish connection.
> > I realize that the collection server should never go away; it should be a
> > high-availability type of system.
> 
> This is what is supposed to happen: once an agent notice the connection
> loss, it will wait for ten seconds then attempt a reconnection. 
> 
> Each time the reconnection attempt fail, the connection timeout is
> increased by a factor of two, up to one hour total.
> 
> - 10 seconds
> - 20 seconds
> - 40 seconds
> - 80 seconds
> - ...
> - 3600 seconds
> 
> Aren't you observing this behavior? 
> 
> Regards,

Yoann,

This may be happening as you describe.

We left the connection disabled for ~23 minutes, after which time your
algorithm would be at or near the 1-hour reconnect time.

It gets to a long time rather quickly this way...the first 3 checks in
the series happen in < 1 minutes, while the last 3 are at the 21.2
minutes, 42.4 minutes and 1 hour mark IIUC.

This is a long time - the reconnect time dominates the downtime.

Is there a reason for the incremental reconnect delay? 

Thx,
LCB.


-- 
LC (Lenny) Bruzenak
[email protected]

_______________________________________________
Prelude-user site list
[email protected]
http://lists.prelude-ids.org/mailman/listinfo/prelude-user