Re: lots of InActConn

Denis <[email protected]> Wed, 2 May 2007 12:14:28 -0300
Newsgroups gmane.linux.highavailability.ultramonkey
Message-ID <[email protected]>
Hey, thanks for the aswers.

I could decrease the number of InActConn by decreasing the time of
tcpfin timeout from 10 minutes to 10 seconds.

That appears to not generated any problems.

Did someone know if this can cause any issue?


I'm using this lvs array for squid proxy.


Thanks and regards.


Denis Anjos

Proxy-Node1:~# ipvsadm -L --timeout
Timeout (tcp tcpfin udp): 300 10 120
Proxy-Node1:~# ipvsadm -L -n
IP Virtual Server version 1.2.0 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  172.16.8.77:3128 wlc persistent 180
  -> 172.16.8.85:3128             Route   4      181        168
  -> 172.16.8.83:3128             Local   5      227        315
Proxy-Node1:~#




2007/4/26, Matthew Newton <[email protected]>:
> Hi,
>
> On Thu, Apr 26, 2007 at 02:59:17PM +0900, Simon Horman wrote:
> > On Wed, Apr 25, 2007 at 03:59:02PM -0300, Denis wrote:
> > > Someone know what can cause this issue (lots of InActConn)) and how
> > > can I Verify if these inactConn really exists, and how to drop the
> > > invalid connections?
> > >
> > >
> > > IP Virtual Server version 1.2.0 (size=4096)
> > > Prot LocalAddress:Port Scheduler Flags
> > >  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
> > > TCP  172.16.8.77:3128 wlc persistent 180
> > >  -> 172.16.8.85:3128                  Route       4        162              424
> > >  -> 172.16.8.86:3128                   Route      1        113
> > >        35
> > >  -> 172.16.8.83:3128                   Local       5        175
> > >      6472
> >
> > Try looking at the output of ipvsadm -L -c -n.
> > This should show you all the connections.
> > And may shed some light on the source of the inactive ones.
>
> I have this on the load-balancers I set up a few months ago. The
> set-up here is to not send packets through the load-balancers on
> the way out, which is what seems to cause it.
>
> Incidentally, the machines are running sarge with backported etch
> packages (had problems with failover sticking and breaking with
> the sarge packages). I tested on "etch" (was testing) back around
> December, though, and everything was fine.
>
> What would be useful is a set of instructions on how to use the
> new heartbeat 2.0 configuration and infrastructure. I believe
> it is far more versatile but can't find any documentation for it
> on the web anywhere, apart from minimal examples on the lvs site.
> (I am using heartbeart 2.0.x with the 1.0 configuration syntax at
> the moment.)
>
> Thanks,
>
> Matthew
>
>
> --
> Matthew Newton <[email protected]>
>
> UNIX and e-mail Systems Administrator, Network Services,
> I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom
>
> For IT help contact helpdesk extn. 2253, <[email protected]>
>


-- 
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to [email protected], with a body:
unsubscribe ultramonkey-users [email protected]
where "[email protected]" is YOUR email address.