10-03-2006
As sumitpandya indicated your code has a problem.
There have been some posts lately about this problem, try searching using the "search" button and "CLOSE_WAIT"
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 OSX
submitdiaginfo
SubmitDiagInfo(8) BSD System Manager's Manual SubmitDiagInfo(8)
NAME
SubmitDiagInfo -- sends diagnostic information to Apple
SYNOPSIS
SubmitDiagInfo
DESCRIPTION
SubmitDiagInfo is a system process which runs periodically. If the user has opted-in for automatic reporting of diagnostic and usage infor-
mation, then SubmitDiagInfo collects and sends to Apple any recent diagnostic information which has not yet been sent to Apple.
SubmitDiagInfo also cleans up any diagnostic and usage information which was created more than one month ago and is no longer needed.
Sending diagnostic and usage reports to Apple helps us improve the quality and performance of our products and services. It helps Apple
identify common usage trends and issues that enable us to allocate our resources efficiently, and it helps us provide better support services
to you and other customers. All of the diagnostic and usage information is collected anonymously from your computer in a way that does not
personally identify you. Reports may include the following information:
- Details about application or system crashes, freezes, or kernel panics.
- Information about events on your computer (e.g. whether a certain function, such as waking your computer was successful or not).
- Usage information (e.g. data about how Apple and third party software, hardware and services are being used).
Automatic reporting of diagnostic information is off by default and no information is sent to Apple unless a user has opted-in to automatic
collection of diagnostic information. A user is offered the opportunity to opt-in for automatic collection of additional diagnostic and
usage information after the user has manually sent a crash, hang or panic report to Apple. Users may at any time opt in or out of automatic
reporting in the Security & Privacy pane of the System Preferences application under the "Privacy" tab.
All diagnostic and usage information which is eligible for automatic reporting is visible in the Console application under the "DIAGNOSTIC
AND USAGE INFORMATION" heading in the application's sidebar. (The information appears here even if a user has not yet opted-in for automatic
reporting.) For security purposes, some system diagnostic information will only be visible to admin users and will only be submitted when an
admin user is logged in.
Users who need technical support should use http://www.apple.com/support or other authorized support channels. Developers who are ADC mem-
bers should submit bug reports using http://bugreporter.apple.com in order to allow for two way communication between Apple and the bug
reporter.
SEE ALSO
ReportCrash(8)
Mac OS June 2, 2019 Mac OS