Hi,
We are using a application which uses port in CLOSE_WAIT Status.
How can I make this port to LISTEN without rebooting the Server.
Even We have checked with all paremetes.and value is standardized
All values are setting as per recommendation .
Last edited by rbatte1; 12-30-2016 at 11:57 AM..
Reason: Added CODE tags
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)
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)
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT SUSE
aggregate-ios
AGGREGATE-IOS(1) General Commands Manual AGGREGATE-IOS(1)NAME
aggregate-ios - optimise a concatenated set of cisco/IOS prefix filters to help make them nice and short.
SYNOPSIS
aggregate-ios <source_config >optimised_config
DESCRIPTION
Takes cisco IOS configuration on stdin, and optimises any prefix filters found using aggregate(1). Optimised filters are produced on std-
out.
OPTIONS
None.
DIAGNOSTICS
Any diagnostics produced by aggregate(1) are passed through on stderr.
EXAMPLES
The following configuration fragment:
ip prefix-list AS65530 description Foo, Inc
ip prefix-list AS65530 permit 10.1.0.0/16
ip prefix-list AS65530 permit 10.2.0.0/16
ip prefix-list AS65530 permit 10.2.1.0/24
ip prefix-list AS65530 permit 10.3.0.0/16
ip prefix-list AS65531 description Bar.Com
ip prefix-list AS65531 seq 5 permit 192.168.1.0/24
ip prefix-list AS65531 seq 10 permit 192.168.2.0/24
ip prefix-list AS65531 seq 15 permit 192.168.0.0/19
is optimised as follows:
ip prefix-list AS65530 permit 10.1.0.0/16 le 24
ip prefix-list AS65530 permit 10.2.0.0/15 le 24
ip prefix-list AS65531 permit 192.168.0.0/19 le 24
SEE ALSO aggregate(1)HISTORY
Aggregate-ios was written by Joe Abley <jabley@mfnx.net>.
BUGS
All those in aggregate(1) and then some :)
Joe Abley 2000 November 27 AGGREGATE-IOS(1)