Thanks guys. Brad, I ran netstat and unbelievably only found a remote computer that I was connected to on *its* port 80. I had nothing happening on my own port 80. Weird.
Akshay, yup that worked. However, I am struggling to configure an instance of mediawiki, and didn't want any additinal weirdness what with moving to port 8080 on the web server itself. Anyway, I didn't have any files on the web server yet, so I just blew it away - uninstalled and reinstalled. Now the web server is working cheerfully. Still struggling with the mediawiki configuration, though. I point my browser at the index page, click on a link to hit a config file (which I have chmoded with 777) and then get told that I don't have permission to access the config file. Sigh. Solve one problem, move to the next .... PH. --- In [email protected], Akshay Lamba <[EMAIL PROTECTED]> wrote: > > Alternatively, setup your apache instance to bind to another port (8080 > maybe??) and see if that works just fine. > > A > > Brad Campbell wrote: > > > > profadourman wrote: > > > > > > > > The log files say nothing, as far as I can tell. I tried starting > > > httpd from the command line and got this error message back: > > > (98)Address already in use: make_sock: could not bind to address [::]:80 > > > (98)Address already in use: make_sock: could not bind to address > > > 0.0.0.0:80 > > > no listening sockets available, shutting down > > > Unable to open logs > > > > > > > So something else is listening on port 80 by the sounds of it.. try > > netstat -tnap as root > > > > [EMAIL PROTECTED]:~$ sudo netstat -tnap | grep 80 > > Password: > > tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 5206/thttpd > > > > Brad > > -- > > "Human beings, who are almost unique in having the ability > > to learn from the experience of others, are also remarkable > > for their apparent disinclination to do so." -- Douglas Adams > > > > >
