search for: close_waits

...ngrel_r 831 root 32u IPv4 95165064 TCP localhost.localdomain :8011->localhost.localdomain:59830 (CLOSE_WAIT) etc. this goes on for 700 lines, where the mongrel on port 8011 has roughly 700 CLOSE_WAIT TCP connections to the 30-60k port range (to apache, I believe). All of these close_waits are for the mongrel on port 8011, in this case. Also, any ideas what''s going on with the close_wait connections to amazon s3? lsof -i -P | grep CLOSE_ | grep mongrel | wc -l 703 netstat | grep 56586 # an example port tcp 1 0 localhost.localdomain:8011 localhost.l...

...ngrel_r 831 root 32u IPv4 95165064 TCP localhost.localdomain :8011->localhost.localdomain:59830 (CLOSE_WAIT) etc. this goes on for 700 lines, where the mongrel on port 8011 has roughly 700 CLOSE_WAIT TCP connections to the 30-60k port range (to apache, I believe). All of these close_waits are for the mongrel on port 8011, in this case. Also, any ideas what''s going on with the close_wait connections to amazon s3? lsof -i -P | grep CLOSE_ | grep mongrel | wc -l 703 netstat | grep 56586 # an example port tcp 1 0 localhost.localdomain:8011 localhost.l...

...blem related to winbindd. When I leave it running overnight on a quiet (not silent however) server I find that it generates a large number of CLOSE_WAIT state connections. 84 on a fairly quiet system in the last 18 hours. I can't seem to find any command that directly affects the number of CLOSE_WAITS. Below is my netstat listing. Any ideas would be helpful. I looked around but could find no reference to this problem. I am running in SECURITY = ADS mode. Thank you everyone for help. --Tim Laurence Versions of Software Samaba 3.0.1 Winbind 3.0.1 823-mailsrv:/# netstat --ip -ap Active...

Hi folks, When I enabled stored configs on my puppet master, it began keeping lots of open connections to the MySQL server (as far as I understand it opened one connection for each client run and never closed them). I set up the server to close idle connections after 5 minutes. Now the database server does close the connections but the puppet master keeps them in CLOSE_WAIT state and eventually

Lately it never fails when I attach a Mac running OSX 10.5 that I get runaway pid's. I tracked them down so far to multiple close_wait's: # /usr/sbin/lsof | grep pbg5mac smbd 24876 root 6u IPv4 80015755 TCP yoda.wrenkasky.com:netbios-ssn->pbg5mac.wrenkasky.com:49381 (CLOSE_WAIT) They can grow to over 100 if I don't catch it or nobody can log on anymore ;-)

We have a windows 2003 dc here at the university and I have successfully setup samba-3.0.2-6.3E on a RHEL WS3 machine. The problem is that after several hours, or several days winbind stops running and connections fail. I have seen instances of this on other sites, but no firm answers. I can provide files and logs if helpful

Hello list Our central fileserver is a Samba 3.0.25b on Solaris 9 and has 10'000 users (several hundreds at the same time). This week it died on us and when I inspected the machine, it was out of 8GB Memory and 16GB Swap because thousands of smbd processes were running. netstat -na showed that many hundreds of connections to port 445 were in CLOSE_WAIT state. We first thought it could be

the rail application I have developed (really simple one 2 -> db tables with no more than 100 records) works perfectly in development / production mode on my windows desktop (win200 pro + mysql + ruby 1.8.2 + rails 1.1.6). when deploying the application on linux (ruby 1.8.4 , rails 1.1.6 the same mysql as on windows) everything *seems* to work fine. well atleast for the first few hours. the

Hello. Im running tinc from long time, but recently I noticed that tinc TCP connections are not closed correctly (timeout). They seem to linger around like this: Proto Recv-Q Send-Q Local Address Foreign Address State tcp 80 0 xxx.x.x.xx:58801 xx.xxx.xxx.xx:*** ESTABLISHED tcp 515 0 xxx.x.x.xx:45422 xx.xxx.xxx.xxx:*** ESTABLISHED

Hi folks I know that has, to some degree, been run over the past year in different ways, but, I may have yet another instance of an issue on this. The puppetmaster system and the puppet system are both running 0.24.7-r1, on a gentoo system. Other puppet systems are running 0.24.4. The puppet system (not the puppetmaster system) that is running 0.24.7-r1 is showing multiple close_wait

Hi folks I am running openssh-3.7.1 on my servers most of them are Solaris and Linux built. I run ssh-keyscan , some times it seems to be hanging ( even with -T option enabled) in close_wait state. can you please point me to any patch that is available or any work around for this problem ? thanks, Sai.

Hello! I can't find the cause of the above problem. Some smbd processes stuck in close_wait state and some file locks remain behind too. /any clue would be apreciated Attila /

We've seen Samba crash and burn twice in the last 48 hours - it just started happening, and we have no idea what might be causing it. I'm hoping that someone will recognize this problem. Platform: we are running RedHat Enterprise Server, with Samba 3.0.7. We're using security=domain in an old-style NT4 domain environment. The symptom that we're seeing is that the number of

Hello, I''m experiencing a strange, but very bad behavior with Mongrel 0.3.13.4 and Pound 1.8. Every 6 hours or so one of our nine (not consistent on which one) application servers ( each one running several mongrel processes ) will start leaving lots of socket connections with pound open. This leads to "Too many open files" errors. I''ve set pound to close connections

hi everyone, congratulations on the release of icecast 2.1.0 I presume this is the right place to post about iceS. please correct if wrong. I have a two instance setup, and have been finding that after a network error occurs, the instance does not reconnect. The source server is behind a linux NAT box. I have simulated the problem by using iptables REJECT with tcp-reset and here is the

Over the past 2 days, my smbd processes are multiplying worse than rabbits. At least with rabbits it's easy to tell why you wind up with so many... Here's the setup: Samba version 3.2.8-0.24 installed via rpm on a FC6 box with 2 nics, both on the same subnet. The samba server acts as a PDC in a mixed environment but mostly windows pc's running xp. It is used mostly for file

Hi all! I've bumped into an issue which Dovecot which has me a bit stumped; All of a sudden (ie. no obvious changes made to the config as far as I know) Dovecot seems to never stop 'imap-login' processes. This continues to the point where it will hit the 'process_limit'. For a 50-ish user install the limit was set to 100 but I increased it to 512. The only thing this changes

I have the need to know how many connection the server has, i run this command but i don't know how to sum all the results and get a final number. any ideas? netstat -an | grep -E 'tcp|udp' | awk '{print $6}' | sort | uniq -c | sort -n ?? 1 CLOSE_WAIT ?? 1 FIN_WAIT_2 ?? 1 LAST_ACK ?? 1 TIME_WAIT ?? 4 SYN_SENT ? 15 ? 37 LISTEN ? 44 ESTABLISHED

Greetings, I need some help... please be gentle :-) MY SETUP: Solaris-X86, ruby-1.8.4, Apache-2.2.0, Mongrel-0.3.13.4, MySql-4.1.10a I am using the typical setup with apache proxying request to mongrel with mod_proxy_balancer. Currently, I am only running a single instance of mongrel behind the proxy. I am also using the following gems with this app: capistrano (1.2.0) daemons (1.0.2)

Hi all, I encounter timeout errors during file uploads in my Rails application. I think the problem may be in the Mongrel configuration. Here is my setup: * Load balancer (Cisco CSM, my provider''s Catalyst 6509) * Apache 2.2.3 with mod_proxy_balancer * Mongrel 0.3.13.3 * Rails 1.1.6 * Ruby 1.8.4 * MySQL 5.0.22 * file_column I host an application in which users may upload medium files