10-02-2006
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 sockets in CLOSE_WAIT status? This way I won't have to restart the application server every other day...
We have Red Hat Enterprise 4.
Thanks,
Reinout
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 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
3. 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
4. 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
5. 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
6. 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
7. 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
8. 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
9. Shell Programming and Scripting
Hello, this is my first post here.
I'm attempting to write a bash shell script to rm the contents of a directory without deleting the directory, specifically in OS X 10.10 . Here's what I have:
function clear() {
USER="$USER"
DIR=$1
rm -rfv /Users/"$USER"/library/$DIR/*
}
clear... (6 Replies)
Discussion started by: YouNicks
6 Replies
10. 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 49152 0 49152 0 CLOSE_WAIT... (5 Replies)
Discussion started by: SHIV&JYOTI
5 Replies
UP2DATE(8) Red Hat, Inc. UP2DATE(8)
NAME
rhnsd - a program for quering the Red Hat Network for updates and information
SYNOPSIS
rhnsd [OPTION]...
DESCRIPTION
rhnsd is a daemon process that runs in the background and periodically polls the Red Hat Network to see if there are any queued actions
available. If any are queued, it runs them.
rhnsd is typically started from the init scripts in /etc/init.d/rhnsd when it's time to poll the Red Hat Network servers for available
updates and actions. The default interval is every 120 minutes. The minimum polling interval is 60 minutes.
To check for updates, rhnsd runs an external program called rhn_check. This is a small application that actually makes the network connec-
tion to Red Hat Networks.
The rhnsd daemon does not listen on any network ports, nor does it ever talk to the network directly. Any network activity is done via the
rhn_check utility.
rhnsd can be configure by editing the /etc/sysconfig/rhn/rhnsd config file. This is actually the configuration file the rhnsd init script
/etc/init.d/rhnsd uses.
-i, --interval
Specify the interval that rhnsd should wait between checking the Red Hat Network. Default is 120 minutes, the minimum is 60 minutes.
This can also be specified in /etc/sysconfig/rhn/rhnsd
-v, --verbose
output more information about what rhnsd is doing.
-f, --foreground
force the rhnds process to run in the foreground instead of automatically backgrounding itself, as it does by default.
FILES
/etc/sysconfig/rhn/rhnsd
Configuration settings for the rhnsd daemons init script.
/usr/sbin/rhn_check
The external program launched by rhnsd to connect to the Red Hat Network and retrieve any actions that have queued up.
/etc/sysconfig/rhn/systemid
A certification that authenticates the client machine to the Red Hat Network. Generated via the up2date or rhnreg_ks utility.
SEE ALSO
The rhnsd daemon is tightly coupled with Red Hat Network. Visit <http://www.redhat.com/network> for access or to sign up.
rhn_check(8), up2date(8), up2date-config(8),
AUTHORS
Written by Preston Brown <pbrown@redhat.com> and
Cristian Gafton <gafton@redhat.com>
REPORTING BUGS
Report bugs to <http://bugzilla.redhat.com>.
COPYRIGHT
Copyright (C) 1999, 2000 Red Hat, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
4th Berkeley Distribution Fri Feb 9 2001 UP2DATE(8)