search for: fin_wait_1

...amd64. After running for a while (~ 8 hours), the throughput degrades to very very low rate. I found the squid is in "zoneli" state and is already a bug report on http://www.freebsd.org/cgi/query-pr.cgi?pr=106317 But after more investigation, I found there are lots of TCP Connections in FIN_WAIT_1 and never close. # netstat -an | grep FIN_WAIT_1 | wc -l 823 # netstat -an | grep FIN_WAIT_1 | head tcp4 0 273 192.168.1.1.80 61.62.121.195.64739 FIN_WAIT_1 tcp4 0 13448 192.168.1.1.80 163.22.44.102.58775 FIN_WAIT_1 tcp4 0 33304 192.168.1.1.80...

...g or in /var/log/messages. The server has plenty free available physical RAM, swap is untouched, CPU load is low, etc. Apache is setup to handle a max of 100 clients using prefork model. If I stop and restart Apache, it does not help. What I do notice is 1000's of sockets stuck in "FIN_WAIT_1" in netstat: [web0:~] netstat -an | grep FIN_WAIT | wc -l 1827 These stick around forever. Some eventually trickle away after hours, but the only thing that appears to fix it is to reboot the server. Then all is fine for another day or so. I've tried just about every tuning...

...uded -e "ssh" [user]@[host]:"/cygdrive/e/Shared" /home/[host] However, rsync stalls. This seems to be happening when there are some new large file(s) on [host] - or perhaps too many files? The total is about 30 GB and 55,000 files. On the FreeBSD box the connection state is FIN_WAIT_1. On the Cygwin side the connection state is ESTABLISHED. The connections seem to be hanging around indefinitely. If I "push" the files from the Cygwin machine, rsync runs fine and exits with no error. How can I resolve this problem? -- Joe Demeny

Forwarded message: > From full-disclosure-admin@lists.netsys.com Wed Apr 21 11:49:12 2004 > To: full-disclosure@lists.netsys.com > From: Darren Bounds <dbounds@intrusense.com> > Subject: [Full-Disclosure] IETF Draft - Fix for TCP vulnerability > Date: Tue, 20 Apr 2004 18:19:58 -0400 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >