Sponsored Content
Top Forums UNIX for Advanced & Expert Users 30 tcp connections Established for a while and after a few minutes are close Post 303030676 by alexcol on Wednesday 13th of February 2019 08:37:05 PM
Old 02-13-2019
Thanks you very much for your support and explanation, it is useful for me to grow. Unfortunately i dont have enough documentation at hand for every party (ip adresses,ports, services and so on) to provide and to keep the resolution . AS soon as i get this i will let you know. THanks once again for your support
This User Gave Thanks to alexcol For This Post:
 

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. UNIX for Dummies Questions & Answers

close tcp port

Hello, I have a service running (ODBC) and every now and then it will hang and I will have to stop and restart the service. The problem is when I stop the service, it indeed stops the service, but netstat reports a tcp port still open with the fin_wait_2 status. Then I must close the client... (1 Reply)
Discussion started by: raidzero
1 Replies

3. Programming

close existing tcp connection in C

Hello. I would like to know how to close an existing tcp socket. I have read some stuff and learned how to create a socket and then close it but have not found anything about how to close an existing tcp socket created by another application. The situation is this: I have an ODBC server running and... (6 Replies)
Discussion started by: raidzero
6 Replies

4. Red Hat

How to kill all active tcp connections from an IP?

How to kill all active tcp connections from an IP? I am using CentOS (3 Replies)
Discussion started by: an00p
3 Replies

5. Solaris

How to kill the TCP ESTABLISHED connection in netstat

Hello, Actually there are some bugs in application which does not close the TCP connection to other server though CORBA. We need to kill that ESTABLISHED connections as new connection are not happeneing as the allocated ports were used and showing as ESTABLISHED Is there any... (4 Replies)
Discussion started by: GIC1986
4 Replies

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

7. Programming

TCP trashing data on application close

I am using c to send data to a socket with the following commands: socket = socket(AF_INET, SOCK_STREAM, ptrp->p_proto); ioctl(socket, FIONBIO, (char *)&on); connect(socket) send(socket,data) shutdown(socket, SHUT_WR); recv(socket) //ready last of data waiting on the port //note this is... (3 Replies)
Discussion started by: metrix
3 Replies

8. IP Networking

How to test max number of tcp connections

Hello, I wanna test max tcp connection value. Please suggest how to do that. Thanks. (2 Replies)
Discussion started by: gstoychev
2 Replies

9. Solaris

many tcp connection in close-wait

Hi, I use solaris Unix . I find there is some problem in application and it generate many "close-wait" tcp connect and stay in the server . it is generate by process id 7740 root@XX # netstat -an | grep CLOSE_WAIT | wc -l 285 root@XX # netstat -an | grep CLOSE_WAIT 10.158.35.4.34805 ... (2 Replies)
Discussion started by: abcdef
2 Replies

10. IP Networking

Need to know reason for connections closed in netstat -p tcp

Hello netstat -p give below 6634176 connections as closed.How do we trace that which all connections are being closed on the server? 1366888371 data packet headers correctly predicted 1195906 connection requests 5227320 connection accepts 5992919... (6 Replies)
Discussion started by: Vishal_dba
6 Replies
sys_attrs_io(5) 						File Formats Manual						   sys_attrs_io(5)

