Re: httpd.conf error causes apache not to load
![](https://seccdn.libravatar.org/avatar/686bcf8ee9a8602e8b32ed99e9c1691d.jpg?s=120&d=mm&r=g)
Hi Robert:
Nope, the install is straight from the upgrade CD for 7.0. Must be the latest on the CD if that is the issue.
Boy I don't know what it could be. Go to the Suse Support Data base and type in "apache" or "httpd" in the keyword search. That should give something if indeed it is a quirk in the distribution. I would advise against getting the bug fixes for apache or mod_php as they offer only trifling security improvements and appear to disable the apache web server. I have exactly the behavior you describe: can't access local help files. That's why I
Message-Id: <200012120345.WAA13013@demai05.mw.mediaone.net>
Date: Mon, 11 Dec 2000 22:37:50 -0500
From: Robert
was the updates. Before those two bug fixes, SuSE 7.0 worked fine.
Jonathan
![](https://seccdn.libravatar.org/avatar/123c73f5bbd6a6c6f5f419ffb4316862.jpg?s=120&d=mm&r=g)
From: Álvaro A. Novo
Jonathan,
Did check the online FAQ and DB @ suse.de & .com with no luck. Tried to go through the httpd.conf file put too larage and don't know what all the options stand for ... not yet anyway.
I did not bothered checking which package is the culprit, but if you uninstall the apache modules (do a search in YaST keyword "apache", make a list if you need them later) and keep apache (ONLY) -- then the error message goes away and httpd fires up... if you really need the modules, install one by one until you detect the "bad guy"... and let us know... Alvaro Novo SuSE 6.4 -=- Kernel 2.2.17 -=- KDE 2.0.1 9:55pm up 1 day, 9:21, 5 users, load average: 0.00, 0.00, 0.00
![](https://seccdn.libravatar.org/avatar/dad27147dfdd227ecdc9f25af9c9efc4.jpg?s=120&d=mm&r=g)
Date: Tue, 12 Dec 2000 15:15:55 +0000 (WET)
From: "Nuno Fernando Higgs (Admin)"
On Monday 11 December 2000 21:37, Robert wrote:
Jonathan,
Did check the online FAQ and DB @ suse.de & .com with no luck. Tried to go through the httpd.conf file put too larage and don't know what all the options stand for ... not yet anyway.
I did not bothered checking which package is the culprit, but if you uninstall the apache modules (do a search in YaST keyword "apache", make a list if you need them later) and keep apache (ONLY) -- then the error message goes away and httpd fires up... if you really need the modules, install one by one until you detect the "bad guy"... and let us know...
Alvaro Novo
SuSE 6.4 -=- Kernel 2.2.17 -=- KDE 2.0.1 9:55pm up 1 day, 9:21, 5 users, load average: 0.00, 0.00, 0.00
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
participants (3)
-
novo@uiuc.edu
-
nuno@chackal.dyndns.org
-
rwarner@mediaone.net