16 Feb
2010
16 Feb
'10
10:18 p.m.
Michel-G. .Maria-Sube wrote:
ok.
Regards,
Alain
> What would be interesting to check is:
> 1. Find out what the process is called: do an lsof -i
> tcp:1154 while it
> works, and not the name of the process.
^
Ooops, should have been "note the name of the process"
Be sure to exclude firefox of course, if you have a connection right at
that time :-) We are interested in the process that is LISTENing on this
port, not in the clients that may be connecting to it...
Ok, for practical aspect I will use port 1158 here because I have
the same problem on two machine running under Suse10.* (one in 32b
the other in 64b); on current machine http is configurated on port
1158.
lsof -i tcp:1158 gives no answer
Weird... and you are sure that at this point in time, firefox was still
connecting?
When I'm launchig
firefox http://127.0.0.1:1158/apex
and ps -ax|grep firefox I obtain:
6505 ? S 0:00 /bin/sh /usr/bin/firefox
6510 ? Sl 0:40 /usr/lib64/firefox/firefox
6749 pts/28 S+ 0:00 grep firefox
Indeed, it's the server process that's important, not the client (which
is firefox obviously...)
I don't find any log-file at the moment
[...]
if you somehow
don't trust your browser or its settings,
you can try to
telnet directly to the port:
telnet localhost 1154
Once again connection is refused:
#telnet localhost 1158
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
Trying ::1...