Sponsored Content
Top Forums UNIX for Advanced & Expert Users close_wait connections causing a server to hung Post 302091598 by hariza on Wednesday 4th of October 2006 01:12:42 AM
Old 10-04-2006
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 connections. Is there anything that can be done to remove them therefore avoiding rebooting the server. Thanks.

harbry.
 

10 More Discussions You Might Find Interesting

1. HP-UX

Server hung

So my server was hung when I came in this morning. It was responding to pings, but the console and telnet sessions would not respond. There was no disk activity. The display said FA1F which I discovered that the "A" represents a high CPU load. I tired several things to get it going but was forced... (6 Replies)
Discussion started by: biznatch
6 Replies

2. 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

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. HP-UX

ssh session getting hung (smilar to hpux telnet session is getting hung after about 15 minutes)

Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Discussion started by: yoda9691
1 Replies

5. Solaris

Established connections causing lag?

I'm not to sure how to go about this questions, so I will just ask it and then get criticized. How many Established connections should a V440 be able to support? (4 Replies)
Discussion started by: adelsin
4 Replies

6. 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

7. AIX

connections on server

I am using AIX 5.3, its a application server, i am giving the support of OS & Hardware only, now i want to check how many connections are connected to my server, means how many people using my server.:confused: (4 Replies)
Discussion started by: reply.ravi
4 Replies

8. SuSE

Server hung with firmware error

Hi all We've had an issue over the weekend when one of the SUSE Linux Enterprise Server 11 hung and had to be rebooted. The thing is that I got the ticket alert for a FS exceeding its usage at about 22:41:49 PM on 23 March. I checked the dmesg, the messages log and the boot.msg but all I found... (1 Reply)
Discussion started by: hedkandi
1 Replies

9. Linux

Server hung, is this a stack trace?

Hi everyone, Our Red Hat server hung yesterday, and I managed to log into the console and see the following message: RIP: 0010: mwait_idle_with_hints+0x66/ 0x67 RSP: 0018:ffffffff80457f40 EFLAGS: 00000046 RAX: 0000000000000010 RBX: ffff810c20075910 RCX: 0000000000000001 RDX:... (6 Replies)
Discussion started by: badoshi
6 Replies

10. Infrastructure Monitoring

Can HPOV monitor server hung state ?

Hi, We have Solaris-10 running on VMware (x86). It is being monitored by HP Openview. Sometimes when this server hungs, while ping still works, HPOpenview can't alert that server is down (which is actually unresponsive). First symptom we see is, login failure. It will ask user name and after... (7 Replies)
Discussion started by: solaris_1977
7 Replies
statd(1M)						  System Administration Commands						 statd(1M)

NAME
statd - network status monitor SYNOPSIS
/usr/lib/nfs/statd DESCRIPTION
statd is an intermediate version of the status monitor. It interacts with lockd(1M) to provide the crash and recovery functions for the locking services on NFS. statd keeps track of the clients with processes which hold locks on a server. When the server reboots after a crash, statd sends a message to the statd on each client indicating that the server has rebooted. The client statd processes then inform the lockd on the client that the server has rebooted. The client lockd then attempts to reclaim the lock(s) from the server. statd on the client host also informs the statd on the server(s) holding locks for the client when the client has rebooted. In this case, the statd on the server informs its lockd that all locks held by the rebooting client should be released, allowing other processes to lock those files. lockd is started by automountd(1M), mount_nfs(1M), and share(1M) if NFS automounts are needed. FILES
/var/statmon/sm lists hosts and network addresses to be contacted after a reboot /var/statmon/sm.bak lists hosts and network addresses that could not be contacted after last reboot /var/statmon/state includes a number which changes during a reboot /usr/include/rpcsvc/sm_inter.x contains the rpcgen source code for the interface services provided by the statd daemon. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnfscu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), automountd(1M), lockd(1M), mount_nfs(1M), share(1M), svcadm(1M), attributes(5), smf(5) System Administration Guide: IP Services NOTES
The crash of a server is only detected upon its recovery. The statd service is managed by the service management facility, smf(5), under the service identifier: svc:/network/nfs/status Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. If it is disabled, it will be enabled by mount_nfs(1M), share_nfs(1M), and automountd(1M) unless its application/auto_enable prop- erty is set to false. SunOS 5.10 18 Nov 2004 statd(1M)
All times are GMT -4. The time now is 06:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy