11-20-2009
Thanks for the reply jlliagre,
Due the application urgency we are forced to go for the application (weblogic server restart to kill the connections ) then the connection status went to FIN_WAIT_1 from ESTABLISHED and later on it dissappered. Now BAU.
But the appplication bug is there so we may need to find out other than the application restart.
I followed the way you shown and i have find out the process but again it was the weblogic server running on the system. which means in order to kill the connection i need to kill/stop the weblogic server
'
But any way great learning !!
Thanks again for your patience in explaining this
Cheers
GIC
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi Experts,
need help about release or refresh TCP Connection:
i have the sample like below :
application log connection:
0500 ( 192.168.0.1:36053) 00919 2007/05/10 23:30:25 112 13 2007/05/10 23:30:25 1969/12/31 17:00:00
0500 ( 192.168.0.1:36054) 00920 2007/05/10 23:30:26 000 00... (3 Replies)
Discussion started by: bucci
3 Replies
2. UNIX for Dummies Questions & Answers
I wrote a very simple script to calculate the DB connection from an appserver and check the total netstat connection to a particular DB exceed 25 then it will send mail
netstat -a 2> /dev/null | awk '/.*ESTAB/{print $5}' | cut -d. -f1 | uniq -c | awk '{if ($1 > 25)print $2," exceed ",$1;}'
... (1 Reply)
Discussion started by: senthil.ak
1 Replies
3. Red Hat
How to kill all active tcp connections from an IP?
I am using CentOS (3 Replies)
Discussion started by: an00p
3 Replies
4. UNIX for Advanced & Expert Users
Hi - I frequently run commands, and transfer files to/from a host that uses SecurID ssh authentication. It is a real pain to have to enter the authentication information every time I want to interact with this host. I am wondering if there is a way to establish a one-time ssh connection to this... (2 Replies)
Discussion started by: cpp6f
2 Replies
5. UNIX for Dummies Questions & Answers
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
6. Shell Programming and Scripting
HI
I know that it sounds crazy :eek:
appreciated if any one provided me a solution for my below case , the below script is checking the Database availability on many servers by establishing rsh session ( one by one ) , sometime one of the servers goes down and while this the script taking... (0 Replies)
Discussion started by: bejo4ever
0 Replies
7. Red Hat
Hi,
I want to kill TCP connections which have status as TIME_WAIT & no PID
(as per the output of the "netstat - p" command).
Is there any command/utility available to kill connections to a specific port or IP address.
The problem is that these connections don't have process ID (see... (4 Replies)
Discussion started by: Davinder31may
4 Replies
8. IP Networking
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
9. AIX
I'm trying to configure a firewall for AIX to accept incoming connections on ports 22 and 443 and deny everything else. All is ok; the server accepts connections only on 22 and 443, but after that I also need to accept all outgoing connections -- ssh and telnet, for example. So I started with
... (0 Replies)
Discussion started by: Michael1457
0 Replies
10. UNIX for Advanced & Expert Users
Good morning, I need your help please
After Restarting Aps or connection, these are connections
tcp 0 0 10.80.1.26.57597 10.81.248.79.53008 ESTABLISHED
tcp 0 47 10.80.1.26.57607 10.81.248.79.53008 ESTABLISHED
tcp 0 0 ... (4 Replies)
Discussion started by: alexcol
4 Replies
pcastctl(8) BSD System Manager's Manual pcastctl(8)
NAME
pcastctl -- Podcast Producer daemons control interface
SYNOPSIS
pcastctl status target on|off|start|stop|restart
OPTIONS
The available options are as follows:
status print status of running daemons
target affect agent or server daemon
start|stop|restart explicitly start/stop/restart daemon. Note that 'restart' will kill all instances of a given daemon, as will
'stop' if none is specified in the pid file.
RETURN VALUES
0 Completed succesfully.
1 Action failed
10 Not run as root.
50 Target not recognized: use 'a', or 's'.
51 Action not recognized: use start|stop|restart
52 Executables not found; may need to reinstall Podcast Producer.
53 Process directory not found; may need to reinstall Mac OS X.
54 Timeout waiting for action to complete.
55 Launchd manipulation failure.
FILES
/usr/libexec/podcastproducer/pcastagentd
Podcast Producer agent daemon
/usr/share/podcastproducer/pcastserverd
Podcast Producer server daemon
/var/run/pcastagentd.pid
Podcast Producer agent process ID
/var/run/pcastserverd.pid
Podcast Producer server process ID
/System/Library/LaunchDaemons/com.apple.pcastagentd.plist
Launchd agent daemon control file
/System/Library/LaunchDaemons/com.apple.pcastserverd.plist
Launchd server daemon control file
EXAMPLES
status of Podcast Producer agent daemon
$ pcastctl agent status
edit launchd configuration to launch server on system startup
$ pcastctl server on
DIAGNOSTICS
Warning: Warning: ## copies of (pcastagentd|pcastserverd) already running
Trying to launch another daemon when one or more already running; will usually succeed, but may cause unpredictable behavior.
See also RETURN VALUES, above.
ERRORS
Error: failed to launch (executable)
Tried to start/restart a give daemon, but failed.
Error: process 'executable' not currently running
Tried to kill a process which did not exist.
SEE ALSO
pcast(1) launchd(8)
HISTORY
This program was first introduced in Mac OS X 10.5 "Leopard". It was inspired by xgridctl(8).
BUGS
pcastctl(8) uses kill -TERM to allow the daemons a chance to die gracefully; there is currently no way to force a kill -KILL.
Bug reports can be sent to bugreport.apple.com
Feedback can be sent to podcastproducer@apple.com
Mac OS September 29, 2004 Mac OS