On Mon, 1 Nov 1999, Erik Verbruggen wrote:
> On Fri, Oct 29, 1999 at 02:18:04AM +0200, Andi Kleen wrote:
> > On Thu, Oct 28, 1999 at 09:42:11PM +0200, Benjamin C.R. LaHaise wrote:
> > > Hello,
> > >
> > > I've just noticed a bunch of sockets stuck in CLOSE_WAIT without a timer
> > > have been sitting around for at least a day now. They appear to be
> > > triggered by incoming auth requests when my system is delivering mail. I
> > > remember seeing the same thing under 2.3.12 once before as well.
> >
> > CLOSE_WAIT means it is waiting for the process to call close().
> > Fix: kill the process.
>
> No, only a reboot cures them. This behaviour results in quite a lot
> sockets in this state on larger servers. Having like 448 sockets in
> CLOSE_WAIT this way is quite "normal" for an irc server, for example.
To reiterate, they're still here another week later... (zmailer's been
restarted a few times, and I have verified that all of its processes were
killed =)
-ben
tcp 10 0 cr1008912-a.yec1.o:auth radium.scl.zaz.com:4673
CLOSE_WAIT off (0.00/0)
tcp 10 0 cr1008912-a.yec1.o:auth bettina.informati:65057
CLOSE_WAIT off (0.00/0)
tcp 12 0 cr1008912-a.yec1.o:auth mea.tmt.tele.fi:4182
CLOSE_WAIT off (0.00/0)
tcp 10 0 cr1008912-a.yec1.o:auth COYOTE.RES.CMU.EDU:2046
CLOSE_WAIT off (0.00/0)
|