12-30-2016
I think the server waits 60 seconds (Sol 10 default, while the old RFC standard is 240) for the client application to finally close the connection in CLOSE_WAIT.
That means each CLOSE_WAIT should go away latest after 60 seconds.
The last netstat line says there is already a service process in LISTEN status.
After shutting down the service (especially after a kill -9) you might need to wait a minute until you can start it again.
Last edited by MadeInGermany; 12-30-2016 at 12:28 PM..
10 More Discussions You Might Find Interesting
1. Solaris
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
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
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
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
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. Solaris
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)
Discussion started by: helplineinc
2 Replies
7. Red Hat
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
8. UNIX for Advanced & Expert Users
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
9. Shell Programming and Scripting
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
10. AIX
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
LMTPD(8) System Manager's Manual LMTPD(8)
*
NAME
lmtpd - LMTP server process
SYNOPSIS
lmtpd [ -C config-file ] [ -U uses ] [ -T timeout ] [ -D ]
[ -a ]
DESCRIPTION
Lmtpd is an LMTP server used to deliver mail to the IMAP mailstore. It accepts commands on its standard input and responds on its standard
output. It MUST be invoked by master(8) with those descriptors attached to a remote client connection.
Lmtpd reads its configuration options out of the imapd.conf(5) file unless specified otherwise by -C.
OPTIONS
-C config-file
Read configuration options from config-file.
-U uses
The maximum number of times that the process should be used for new connections before shutting down. The default is 250.
-T timeout
The number of seconds that the process will wait for a new connection before shutting down. Note that a value of 0 (zero) will dis-
able the timeout. The default is 60.
-D Run external debugger specified in debug_command.
-a Preauthorize connections initiated on an internet socket, instead of requiring LMTP AUTH. This should only be used for connections
coming from trusted hosts.
FILES
/etc/imapd.conf
SEE ALSO
imapd.conf(5), master(8)
CMU
Project Cyrus LMTPD(8)