Sponsored Content
Full Discussion: clear CLOSE_WAIT status
Top Forums UNIX for Advanced & Expert Users clear CLOSE_WAIT status Post 302091443 by sumitpandya on Tuesday 3rd of October 2006 04:06:45 AM
Old 10-03-2006
You need to look into sysctl document

You can tune many of TCP/IP related parameters from procfs/sysfs
See to document /usr/src/linux/Documentation/networking/ip-sysctl.txt
Example, for TCP there are following files
/proc/sys/net/ipv4/tcp_*
Remember changes in those file will be temperal and will not remain after system reboot. To make it parmenant you need to create "/etc/sysctl.conf" entries. Look man sysctl
Also if you can do socket shutdown then socket close in your application then it also overcome our problem
 

10 More Discussions You Might Find Interesting

1. Solaris

remove CLOSE_WAIT connections

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

close_wait connections causing a server to hung

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

CLOSE_WAIT problem in solaris server

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

How to remove CLOSE_WAIT in 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

Too many CLOSE_WAIT connections

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

stuck in CLOSE_WAIT Solaris 10 - Patch and workaround

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

Terminate processes for CLOSE_WAIT status of TCP

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

How to repair a TCP/IP socket in state: CLOSE_WAIT?

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

Clear contents of specified directories, then return exit status

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

How to remove CLOSE_WAIT in Solaris 5.10?

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
SYSTEMD-SYSCTL.SERVICE(8)				      systemd-sysctl.service					 SYSTEMD-SYSCTL.SERVICE(8)

NAME
systemd-sysctl.service, systemd-sysctl - Configure kernel parameters at boot SYNOPSIS
/lib/systemd/systemd-sysctl [OPTIONS...] [CONFIGFILE...] systemd-sysctl.service DESCRIPTION
systemd-sysctl.service is an early boot service that configures sysctl(8) kernel parameters by invoking /lib/systemd/systemd-sysctl. When invoked with no arguments, /lib/systemd/systemd-sysctl applies all directives from configuration files listed in sysctl.d(5). If one or more filenames are passed on the command line, only the directives in these files are applied. In addition, --prefix= option may be used to limit which sysctl settings are applied. See sysctl.d(5) for information about the configuration of sysctl settings. After sysctl configuration is changed on disk, it must be written to the files in /proc/sys before it takes effect. It is possible to update specific settings, or simply to reload all configuration, see Examples below. OPTIONS
--prefix= Only apply rules with the specified prefix. -h, --help Print a short help text and exit. --version Print a short version string and exit. EXAMPLES
Example 1. Reset all sysctl settings systemctl restart systemd-sysctl Example 2. View coredump handler configuration # sysctl kernel.core_pattern kernel.core_pattern = |/libexec/abrt-hook-ccpp %s %c %p %u %g %t %P %I Example 3. Update coredump handler configuration # /lib/systemd/systemd-sysctl --prefix kernel.core_pattern This searches all the directories listed in sysctl.d(5) for configuration files and writes /proc/sys/kernel/core_pattern. Example 4. Update coredump handler configuration according to a specific file # /lib/systemd/systemd-sysctl 50-coredump.conf This applies all the settings found in 50-coredump.conf. Either /etc/sysctl.d/50-coredump.conf, or /run/sysctl.d/50-coredump.conf, or /usr/lib/sysctl.d/50-coredump.conf will be used, in the order of preference. See sysctl(8) for various ways to directly apply sysctl settings. SEE ALSO
systemd(1), sysctl.d(5), sysctl(8), systemd 237 SYSTEMD-SYSCTL.SERVICE(8)
All times are GMT -4. The time now is 12:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy