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,
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 ... (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)
Discussion started by: bobochacha29
8 Replies
LEARN ABOUT DEBIAN
prips
PRIPS(1) BSD General Commands Manual PRIPS(1)NAME
prips -- print the IP addresses in a given range
SYNOPSIS
prips [-c] [-d delim] [-e exclude] [-f format] [-i incr] start end
prips [-c] [-d delim] [-e exclude] [-f format] [-i incr] CIDR-block
prips -h
DESCRIPTION
The prips tool can be used to print all of the IP addresses in a given range. It can enhance tools that only work on one host at a time,
e.g. whois(1).
The prips tool accepts the following command-line options:
-c Print the range in CIDR notation.
-d delim
Set the delimiter to the character with ASCII code delim where 0 <= delim <= 255.
-e <x.x.x,x.x>
Exclude ranges from the output.
-f format
Set the format of addresses (hex, dec, or dot).
-h Show summary of options.
-i incr
Set the increment to 'x'.
ENVIRONMENT
The prips tool's operation is not influenced by any environment variables.
FILES
The prips tool's operation is not influenced by any files.
EXAMPLES
Display all the addresses in a reserved subnet:
prips 192.168.32.0 192.168.32.255
The same, using CIDR notation:
prips 192.168.32/24
Display only the usable addresses in a class A reserved subnet using a space instead of a newline for a delimiter:
prips -d 32 10.0.0.1 10.255.255.255
Display every fourth address in a weird block:
prips -i 4 192.168.32.7 192.168.33.5
Determine the smallest CIDR block containing two addresses:
prips -c 192.168.32.5 192.168.32.11
DIAGNOSTICS
The prips utility exits 0 on success, and >0 if an error occurs.
SEE ALSO ipsc(1), gipsc(1)STANDARDS
No standards were harmed in the writing of the prips tool.
HISTORY
The prips tool was originally written by Daniel Kelly and later adopted by Peter Pentchev. This manual page was originally written by Juan
Alvarez for the Debian GNU/Linux system and later added to the prips distribution and converted to mdoc format by Peter Pentchev.
AUTHORS
Daniel Kelly <dan@vertekcorp.com>
Juan Alvarez <jalvarez@fluidsignal.com>
Peter Pentchev <roam@ringlet.net>
BUGS
Please report any bugs in the prips tool to its current maintainer, Peter Pentchev.
BSD March 1, 2011 BSD