NAME
sys_attrs_io - io subsystem attributes DESCRIPTION
This reference page lists and describes attributes for the I/O (io) kernel subsystem. Refer to the sys_attrs(5) reference page for an introduction to the topic of kernel subsystem attributes. Amount of space in megabytes to allocate for the 32-bit scatter-gather DMA window on PCI-based AlphaServers. This parameter is set by the TruCluster software. Default value: 0 (MB) Do not modify the value of this attribute unless instructed to do so by support personnel or by patch kit documentation. Number of entry dispatch points supported by the in-memory table for the bdev (block device driver) switch. This table is used to access block device drivers, and must be large enough to accommodate the drivers registered in the bdevsw table in the /usr/sys/sys- tem_name /conf.c file, plus any additional device drivers that will be dynamically loaded. Default value: 200 Minimum value: 0 Maximum value: INT_MAX If the number of third-party block device drivers that will be dynamically loaded to the system plus the number of block device drivers already registered in the system_name /conf.c file exceeds 200, you may want to increase the value of bdevsw_size. A query-only attribute that specifies the media from which the system was booted. Number of buffers either added to or removed from the buffer pool free list. Buffers are allocated as they are needed in order to handle immediate demands; however, they are deallocated carefully to prevent spikes. Default value: 50 buffers Do not modify the default setting for this attribute unless instructed to do so by support personnel or by patch kit instructions. A threshold value that determines when more buffers are allocated from the kernel. More buffers are allocated from the kernel when the number of buffers in the pool free list falls below this value. CAM reserves the number of buffers specified by the cam_ccb_low_water attribute to ensure that the kernel always has enough memory to shut down runaway processes. Default value: 100 (buffers) Do not modify the default setting for this attribute unless instructed to do so by support personnel or by patch kit instructions. The base number of Common Access Method (CAM) control blocks (ccbs) allocated to the buffer pool free list. One ccb is needed for each outstanding I/O request. The system will automatically increase the number of ccbs, as necessary for the I/O load, but will not decrease allocation of ccbs below cam_ccb_pool_size. Default value: 200 (ccbs) Minimum value: 100 Maximum value: 1000 If the I/O load on your system is consistently very high, increasing the number of ccbs that are always available in memory (rather than starting with a lower number and letting the system dynamically increase it when necessary) may improve performance. However, by increasing cam_ccb_pool_size, you prevent the system from using the additional memory for other purposes at times when the number of I/O requests is lower than the number of ccbs. Any performance improvement that results from a cam_ccb_pool_size increase can occur only if your system's memory size is large enough to support the dedication of additional memory resources to I/O. Decreasing cam_ccb_pool_size to a value below the default is very likely to cause I/O problems and is strongly discouraged. Number of entry dispatch points supported by the in-memory table for the cdev (character device driver) switch. This table is used to access character device drivers, and must be large enough to accommodate the drivers registered in the cdevsw table in the /usr/sys/system_name /conf.c file, plus any additional character device drivers that will be dynamically loaded. Default value: 200 (entry dispatch points) Minimum value: 0 Maximum value: INT_MAX If the number of third-party character device drivers that will be dynamically loaded to the system plus the number of character device drivers already registered in the system_name /conf.c file exceeds 200, you may want to increase the value of cdevsw_size. An on/off switch for internal use only. Do not modify this attribute unless instructed to do so by support personnel or by patch kit instructions. An on/off switch for internal use only. Do not modify this attribute unless instructed to do so by support personnel or by patch kit instructions. An on/off switch for internal use only. Do not modify this attribute unless instructed to do so by support personnel or by patch kit instructions. A value used by developers when debugging subsystem source code. Do not modify the default value of this attribute unless instructed to do so by support personnel or by patch kit documentation. Amount of space in megabytes to allocate for the 64-bit scatter-gather DMA window on PCI-based AlphaServers. Default value: 0 (MB) Do not modify this attribute unless instructed to do so by support personnel or by patch kit documentation. A value that controls the zeroing of scatter-gather mapping entries in the PCI adapter on AS8x00 Alphaservers. Default value: 2 Do not modify this attribute unless instructed to do so by support personnel or by patch kit documentation. A value used by developers for debugging subsystem source code. Do not modify this attribute unless instructed to do so by support personnel or by patch kit documentation. The size, in bytes, of an I/O read request used by nondriver kernel code if an ioctl() call fails or returns 0 (zero). (When non- driver kernel code needs to know the maximum size of an I/O read request for a block-I/O device, it issues an ioctl call to the driver.) Default value: 65,536 (bytes) Change the default value of this attribute only if a third-party device driver does not use the ioctl call and has a maximum size that is less than the default value (65536 bytes, or 64 kilobytes) in the sysconfigtab file . (The person writing the third-party device driver must provide information, either in documentation or an installation script, on how to change the entry in the syscon- figtab file to the correct value.) The size, in bytes, of an I/O write request used by nondriver kernel code if an ioctl() call fails or returns 0 (zero). (When non- driver kernel code needs to know the maximum size of an I/O write request for a block-I/O device, it issues an ioctl() call to the driver.) Default value: 65,536 (bytes) Change the default value of this attribute only if a third-party device driver does not use the ioctl call and has a maximum size that is less than the default value (64 KB) in the sysconfigtab file. (The person writing the third-party device driver must pro- vide information, either in documentation or an installation script, on how to change the entry in the sysconfigtab file to the cor- rect value.) Default value: 0 Do not modify the default setting of this attribute unless instructed to do so by support personnel or by patch kit documentation. Maximum number of NPort I/Os. This attribute is visible only if the Emulex Fibre Channel Host Adapter is installed on the system. Refer to the emx(7) reference page for information on setting this attribute. Default value: 256. To turn I/O limiting off, set the value of NPort_Max_IOs to equal 0xFFFFFFFF. Do not attempt to set the value of NPort_Max_IOs to less than the value of NPort_Min_IOs. Minumum number of NPort I/Os. This attribute is visible only if the Emulex Fibre Channel Host Adapter is installed on the system. Refer to the emx(7) reference page for information on setting this attribute. Default value: 20. The value of NPort_Min_IOs must always be less than the value of NPort_Max_IOs. The NPort I/O ramp time delay in seconds. This attribute is visible only if the Emulex Fibre Channel Host Adapter is installed on the system. Refer to the emx(7) reference page for information on setting this attribute. Default value: 1. The NPort I/O ramp percentage (integer). This attribute is visible only if the Emulex Fibre Channel Host Adapter is installed on the system. Refer to the emx(7) reference page for information on setting this attribute. Default value: 10 A query-only attribute used for subsystem debugging. A query-only attribute used for subsystem debugging. An attribute used only internally. Do not modify the default setting of this attribute unless instructed to do so by support personnel or by patch kit documentation. SEE ALSO
sys_attrs(5) sys_attrs_io(5)
All times are GMT -4. The time now is 12:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy