(98)Address already in use: make_sock: could not bind to address
xxx.xxx.xxx.x94:80
no listening sockets available, shutting down
I've been trying to figure out what xxx.xxx.xxx.xxx means. 0.0.0.0 is
used a lot for "default" and "use any incoming IP address" at the API level
(or something like that). I thought it might mean there's no address to
be had, but now it looks like maybe you're just disguising the numbers. In
which case, disregard my notion that it's trying to tell you something's wrong.
My own troubleshooting methods are to peek and poke at it with whatever
tools I can think of. Since I am an expert at few things, but a good
hacker in most. So I'd try "telnet localhost 80" (if it's not your machine
put the IP address in place of localhost) [1] and see if anything
answers. If something is listening on port 80 it will do something--even
if it's hang up on you (connection closed). Now I'm trying to think of
something that would take connections on a port that you could try to
run. I think I've got a dirt-simple server program I wrote while
experimenting with connections, but I'm not sure. Of course the likely
result would be the same (can't open the port...) that's how it usually
turns out.
Most of what I'm saying is for Jim's ears, to try to suggest ideas. I know
it may sound a little technical and rambling, mostly because it is.
Barry
[1] Reminds me, someone once had a problem because "localhost" wasn't being
turned on in the network setup. For this, try /sbin/ifconfig and look for
"lo" or 127.0.0.1
--
KPLUG-Newbie@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
