Sponsored Content
Operating Systems AIX Port hang issue in AIX Version 5.3 Post 302343816 by subharai on Thursday 13th of August 2009 05:01:39 PM
Old 08-13-2009
Question

We have confirmed the same from the development team that there is no such setting for the max. no of connections allowed to the ports. Moreover from our analysis point of view the no. 300 may not be hard coded because everytime the no. of established connection varies before the ports get into hanged status, but everytime it is > 300.

Few quick questions for better understanding of the issue:-

1.Is there any other workaround available to analyze from OS point of view before throwing the ball to the application developers court?

2.Please let me know what may be the possible reason or the scenarios where ports remain in ESTABLISHED status.

3. Is there any system timeout variable/parameter from AIX point of view where we can mention the time after which the established connection will get automatically closed.

4. Does established connection for a long time mean an IDLE conection?

5. Is there any possibility that due to some never ending processes these connections are getting created with time?

Being very much new to the platform, asked you all the above questions for better understanding of the issue. Thanks in advance.
 

10 More Discussions You Might Find Interesting

1. AIX

AIX 4.1.5/RS6000 boot hang, help requested

Hello there! I have a RS-6000 7043-140 machine with AIX version 4.1.5, that is working for almost 8 years now. It has a tty monitor. My problem started when I upgraded my machine to install a gxt250 graphics adapter card together with a 15" AOC VGA Monitor, logitech keyboard and mouse, ... (2 Replies)
Discussion started by: bright_genius
2 Replies

2. AIX

how to up the aix machine when the desktop was hang

Hi all, My AIX machine desktop was hanged. What to do. please help me. It's very urgent. Thank's & regards, Balaraju. (7 Replies)
Discussion started by: balarajum
7 Replies

3. UNIX for Advanced & Expert Users

removing hang processes (AIX)

Hi Guys, Just wondering if I have a child process which is basically hanging and I can see that is on sleep or wait mode if I want to remove/terminate this process , the signal has to come from its parent I assume. The reason I'm asking this is because I'm facing a db2 hang situation and we... (3 Replies)
Discussion started by: hariza
3 Replies

4. Solaris

Solaris 10 CDE hang issue

Hi, I am facing some issues on Solaris 10 (SPARC 5.10 Generic_118833-36). The issue is when I try to connect/login through CDE it hangs (hangs at login screen). I tried connecting thourgh VNC client also but that also not helped. I had done no configuration change or modified any kernel... (2 Replies)
Discussion started by: kgupta
2 Replies

5. Solaris

Zone hang issue

I have a solaris10 zone running an oracle db in it. The zone hangs after some time the db is started and i 'm unable to log into the zone after that so i have to halt and restart the zone along with db .. but after few hrs again it hangs. What would be the reason for it. I did svcs -xv and got... (13 Replies)
Discussion started by: fugitive
13 Replies

6. AIX

DNS is hang in AIX 6.1

Guy's I have configured DNS like the below but I faced another issue ! nameserver 172.18.14.7 nameserver 172.18.14.8 domain domain.com When I ping any Host from the server itself its replaying me the IP of that hosts that's mean DNS is working fain but when I try to ftp or telnet... (8 Replies)
Discussion started by: Mr.AIX
8 Replies

7. AIX

Need Help Urgent AIX Hang

hello all, I'm newbie on AIX. Can any one tell why this happen ? I have expectation this error came because paging memory. This is my error : ( I cann;t read this log and need your help) --------------------------------------------------------------------------- LABEL: ... (7 Replies)
Discussion started by: Fandikurnia
7 Replies

8. Programming

A system hang issue in porting an old fs to kernel 2.6.32.*

Hi, I ported a file system from Kernel version 2.6.18.* to 2.6.32.46 as VFS implementation has changed and prepare_write/commit_write are replaced by write_begin/write_end pairs. Implemented the feature by writing a wrapper for write_begin and write_end and calling original functions for... (0 Replies)
Discussion started by: Praveen_218
0 Replies

9. Shell Programming and Scripting

How to solve hang issue in script?

i have one function block in the beginning of my script and there are some commands inside that function which will perform some operations. And i am invoking that function from my main script by passing some values. Sometimes it is hanging in the middle for some value. For example: For 1st... (3 Replies)
Discussion started by: thomasraj87
3 Replies

10. AIX

AIX 5.3 NFS export not mounting, rpcinfo hang/timeout on server

Been trying to get a directory NFS-mounted with no success. I've tried both NFS v3 and v4, but currently trying v4. I can't figure out what's going on here. server: sbkovwadmd01 sbkovwadmd01# chnfsdom Current local domain: edw.dev sbkovwadmd01# lssrc -a | grep nfs | grep active nfsd ... (3 Replies)
Discussion started by: eckertd
3 Replies
BIO_s_accept(3) 						      OpenSSL							   BIO_s_accept(3)

NAME
BIO_s_accept, BIO_set_accept_port, BIO_get_accept_port, BIO_set_nbio_accept, BIO_set_accept_bios, BIO_set_bind_mode, BIO_get_bind_mode, BIO_do_accept - accept BIO SYNOPSIS
#include <openssl/bio.h> BIO_METHOD *BIO_s_accept(void); long BIO_set_accept_port(BIO *b, char *name); char *BIO_get_accept_port(BIO *b); BIO *BIO_new_accept(char *host_port); long BIO_set_nbio_accept(BIO *b, int n); long BIO_set_accept_bios(BIO *b, char *bio); long BIO_set_bind_mode(BIO *b, long mode); long BIO_get_bind_mode(BIO *b, long dummy); #define BIO_BIND_NORMAL 0 #define BIO_BIND_REUSEADDR_IF_UNUSED 1 #define BIO_BIND_REUSEADDR 2 int BIO_do_accept(BIO *b); DESCRIPTION
BIO_s_accept() returns the accept BIO method. This is a wrapper round the platform's TCP/IP socket accept routines. Using accept BIOs, TCP/IP connections can be accepted and data transferred using only BIO routines. In this way any platform specific operations are hidden by the BIO abstraction. Read and write operations on an accept BIO will perform I/O on the underlying connection. If no connection is established and the port (see below) is set up properly then the BIO waits for an incoming connection. Accept BIOs support BIO_puts() but not BIO_gets(). If the close flag is set on an accept BIO then any active connection on that chain is shutdown and the socket closed when the BIO is freed. Calling BIO_reset() on a accept BIO will close any active connection and reset the BIO into a state where it awaits another incoming connection. BIO_get_fd() and BIO_set_fd() can be called to retrieve or set the accept socket. See BIO_s_fd(3) BIO_set_accept_port() uses the string name to set the accept port. The port is represented as a string of the form "host:port", where "host" is the interface to use and "port" is the port. Either or both values can be "*" which is interpreted as meaning any interface or port respectively. "port" has the same syntax as the port specified in BIO_set_conn_port() for connect BIOs, that is it can be a numerical port string or a string to lookup using getservbyname() and a string table. BIO_new_accept() combines BIO_new() and BIO_set_accept_port() into a single call: that is it creates a new accept BIO with port host_port. BIO_set_nbio_accept() sets the accept socket to blocking mode (the default) if n is 0 or non blocking mode if n is 1. BIO_set_accept_bios() can be used to set a chain of BIOs which will be duplicated and prepended to the chain when an incoming connection is received. This is useful if, for example, a buffering or SSL BIO is required for each connection. The chain of BIOs must not be freed after this call, they will be automatically freed when the accept BIO is freed. BIO_set_bind_mode() and BIO_get_bind_mode() set and retrieve the current bind mode. If BIO_BIND_NORMAL (the default) is set then another socket cannot be bound to the same port. If BIO_BIND_REUSEADDR is set then other sockets can bind to the same port. If BIO_BIND_REUSEADDR_IF_UNUSED is set then and attempt is first made to use BIO_BIN_NORMAL, if this fails and the port is not in use then a second attempt is made using BIO_BIND_REUSEADDR. BIO_do_accept() serves two functions. When it is first called, after the accept BIO has been setup, it will attempt to create the accept socket and bind an address to it. Second and subsequent calls to BIO_do_accept() will await an incoming connection, or request a retry in non blocking mode. NOTES
When an accept BIO is at the end of a chain it will await an incoming connection before processing I/O calls. When an accept BIO is not at then end of a chain it passes I/O calls to the next BIO in the chain. When a connection is established a new socket BIO is created for the connection and appended to the chain. That is the chain is now accept->socket. This effectively means that attempting I/O on an initial accept socket will await an incoming connection then perform I/O on it. If any additional BIOs have been set using BIO_set_accept_bios() then they are placed between the socket and the accept BIO, that is the chain will be accept->otherbios->socket. If a server wishes to process multiple connections (as is normally the case) then the accept BIO must be made available for further incoming connections. This can be done by waiting for a connection and then calling: connection = BIO_pop(accept); After this call connection will contain a BIO for the recently established connection and accept will now be a single BIO again which can be used to await further incoming connections. If no further connections will be accepted the accept can be freed using BIO_free(). If only a single connection will be processed it is possible to perform I/O using the accept BIO itself. This is often undesirable however because the accept BIO will still accept additional incoming connections. This can be resolved by using BIO_pop() (see above) and freeing up the accept BIO after the initial connection. If the underlying accept socket is non-blocking and BIO_do_accept() is called to await an incoming connection it is possible for BIO_should_io_special() with the reason BIO_RR_ACCEPT. If this happens then it is an indication that an accept attempt would block: the application should take appropriate action to wait until the underlying socket has accepted a connection and retry the call. BIO_set_accept_port(), BIO_get_accept_port(), BIO_set_nbio_accept(), BIO_set_accept_bios(), BIO_set_bind_mode(), BIO_get_bind_mode() and BIO_do_accept() are macros. RETURN VALUES
TBA EXAMPLE
This example accepts two connections on port 4444, sends messages down each and finally closes both down. BIO *abio, *cbio, *cbio2; ERR_load_crypto_strings(); abio = BIO_new_accept("4444"); /* First call to BIO_accept() sets up accept BIO */ if(BIO_do_accept(abio) <= 0) { fprintf(stderr, "Error setting up accept "); ERR_print_errors_fp(stderr); exit(0); } /* Wait for incoming connection */ if(BIO_do_accept(abio) <= 0) { fprintf(stderr, "Error accepting connection "); ERR_print_errors_fp(stderr); exit(0); } fprintf(stderr, "Connection 1 established "); /* Retrieve BIO for connection */ cbio = BIO_pop(abio); BIO_puts(cbio, "Connection 1: Sending out Data on initial connection "); fprintf(stderr, "Sent out data on connection 1 "); /* Wait for another connection */ if(BIO_do_accept(abio) <= 0) { fprintf(stderr, "Error accepting connection "); ERR_print_errors_fp(stderr); exit(0); } fprintf(stderr, "Connection 2 established "); /* Close accept BIO to refuse further connections */ cbio2 = BIO_pop(abio); BIO_free(abio); BIO_puts(cbio2, "Connection 2: Sending out Data on second "); fprintf(stderr, "Sent out data on connection 2 "); BIO_puts(cbio, "Connection 1: Second connection established "); /* Close the two established connections */ BIO_free(cbio); BIO_free(cbio2); SEE ALSO
TBA 1.0.1e 2013-02-11 BIO_s_accept(3)
All times are GMT -4. The time now is 03:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy