Sponsored Content
Operating Systems AIX How to repair a TCP/IP socket in state: CLOSE_WAIT? Post 302962751 by agent.kgb on Friday 18th of December 2015 03:38:56 AM
Old 12-18-2015
in some universe is possible that 2+2=5, but in no universe is possible, that a socket changes its state from CLOSE_WAIT to ESTABLISHED.
 

10 More Discussions You Might Find Interesting

1. Programming

C Prog to close a socket in established state

I have a SUN environment running an WebLogic that communicates w/a 3rd party running IIS. When the IIS site goes down (frequently), I am stuck with sockets in an ESTABLISHED state, and cannot seem to figure out how to avoid this. No exceptions are thrown as I can still open connections to the IIS... (1 Reply)
Discussion started by: teledelux
1 Replies

2. Programming

Confusion about TCP/IP socket programming

Hello there chaps. First of all, i'm no TCP/IP-wiz, so forgive me if this is a stupid question. I've been messing around with filetransfer using sockets, and there is one thing that confuses me. This is how it's set up: A server app listens on a port for a client connection. When it... (3 Replies)
Discussion started by: crippe
3 Replies

3. UNIX for Dummies Questions & Answers

Which application has a TCP socket open

If I do a netstat -a I can see all the sockets currently open, is there a way that I can tell which application is holding open these sockets ? (3 Replies)
Discussion started by: murphyboy
3 Replies

4. AIX

TCP/IP socket binding problem

I have what appears to be a unique socket problem, although admittedly my tcp/ip programming experience is relatively limited. I have a AIX server process using TCP/IP berkely sockets, and a Windows (C#) process. The windows process takes input from a user and sends a message to the Unix... (1 Reply)
Discussion started by: adiaconou
1 Replies

5. UNIX for Dummies Questions & Answers

Hitting with custom port in CLOSE_WAIT state for long time in solaris 10

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... (0 Replies)
Discussion started by: mgmk.84
0 Replies

6. Programming

Using socket to test a TCP port

Hello, I'm trying to write a small c application to test a tcp port. This works fine for the most part but the default timeout on the connect is very long. I have been reading many posts but and it looks like I need to set the socket to be non-blocking and poll for a result. I have been totally... (2 Replies)
Discussion started by: tjones1105
2 Replies

7. Solaris

socket in listen state disappears/closes automatically

Hi, I am using solaris 10. I have opened a socket connection using java in solaris 10 operating system, the port went to LISTEN state and able to create new socket connection and the new connections went to ESTABLISHED state. If I issue the command "netstat -an | grep <<portnumber>>", I... (10 Replies)
Discussion started by: kumar3k
10 Replies

8. IP Networking

Packets sent from Linux TCP socket

Hello, Our software is using a TCP socket (AF_INET, SOCK_STREAM) to communicate with an Ethernet device. When we send a message, the message object writes itself in full onto the socket's stream buffer before the software invokes send() from socket.h. I'm still researching, but have 2... (1 Reply)
Discussion started by: bix_20002000
1 Replies

9. Shell Programming and Scripting

Read and write to tcp socket

Hello all, I have a requirement to read and write to a tcp socket from an HP-UX shell script. I see a /dev/tcp character device on my servers: crw-rw-rw- 1 root root 72 0x00004f Mar 28 18:37 /dev/tcp So I believe this is what I should use. The problem is that all the... (2 Replies)
Discussion started by: lupin..the..3rd
2 Replies

10. 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
LAMHALT(1)                                                           LAM TOOLS                                                          LAMHALT(1)

NAME
lamhalt - Shutdown the LAM/MPI run-time environment. SYNOPSIS
lamhalt [-dhHv] OPTIONS
-d Turn on debugging mode. This implies -v. -h Print the command help menu. -i Return immediately (even before the LAM universe is fully halted); deprecated -H Suppress printing the header message. -v Be verbose. DESCRIPTION
The lamhalt tool terminates the LAM software on each of the nodes that were initially booted with lamboot and/or lamgrow. No additional command line arguments are necessary - lamhalt simply sends a message to each remote node telling it to shut down. Each remote node invokes tkill(1) locally to shut down. See tkill(1) for a description of how LAM is terminated on each node. lamhalt may fail if one of the remote nodes has failed, and does not respond to lamhalt's queries. In this case, the lamwipe(1) command should be used to shut down LAM/MPI. If lamwipe(1) fails, the user can manually invoke tkill(1) on the troubled node. In extreme cases, the user may have to terminate individual LAM processes with kill(1). Older versions of lamhalt would return 1-3 seconds before the entire LAM universe was shut down. This caused problems for some LAM users, particularly those who had scripts that invoked lamboot immediately after lamhalt. lamhalt has therefore been changed to wait until the entire LAM universe is down before exiting. This makes the execution of lamhalt take a few seconds (typically less than 5). For users who want the old lamhalt behavior, use the -i (or "immediate") switch, which will cause lamhalt to return immediately, likely before the entire LAM universe has been taken down. EXAMPLES
lamhalt -d Shutdown LAM on the machines and be verbose about its actions. SEE ALSO
recon(1), lamboot(1), tkill(1), bhost(5), lam-helpfile(5), lamwipe(1) LAM 7.1.4 July, 2007 LAMHALT(1)
All times are GMT -4. The time now is 05:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy