close_wait connections causing a server to hung Post: 302091909

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

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.

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

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?

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?

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.

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:

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

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

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

LEARN ABOUT DEBIAN

ucmatose

UCMATOSE(1)							     librdmacm							       UCMATOSE(1)

NAME

       ucmatose - RDMA CM connection and simple ping-pong test.

SYNOPSIS

       ucmatose [-s server_address] [-b bind_address] [-c connections]
		 [-C message_count] [-S message_size]
       ucmatose -s server_address [-b bind_address] [-c connections]
		 [-C message_count] [-S message_size] [-t tos]

DESCRIPTION

       Establishes  a  set  of	reliable RDMA connections between two nodes using the librdmacm, optionally transfers data between the nodes, then
       disconnects.

OPTIONS

       -s server_address
	      The network name or IP address of the server system listening for connections.  The used name or address must  route  over  an  RDMA
	      device.  This option must be specified by the client.

       -b bind_address
	      The local network address to bind to.

       -c connections
	      The number of connections to establish between the client and server.  (default 1)

       -C message_count
	      The number of messages to transfer over each connection.	(default 10)

       -S message_size
	      The size of each message transferred, in bytes.  (default 100)

       -t tos Indicates  the  type  of service used for the communication.  Type of service is implementation dependent based on subnet configura-
	      tion.

       -m     Tests event channel migration.  Migrates all communication identifiers to a different event channel for disconnect events.

NOTES

       Basic usage is to start ucmatose on a server system, then run ucmatose -s server_name on a client system.

       Because this test maps RDMA resources to userspace, users must ensure that they have available system resources and permissions.   See  the
       libibverbs README file for additional details.

SEE ALSO

       rdma_cm(7), udaddy(1), mckey(1), rping(1)

librdmacm							    2007-05-15							       UCMATOSE(1)

10 More Discussions You Might Find Interesting

1. HP-UX

Server hung

Discussion started by: biznatch

2. Solaris

remove CLOSE_WAIT connections

Discussion started by: Livio

3. Solaris

CLOSE_WAIT problem in solaris server

Discussion started by: mgmk.84

4. HP-UX

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

Discussion started by: yoda9691