Operating System - HP-UX
1753788 Members
7342 Online
108799 Solutions
New Discussion юеВ

Re: Port opening issue in Hpux

 
Sreer
Valued Contributor

Port opening issue in Hpux

Hi Gurus,

I have an issue in my hpux box 11.11.
My application users are trying to configure a software in the sever.
"
Reason is that the software does not open a port can on which she listens to clients.
In the log files to find the following line:
ERROR PlainServerWorkerThread73 pvar.server.MyRMISocketFactory - problem creating socket: Connection timed out (errno 238)

I also tried using other software to open a port. Here comes the message:
Address already in use (errno: 226)

Because the error occurs and regardless of pVar pVar on the test machine (server2) runs smoothly, there should be a operating system problem. "

Iam not sure about the portmanagement.

Could you pls help me how to confirm if there is some issue with Operating system?

netstat -a | grep -i listen
tcp 0 0 *.2818 *.* LISTEN
tcp 0 0 *.60089 *.* LISTEN
tcp 0 0 *.8100 *.* LISTEN
tcp 0 0 *.5989 *.* LISTEN
tcp 0 0 *.registrar *.* LISTEN
tcp 0 0 *.stat *.* LISTEN
tcp 0 0 *.6287 *.* LISTEN
tcp 0 0 *.3275 *.* LISTEN
tcp 0 0 *.9495 *.* LISTEN
tcp 0 0 *.chargen *.* LISTEN
tcp 0 0 *.klogin *.* LISTEN
tcp 0 0 *.dtspc *.* LISTEN
tcp 0 0 *.recserv *.* LISTEN
tcp 0 0 *.ssh *.* LISTEN
tcp 0 0 *.49154 *.* LISTEN
tcp 0 0 *.ftp *.* LISTEN
tcp 0 0 *.10014 *.* LISTEN
tcp 0 0 *.49173 *.* LISTEN
tcp 0 0 *.49160 *.* LISTEN
tcp 0 0 *.49194 *.* LISTEN
tcp 0 0 *.49416 *.* LISTEN
tcp 0 0 *.49295 *.*

Most of the ports are in Listening state.
And not sure why the errror happening to configure the appli...

Thanks
Rgds Sree


4 REPLIES 4
Larry Klasmier
Honored Contributor

Re: Port opening issue in Hpux

What port are you trying to open? I looks likes something else may already be using that port. Use netstat to see if the port you app needs is already in use.
kevin_m
Valued Contributor

Re: Port opening issue in Hpux

The lsof command may be useful if you want to determine which process is using the port.

/usr/local/bin/lsof -i :

If it's not installed you can download from the Porting and Archive Center at http://hpux.connect.org.uk/

- Kevin
Steven E. Protter
Exalted Contributor

Re: Port opening issue in Hpux

Shalom,

Need to know what port the software is supposedly listening on:

export PORT=
netstat -an | grep ":${PORT} "

If you already have a process listening, you have a conflict. If not its a different kind of application error.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Steven Schweda
Honored Contributor

Re: Port opening issue in Hpux

> [...] my hpux box 11.11.

Actual output from "uname -a" is always nice.

> [...] a software [...]

Not a very useful description of anything.

> Reason is that the software does not open
> a port can on which she listens to
> clients.

Says who? Evidence?

> [...] other software [...]

Not a very useful description of anything.

> [...] Connection timed out (errno 238)

Normally, if no program is listening at a
particular port, then the client will get a
"Connection refused" complaint, not
"Connection timed out".

> [...] Address already in use (errno: 226)

Which also suggests that the server
(whatever it might be) is running.

> What port are you trying to open?

A fair question.

> Because the error occurs and regardless of
> pVar pVar on the test machine (server2)
> runs smoothly, there should be a operating
> system problem. "

Huh? What, exactly, is "the se[r]ver"?
What, exactly, is "the test machine
(server2)"? What, exactly, does "runs
smoothly" mean here?

As usual, showing actual commands with their
actual output can be more helpful than vague
descriptions and interpretations.


> [...] Connection timed out (errno 238)

My first guess would be some basic network
problem. Can these systems talk to each
other using, say, Telnet or FTP? If the
server has no route back to the client, for
example, then replies from the server may
never reach the client, and that might cause
a time-out.