[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FreeBSD 7.0: sockets stuck in CLOSED state...
- To: Eygene Ryabinkin <rea-fbsd_(_at_)_codelabs_(_dot_)_ru>
- Subject: Re: FreeBSD 7.0: sockets stuck in CLOSED state...
- From: Paul <paul_(_at_)_gtcomm_(_dot_)_net>
- Date: Fri, 27 Jun 2008 08:45:50 -0400
- Cc: Ali Niknam <freebsd-net_(_at_)_transip_(_dot_)_nl>, net_(_at_)_freebsd_(_dot_)_org
I have the same 'problem' if that helps any.. Sockets stuck for over a
month in CLOSED and they have a * for the port on the source IP.
tcp4 0 0 184.108.40.206.* 220.127.116.11.1261 CLOSED
7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #6: Thu Apr 17 18:11:49 EDT 2008
Doesn't seem to cause any issues though.
Eygene Ryabinkin wrote:
Ali, good day.
Fri, Jun 27, 2008 at 08:49:20AM +0200, Ali Niknam wrote:
Just a quick "me too" message: I also used to see this on my 7.x
machines. This was with Apache servers in the proxy setup: one
I'm wondering: where these 32 bit, or 64 bit machines?
Well, if your machine was indeed 64 bit, I for one would be very
interested in knowing if it also appears in 32 bit.
I had already tried to debug this situation and Mike Silbersack
helped me with patching the kernel. At that days his patches (that
went into 7.x) helped, but with higher request rate to the Apache,
they seem to be back again. I can try to setup the testbed and
verify if I will still be able to reproduce them. Will it be needed?
Have no i386 machines to test on, sorry. Moreover, I can not yet
reproduce the problem on my amd64, but I am continuing experiments.
freebsd-net_(_at_)_freebsd_(_dot_)_org mailing list
To unsubscribe, send any mail to "freebsd-net-unsubscribe_(_at_)_freebsd_(_dot_)_org"