Michael Lynch wrote: > I commented out the Listen 80 > in http.conf > and now its working. > > Does anybody know why this made it work?
==> I see that while I was composing this, JK has posted another suggestion. In such cases, you should stick with your original help-providers until you exhaust the suggestions there. It may be helpful to read someone else's analysis and advice (just to get "other words") -- or it may be harmful, distracting and even confusing (just getting "more words"). You'll have to use your judgment. I'm not convinced that was what made it work -- because that's a common and standard setting. I think, actually, that apache would STOP listening for http connections (and only listen for https connections -- that's port 443). That's what mine does when I comment out the Listen 80 line. I presume you mean httpd.conf, and more specifically /etc/httpd/conf/httpd.conf (just being sure) If you were talking about a different file, that might explain some things. If you were talking about the file I gave the path for, I suggest you do some more tests because otherwise you haven't really learned what what was wrong. I suggest trying to understand the meaning of the output from this command (run as root): netstat -lntp which is just a variation on the -pant version given by MO'K. This one reports only those tcp ports being LISTENed-on. The -p option (which requires root) is what shows (on the right) which program is doing the listening. When you get a chance, it is a good idea to do some research about _every_ program name on that list which you do not already know about --- this comes under the general security principle of knowing what services are running and why. In any case the interesting lines are for port 80 and for program httpd (the apache server). My f9 shows 2 relevant lines (of 11 total): >.. > tcp 0 0 :::80 :::* > LISTEN 2828/httpd >.. > tcp 0 0 :::443 :::* > LISTEN 2828/httpd >.. This means that process 2828 (program httpd) is listening on 2 ports -- 80 (http) and 443 (https). The ":::" simply stands for listening on all defined network interfaces (eg, lo, eth0, and anything else that shows up in ifconfig -a). Here's what comes to my mind as a way to understand what's going on. Look at the output of 'netstat -lntp' then close apache via 'service httpd stop'. Look at the netstat output once again just to see the difference. Shout if there is still something listening on port 80. Edit the httpd.conf file and un-comment the 'Listen 80' line again -- I assume there is only one line starting with "Listen", right? Start apache via "service httpd start" and look for error messages. If no messages, examine the netstat output. Let us know if service on port 80 does not show up -- that would deserve further exploring (such as posting the contents of /var/log/httpd/error_log). I'd be interested in seeing further results. Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
