Despite netstat not showing anything on port 80, for sanity sake have
you tried changing the bind address to something else, perhaps an
obscure port?
Dan
-Original Message-
From: Mike Watson [mailto:[EMAIL PROTECTED]
Sent: Friday, February 15, 2008 7:50 PM
To: users@httpd.apache.org
I do have a second NIC not connected. Let me check that and I'll get
back to you.
mw
Lose not thy airspeed lest the ground rises up and smites thee. - Anon.
Stusynski, Dan wrote:
Despite netstat not showing anything on port 80, for sanity sake have
you tried changing the bind address to
My intent is that anything to aristede.com:9080 should be redirected to
delegatenichols.com. However, Apache is ignoring the following in my
httpd.conf, even after I gracefully reboot.
VirtualHost *:9080
ServerAlias aristede.com
ServerSignature On
ErrorLog myError.log
LogLevel warn
IfModule
I added a second NIC with an IP of 192.168.1.5.
That worked! Eventually, I want to have a VirtualHost on that IP with
another on x.x.x.30.
Now why is x.x.x.30 failing? lsof -i:80 shows only the 2nd NIC
(x.x.x.5) using port 80.
Could there simply not be enough sockets configured? This,
On Feb 16, 2008 3:36 PM, Mike - W0TMW [EMAIL PROTECTED] wrote:
Any other ideas why x.x.x.30 is failing?
It's been suggested twice (once in the link I sent you and once by Dan
Mitton) to check httpd.conf and any Include'd files for superfluous
Listen statements that could be conflicting with
My apologies. I had checked httpd.conf many times and there was only
one Listen statement. However, since this is a fedora distro, I just
did a grep on /etc/httpd/conf.d and found several Listen statements
there. Apparently, I should have stayed using VI on the config instead
of trying to
Follow-up.
I deleted system-config-httpd.conf from /etc/httpd/conf.d and now httpd
lights off like it should. A word of warning to myself---don't take the
easy route. Use VI.
Thank you all.
Mike W
Lose not thy airspeed lest the ground rises up and smites thee. - Anon.
Joshua Slive
hello everybody
My web server got a problem long time.
It's cannot close finished httpd thread, i used ps -e to check server
got a lot of httpd thread like following:
20292 ? 00:00:01 httpd
4912 ? 00:00:00 cronolog
4913 ? 00:00:00 cronolog
4914 ? 00:00:00 cronolog
4915 ? 00:00:00 cronolog
4916
