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
oidentd_masq.conf
oidentd_masq.conf(5) File Formats Manual oidentd_masq.conf(5)NAME
oidentd_masq.conf - oidentd IP masquerading/NAT configuration file.
DESCRIPTION
If you are using IP masquerading or NAT, oidentd can optionally return a username for connections from other machines. Support for this is
specified by calling oidentd with the -m (or --masq) flag and by creating an /etc/oidentd_masq.conf file.
oidentd can also forward requests for an IP masqueraded connection to the machine from which connection originates by way of the -f option.
This will only work if the host to which the connection is forwarded is running oidentd with the -P (proxy) flag, or if the host's ident
daemon will return a valid reply regardless of the input supplied by and the address of the host requesting the info (some ident daemons
for windows do this, maybe others).
FORMAT
<IP Address|Hostname>[/<Mask>] <Ident Response> <System Type>
The first field contains the IP address or the hostname of a machine that IP masquerades through the machine on which oidentd runs. The
mask parameter can be either a network mask or a mask in CIDR notation. A mask of 24 is equivalent to 255.255.255.0, a mask of 16 is
equivalent to 255.255.0.0, etc.
The second field specifies the reply that oidentd will return for lookups to the host matching the IP address specified in the first param-
eter.
The third field specifies the operating system the machine matching the first parameter is running.
EXAMPLES
<Host>[/<Mask>] <Ident Response> <System Type>
192.168.1.1 someone UNIX
192.168.1.2 noone WINDOWS
192.168.1.1/32 user1 UNIX
192.168.1.0/24 user3 UNIX
192.168.0.0/16 user4 UNIX
somehost user5 UNIX
192.168.1.0/255.255.255.0 user6 UNIX
AUTHOR
Ryan McCabe <ryan@numb.org>
http://dev.ojnk.net
SEE ALSO oidentd(8)oidentd.conf(5)version 2.0.8 13 Jul 2003 oidentd_masq.conf(5)