topic Re: how to kill running address in Operating System - HP-UX

how to kill running address

Kurtkarl — Thu, 05 Apr 2001 15:11:33 GMT

HI,

My informix engines needs to have a port running in order for remote server to connect to our local database. I have this entry on my /etc/services file

informix_db1 8735/tcp

Now everytime I run informix process that use this port number an error occurs which is

"# 25505 The sqlexecd daemon cannot bind a name to the socket.: Address already in use"

When I run to check the port if it's already in use and this port is really in use

# netstat -an | grep 8735
tcp 0 0 15.56.80.64.8735 *.* LISTEN

So my question is, is there a way to kill this port process so I can use it again and re-run my process?

Thanks in advance
Joey

Re: how to kill running address

Vincenzo Restuccia — Thu, 05 Apr 2001 15:46:59 GMT

tcp 0 0 15.56.80.64.8735 *.* LISTEN, kill it from application.

Re: how to kill running address

David Lodge — Thu, 05 Apr 2001 16:11:09 GMT

Another process is using the port - as to how to find the process, this is quite hard...

I'd advise using 'lsof' (need to download it from the HP porting archive) and searching for the application using it...

Re: how to kill running address

Carsten Krege — Thu, 05 Apr 2001 16:17:02 GMT

Before killing the process you should try to find out, which process is listening on this port. You can do this by running lsof on your machine.

Download lsof on http://gatekeep.cs.utah.edu and run it on your machine:

# ./lsof > lsof.out

The output shows you all open files for all processes running. You can then determine whether it is ok to kill the process that listens on the port.

If you have an idea what process is listening, you can also do this in glance (select process -> open files).

Carsten

Re: how to kill running address

Kevin Wright — Thu, 05 Apr 2001 17:25:59 GMT

the process you showed from the netstat is the daemon LISTENing for incoming requests. In your case, another connection must have died and terminated the connection without closing the port on the server..get lsof and run
lsof -i @hostname:portnumber
this will show you all active processes on the port number.