Sponsored Content
Special Forums IP Networking Need to know reason for connections closed in netstat -p tcp Post 302899593 by vbe on Wednesday 30th of April 2014 09:34:56 AM
Old 04-30-2014
And so the command line in post #2 would have worked then...
 

8 More Discussions You Might Find Interesting

1. SCO

tcp port always closed in inetd

sco unix 5.0.x, several weeks ago, I add a telnet-like service in inetd.conf, it runs well for 100 network terminals. But nowdays, the terminals can connect to server successfully after booting machine, but several hours later, can not connect. "netstat -p tcp -a" can NOT find the port in... (1 Reply)
Discussion started by: shark_gao
1 Replies

2. Post Here to Contact Site Administrators and Moderators

Thread was closed without a valid reason

Dear Administrators, I think Mr. Vino is one of your Moderators here because he closes this thread: https://www.unix.com/showthread.php?p=302086230#post302086230 without a valid reason. Rule 7 states no headhunters or recruiters, but career advice is not prohibited here i think, because it... (2 Replies)
Discussion started by: patras
2 Replies

3. SCO

all tcp are CLOSED on SCO Unix on VMWARE

Hi folks, First of all, sorry about my english, isn't the best and thks for advance. Here es my problem... I have virtualize an SCO unix with VMware ESX 3 and everything was going on beatifull until that i try to connect from anorther host, i can't do it so i check the connection with... (5 Replies)
Discussion started by: martocapo
5 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. UNIX for Dummies Questions & Answers

TCP failed connection attempts from netstat -s

Dear experts, I am seeing a lot of TCP failed connection attempts from "netstat -s" on one of our servers. How can I pin point what connection failed and what are the ports involved? Any tools/commands I can dig in deeper to diag. what went wrong on these "failed connection attempts"? ... (2 Replies)
Discussion started by: cache51
2 Replies

7. Solaris

Connections closed for all applications

I've recently installed Solaris 10 10/9 in a new Dell Power Edge 630. Whenever I try to telnet, ssh, or FTP TO this box FROM another box on the same network segment, the following occurs: Roughly 80% of the time I get "Unable to connect to remote host: Connection refused" The remaining 20%... (0 Replies)
Discussion started by: cvaughn
0 Replies

8. IP Networking

Connections not shown in netstat output

I have a TCPIP server application (a Vendor package) which by default allows 10 connections. It provides a parameter to allow us to increase the maximum allowable connections in case it is needed. Intermittently this application is failing with maximum number of connections reached even when there... (1 Reply)
Discussion started by: AIX_user
1 Replies
MONGOCLIENT.CLOSE(3)							 1						      MONGOCLIENT.CLOSE(3)

MongoClient::close - Closes this connection

SYNOPSIS
public bool MongoClient::close ([boolean|string $connection]) DESCRIPTION
The MongoClient.close(3) method forcefully closes a connection to the database, even if persistent connections are being used. You should never have to do this under normal circumstances. PARAMETERS
o $connection - If connection is not given, or FALSE then connection that would be selected for writes would be closed. In a single-node config- uration, that is then the whole connection, but if you are connected to a replica set, close() will only close the connection to the primary server. If connection is TRUE then all connections as known by the connection manager will be closed. This can include connections that are not referenced in the connection string used to create the object that you are calling close on. If connection is a string argument, then it will only close the connection identified by this hash. Hashes are identifiers for a con- nection and can be obtained by calling MongoClient.getConnections(3). RETURN VALUES
Returns if the connection was successfully closed. EXAMPLES
Example #1 MongoClient.close(3) example This example demonstrates how to selectively close all connections for secondaries only. <?php // Connect to a replicaset $a = new MongoClient("mongodb://whisky:13000/?replicaset=seta"); $connections = $a->getConnections(); foreach ( $connections as $con ) { // Loop over all the connections, and when the type is "SECONDARY" // we close the connection if ( $con['connection']['connection_type_desc'] == "SECONDARY" ) { echo "Closing '{$con['hash']}': "; $closed = $a->close( $con['hash'] ); echo $closed ? "ok" : "failed", " "; } } ?> The above example will output: Closing 'whisky:13001;X;4948': ok CHANGELOG
+--------+---------------------------------------------------+ |Version | | | | | | | Description | | | | +--------+---------------------------------------------------+ | 1.3.0 | | | | | | | The $connection parameter to this function was | | | added in 1.3.0. Before that, only the write con- | | | nection would be closed by this method. | | | | | 1.2.0 | | | | | | | Before version 1.2.0 the driver would not use | | | persistent connections by default, and all con- | | | nections would be closed as soon as a MongoDB | | | connection went out if scope. Since version 1.2.0 | | | this is no longer the case and it is a bad idea | | | to call close as you might end up overloading the | | | server with connections under high load. | | | | +--------+---------------------------------------------------+ SEE ALSO
MongoClient.getConnections(3). PHP Documentation Group MONGOCLIENT.CLOSE(3)
All times are GMT -4. The time now is 05:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy