Sponsored Content
Operating Systems Solaris How to remove CLOSE_WAIT in Solaris Post 302332415 by helplineinc on Thursday 9th of July 2009 05:19:32 AM
Old 07-09-2009
How to remove CLOSE_WAIT in Solaris

Hi,
We are using a application which uses port in CLOSE_WAIT Status.
Code:
netstat -an|grep 9191
192.168.32.11.9191   192.168.32.11.54562  49152      0 49152      0 CLOSE_WAIT
192.168.32.11.9191   192.168.32.11.54564  49152      0 49152      0 CLOSE_WAIT
192.168.32.11.9191   192.168.32.11.54568  49152      0 49152      0 CLOSE_WAIT
192.168.32.11.9191   192.168.32.11.54576  49152      0 49152      0 CLOSE_WAIT
      *.9191               *.*                0      0 49152      0 LISTEN

How can I make this port to LISTEN without rebooting the Server.
Even We have checked with all paremetes.and value is standardized
Code:
ndd -get /dev/tcp tcp_time_wait_interval :60000

All values are setting as per recommendation .

Last edited by rbatte1; 12-30-2016 at 11:57 AM.. Reason: Added CODE tags
 

10 More Discussions You Might Find Interesting

1. Solaris

remove CLOSE_WAIT connections

Hi folks. I have a problem that I need to remove CLOSE_WAIT connections. On AIX version 5.x, I can use rmsock command. Is there a similar command on Solaris ? Is there an other solution for this situation ? Thanks. (6 Replies)
Discussion started by: Livio
6 Replies

2. UNIX for Advanced & Expert Users

clear CLOSE_WAIT status

Hi, I have an application with a bug in it that keeps sockets in CLOSE_WAIT, which eventually freezes the server because the user account it runs under runs out of file handles. We have the bug fixed but can only release the fix with the next release. Does anyone know how I can clear the... (3 Replies)
Discussion started by: rein
3 Replies

3. UNIX for Advanced & Expert Users

close_wait connections causing a server to hung

Hi Guys, Just wondering if anyone of you have been in a situation where you end up having around 100 close_wait connections and seems to me those connections are locking up resources/processes in the server so unless the server is rebooted those processes won't be released by the close_wait... (3 Replies)
Discussion started by: hariza
3 Replies

4. UNIX for Dummies Questions & Answers

Hitting with custom port in CLOSE_WAIT state for long time in solaris 10

Hi, Occasionally I am getting the port state in CLOSE_WAIT for long time in the solaris server. I am not sure is it application problem or not. Because we are using port 9009 for Tomcat process in our web application, some time when I start the application, the port 9009 is in CLOSE_WAIT... (0 Replies)
Discussion started by: mgmk.84
0 Replies

5. Solaris

CLOSE_WAIT problem in solaris server

Hi, Occasionally I am getting the port state in CLOSE_WAIT for long time in the solaris server. I am not sure is it application problem or not. Because we are using port 9009 for Tomcat process in our web application, some time when I start the application, the port 9009 is in CLOSE_WAIT... (2 Replies)
Discussion started by: mgmk.84
2 Replies

6. Red Hat

Too many CLOSE_WAIT connections

Hi, I am running JBOSS 6 ona RHEL5 server put it continuously crashes due to the number of CLOSE_WAIT connections on port 8080. How can I kill the several hundred CLOSE_WAIT connections without killing the actual live "LISTENING" connection? R, D. (2 Replies)
Discussion started by: Duffs22
2 Replies

7. UNIX for Advanced & Expert Users

stuck in CLOSE_WAIT Solaris 10 - Patch and workaround

Solaris 10 Sparc: When you got a connection locking a tcp/port, and the status is CLOSE_WAIT (for ever :wall:), you just use the tcpdrop, to close the connection. This is a OS bug. I wrote the bug id bellow: BUG-ID 6468753 connections stuck in CLOSE_WAIT The patch that's correct the bug:... (0 Replies)
Discussion started by: thiagofborn
0 Replies

8. Shell Programming and Scripting

Terminate processes for CLOSE_WAIT status of TCP

Hello Friends, First of all im sorry for spending extra space in DB of forum with this thread, i know there would be a solution if i kept searching, I need to terminate the process which causes CLOSE_WAIT status of TCP connection via port 8103: -bash-3.00$ netstat -na | grep 8103... (3 Replies)
Discussion started by: EAGL€
3 Replies

9. AIX

How to repair a TCP/IP socket in state: CLOSE_WAIT?

Hi The clients connect to my server -using port 9130. But no client could connect to my server at this time. I've checked already and this is the result netstat -Aan|grep -v 127.0.0.1|grep 9130|pg f10006000abcb398 tcp4 10313 0 10.0.89.81.9130 10.158.70.24.1705 CLOSE_WAIT... (8 Replies)
Discussion started by: bobochacha29
8 Replies

10. Solaris

How to remove CLOSE_WAIT in Solaris 5.10?

Hi, We are using a application which uses port in CLOSE_WAIT Status. netstat -an|grep 9191 192.168.32.11.9191 192.168.32.11.54562 49152 0 49152 0 CLOSE_WAIT 192.168.32.11.9191 192.168.32.11.54564 49152 0 49152 0 CLOSE_WAIT 192.168.32.11.9191 192.168.32.11.54568 49152 0 49152 0 CLOSE_WAIT... (5 Replies)
Discussion started by: SHIV&JYOTI
5 Replies
TCPDROP(8)						    BSD System Manager's Manual 						TCPDROP(8)

NAME
tcpdrop -- drop TCP connections SYNOPSIS
tcpdrop local-address local-port foreign-address foreign-port tcpdrop [-l] -a DESCRIPTION
The tcpdrop command may be used to drop TCP connections from the command line. If -a is specified then tcpdrop will attempt to drop all active connections. The -l flag may be given to list the tcpdrop invocation to drop all active connections one at a time. If -a is not specified then only the connection between the given local address local-address, port local-port, and the foreign address foreign-address, port foreign-port, will be dropped. Addresses and ports may be specified by name or numeric value. Both IPv4 and IPv6 address formats are supported. The addresses and ports may be separated by periods or colons instead of spaces. EXIT STATUS
The tcpdrop utility exits 0 on success, and >0 if an error occurs. EXAMPLES
If a connection to httpd(8) is causing congestion on a network link, one can drop the TCP session in charge: # sockstat -c | grep httpd www httpd 16525 3 tcp4 192.168.5.41:80 192.168.5.1:26747 The following command will drop the connection: # tcpdrop 192.168.5.41 80 192.168.5.1 26747 The following command will drop all connections but those to or from port 22, the port used by sshd(8): # tcpdrop -l -a | grep -vw 22 | sh SEE ALSO
netstat(1), sockstat(1) AUTHORS
Markus Friedl <markus@openbsd.org> Juli Mallett <jmallett@FreeBSD.org> BSD
January 30, 2013 BSD
All times are GMT -4. The time now is 12:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy