Date: Wed, 18 Jun 2008 19:21:00 +0200 From: Ali Niknam <freebsd-questions@transip.nl> To: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> Cc: freebsd-questions@freebsd.org Subject: Re: Sockets stuck in CLOSED state... Message-ID: <485943FC.5060807@transip.nl> In-Reply-To: <20080618164345.B34431@wojtek.tensor.gdynia.pl> References: <4859197A.8040203@transip.nl> <20080618164345.B34431@wojtek.tensor.gdynia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
Wojciech Puchar wrote: > #define socket TEST_SOCKET <...> > and write one .c program where all these TEST_* functions are defined, > doing the same as original PLUS logging to file. > > after a while (when you see this closed/unclosed connections) stop it > and look at logs. > Thank you for the suggestions. I had considered that myself, however the server is doing about 300 DNS queries per second, so that's not easy to log. And even if it is logged you have sooo much information that it's nearly impossible to comprehend it. The thing is that the problem does not occur always; the same ip can connect and do queries for thousands of times before 1 connection gets stuck. To give you an idea: after about 24 hours (so that's about 26 million queries) I get about 10 stuck connections. > i'm almost sure you will notice where is a problem. > possibly threads implementation changed... I can imagine; still, as far as I know, it should not be possible to be stuck in "CLOSED"...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?485943FC.5060807>