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
STONITHD(7)						      Pacemaker Configuration						       STONITHD(7)

NAME
stonithd - Options available for all stonith resources SYNOPSIS
[stonith-timeout=time] [priority=integer] [pcmk_host_argument=string] [pcmk_host_map=string] [pcmk_host_list=string] [pcmk_host_check=string] [pcmk_reboot_action=string] [pcmk_poweroff_action=string] [pcmk_list_action=string] [pcmk_monitor_action=string] [pcmk_status_action=string] DESCRIPTION
This is a fake resource that details the instance attributes handled by stonithd. SUPPORTED PARAMETERS
stonith-timeout = time [60s] How long to wait for the STONITH action to complete. Overrides the stonith-timeout cluster property priority = integer [0] The priority of the stonith resource. The lower the number, the higher the priority. pcmk_host_argument = string [port] Advanced use only: An alternate parameter to supply instead of 'port' Some devices do not support the standard 'port' parameter or may provide additional ones. Use this to specify an alternate, device-specific, parameter that should indicate the machine to be fenced. A value of 'none' can be used to tell the cluster not to supply any additional parameters. pcmk_host_map = string [] A mapping of host names to ports numbers for devices that do not support host names. Eg. node1:1;node2:2,3 would tell the cluster to use port 1 for node1 and ports 2 and 3 for node2 pcmk_host_list = string [] A list of machines controlled by this device (Optional unless pcmk_host_check=static-list). pcmk_host_check = string [dynamic-list] How to determin which machines are controlled by the device. Allowed values: dynamic-list (query the device), static-list (check the pcmk_host_list attribute), none (assume every device can fence every machine) pcmk_reboot_action = string [reboot] Advanced use only: An alternate command to run instead of 'reboot' Some devices do not support the standard commands or may provide additional ones. Use this to specify an alternate, device-specific, command that implements the 'reboot' action. pcmk_poweroff_action = string [poweroff] Advanced use only: An alternate command to run instead of 'poweroff' Some devices do not support the standard commands or may provide additional ones. Use this to specify an alternate, device-specific, command that implements the 'poweroff' action. pcmk_list_action = string [list] Advanced use only: An alternate command to run instead of 'list' Some devices do not support the standard commands or may provide additional ones. Use this to specify an alternate, device-specific, command that implements the 'list' action. pcmk_monitor_action = string [monitor] Advanced use only: An alternate command to run instead of 'monitor' Some devices do not support the standard commands or may provide additional ones. Use this to specify an alternate, device-specific, command that implements the 'monitor' action. pcmk_status_action = string [status] Advanced use only: An alternate command to run instead of 'status' Some devices do not support the standard commands or may provide additional ones. Use this to specify an alternate, device-specific, command that implements the 'status' action. AUTHOR
Andrew Beekhof <andrew@beekhof.net> Author. Pacemaker Configuration 04/17/2012 STONITHD(7)
All times are GMT -4. The time now is 05:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy