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
LEARN ABOUT CENTOS
rhsm-icon
rhsm-icon(8) Subscription Status Daemon rhsm-icon(8)
NAME
rhsm-icon - Periodically checks installed products against active subscriptions to check their status.
SYNOPSIS
rhsm-icon [--check-period] [--force-icon=warning|expired|partial] [--check-immediately]
DESCRIPTION
Red Hat provides content updates and support by issuing subscriptions for its products. These subscriptions are applied to systems
(machines) and apply to the installed software products.
On graphical X systems (systems with a GUI interface), a product status daemon runs every 4 hours to check the currently installed software
against the applied subscriptions. If software is installed without a valid and applied subscription (such as a subscription expires or no
subscription is available for the product), then the daemon triggers an icon and warning message to display in the notification area of the
menu.
rhsm-icon
only runs on graphical (X-based) systems. Servers which do not have a GUI interface do not run or require the rhsm-icon daemon.
OPTIONS
-c, --check-period
Sets the interval to use between checks for the product subscription status. The value is in seconds.
-f, --force-icon=TYPE
Manually displays the given type of icon in the start menu. The TYPE can be warning, expired, or partial and uses a different icon
for each type of message.
--i, --check-immediately
Runs the status check process immediately when the command is invoked. Otherwise, there is a four (4) minute delay before running
the check.
-d, --debug
Shows debug messages for the daemon.
USAGE
There are two reasons to invoke rhsm-icon manually:
* To run the daemon on a new schedule (immediately or with a different frequency)
* To view the status icons or messages regardless of the state of the machine
Since X runs the daemon automatically and on schedule, it is not necessary to launch the subscription status daemon manually. The rhsm-icon
command can change this schedule. For example:
rhsm-icon --check-period 120
Administrators can also run rhsm-icon to view any immediate changes to the subscription status of the system. Using the --check-immediately
option runs the check at the time the command is run; otherwise, running rhsm-icon has a four-minute delay before running the status check.
rhsm-icon --check-immediately
If you just want to know what the different subscription status messages look like, then use the --force-icon option. (Also use the
--check-immediately option, or the scan will take the standard four minutes to run and display the icon.)
rhsm-icon --force-icon=warning --check-immediately
rhsm-icon --force-icon=expired --check-immediately
rhsm-icon --force-icon=partial --check-immediately
BUGS
This daemon is part of Red Hat Subscription Manager. To file bugs against this daemon, go to https://bugzilla.redhat.com, and select Red
Hat > Red Hat Enterprise Linux > subscription-manager.
AUTHORS
Deon Lackey, <dlackey@redhat.com>, and James Bowes, <jbowes@redhat.com>. rhsm-icon was written by James Bowes.
COPYRIGHT
Copyright (c) 2010-2012 Red Hat, Inc. This is licensed under the GNU General Public License, version 2 (GPLv2). A copy of this license is
available at http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt.
version 1.3 December 12, 2012 rhsm-icon(8)