Connections locking up with today's -CURRENT
Ian FREISLICH
if at hetzner.co.za
Tue Sep 19 07:04:42 PDT 2006
Andre Oppermann wrote:
> Ian FREISLICH wrote:
> > Hi
> >
> > Anyone noticed that today's current has connections jamming like below:
> >
> > Proto Recv-Q Send-Q Local Address Foreign Address (state)
> > tcp4 0 33028 196.7.162.25.22 196.7.147.230.3569 ESTABLIS
HED
> >
> > Or
> >
> > Proto Recv-Q Send-Q Local Address Foreign Address (state)
> > tcp4 0 846 41.204.193.40.783 196.7.147.20.4131 LAST_ACK
> > tcp4 0 2707 41.204.193.40.783 196.7.147.136.3009 LAST_ACK
> > tcp4 0 650 41.204.193.40.783 196.7.147.18.2159 LAST_ACK
> > tcp4 0 587 41.204.193.40.783 196.7.147.20.3710 LAST_ACK
> > tcp4 0 587 41.204.193.40.783 196.7.147.18.2155 LAST_ACK
> >
> > It's odd because with the top one, I can still log out and the shell
> > disappears, except for the sshd process, which if I kill it terminates
> > the connection.
> >
> > In the second case, those LAST_ACK connections have been around for
> > about 2 hours.
> >
> > Heavy (well, not so heavy) traffic seems to trigger this on long
> > standing connections. For instance, 'tail -f /var/log/spamd.log'
> > on a busy spamassassin process will do it.
>
> Do you have an em(4) interface running at 100Mbit?
I should also say, it just jams one or two connections. Other
connections to the server still function, and I can make new
connections even with the few locked up connections.
Ian
--
Ian Freislich
More information about the freebsd-current
mailing list