TCP Port 9009, not accepting coonection

[vaman]

I have a problem application on tcp port 9009, is not accepting new connection, in ps -ef it shows as it is, started new process on same port, now ps -ef shows both processes on same port?
How can I see the TCP details of perticular port, & other details , I dont know mush about. this is hpux 11.11

[RAC_1]

What makes you think that application is listening on that port.

netstat -an|grep 9009
If you have lsof istalled,
lsof -p tcp:9009

Also from some other machine, telnet host 9009
Does it connect??

Anil

[Sanjay_6]

Hi,

Try lsof,

http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.73/

# lsof -i tcp:9009

Hope this helps.

Regds

[Biswajit Tripathy]

Run the following command to see which ports are
are ready to accept connection on your system:

# netstat -a | grep LISTEN

If port 9009 is not listed, then no application is
listening on that port.

"ps -ef" shows processes running on your system
and not connection status.

- Biswajit

[bhoopathi_1]

Hi
lsof -i tcp:9009 will give you the process name and pid listening in the port. Also you can check out netstat -a|grep CLOSE_WAIT. Check out if the particular application (listening on 9009) has too many CLOSE_WAITs. Then you need to clear these, either by doing a shutdown/startup of the application or if possible by ipcs -rm.

[rick jones]

To search for a given port number in netstat output, do not forget the -n option, so netstat -an | grep 9009

If the application has lots of CLOSE_WAIT connections, it implies the application is buggy and not closing connections like it should.

It is also possible to have hit maxfiles so no more file descriptors (sockets = file descriptors) no more connections. Accept() would return an error in that situation you could see with tusc syscall traces or the app should be logging it somewhere.

[Mark Greene_1]

You can download snort from here:

http://hpux.cs.utah.edu/hppd/hpux/Networking/Admin/snort-2.2.0/

install and run it while you try and connect to the HP from the client. This should give you the right information to tell if it's the HP or the client software that isn't handling the connection properly.

mark