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
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT DEBIAN
qpsmtpd-prefork
qpsmtpd-prefork(8) System Manager's Manual qpsmtpd-prefork(8)
NAME
qpsmtpd-prefork - Preforkin server for qpsmtpd
SYNOPSIS
qpsmtpd-prefork [options]
DESCRIPTION
qpsmtpd-prefork is the qpsmtpd frontend script which binds to the SMTP TCP socket, and asynchronously forks new children in advance of new
connections.
OPTIONS
--port port
Binds to a specific port, instead of the default 2525.
--user user
On startup, switch to run as user instead of the starting user. Applies only when started as root (as is normal when listening on
port 25).
--limit-connections limit
Accept at most limit simultaneous connections. Inbound connections beyondthis limit will be deferred or refused.
--max-from-ip limit
Accept at most limit simultaneous connections from any given IP address; does not override --limit-connections, if set.
--children limit
Limit the total number of child processes to limit; once all children are handling requests, further connections are deferred.
--idle-children count
Keep count child processes available, subject to the upper bound given via --children. Specify 0 to disable preforking entirely.
--interface addr
Bind to the local address addr, instead of the default behavior of binding to all interfaces. Can be specified multiple times to
bind to more than one interface or local address.
--renice-parent delta
Adjust the priority of the parent process by delta, yielding more CPU time to other processes. The default is 5.
--detach
Detach from the controlling terminal at startup, to run as a standalone daemon. See also --pid-file.
--pid-file filename
Upon startup, and after daemonizing if applicable, write the process ID to filename, for use by sysvinit control scripts or similar
utilities.
--pretty-child
Update child process names within the process table.
--version
Print the qpsmtpd release version and exit.
--debug
Be somewhat more verbose about logging during startup (has no effect once fully started).
--help Display commandline help and exit.
AUTHOR
Copyright (c) 2006, SoftScan; based on qpsmtpd-forkserver by Ask Bjorn Hansen <ask@develooper.com>
http://smtpd.develooper.com/
qpsmtpd-prefork(8)