Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > Fedora 17/18 > Using Fedora
FedoraForum Search

Forgot Password? Join Us!

Using Fedora General support for current versions. Ask questions about Fedora and it's software that do not belong in any other forum.

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 13th December 2012, 02:08 AM
gjwalsh Offline
Registered User
 
Join Date: Feb 2011
Posts: 38
linuxfirefox
httpd.conf overly simplified

In F18 Beta, the configuration file for Apache (/etc/httpd/conf/httpd.conf) has been reduced from a 15 page listing to 5.

Yes, I know about the changes in packaging server modules, but I'm not packaging, I'm attempting to use the server.

For years, literally, I have edited httpd.conf to accomplish the following tasks (among others):

Turn KeepAlive On (for php needs)
Increase MaxKeepAliveRequests
Activate Extended Status
Add to DirectoryIndex
Allow local access to status and info reports
Reduce logging activity

followed by insertion of virtual hosts.

All of these sections have been wiped from httpd.conf.

To get a working server again, can I continue to use the proven edits from f17 and will that survive future fedora updates? Retyping or cutting and pasting all of this is asking for errors ......
Reply With Quote
  #2  
Old 13th December 2012, 08:01 PM
vallimar Online
Registered User
 
Join Date: Jul 2008
Posts: 809
windows_7chrome
Re: httpd.conf overly simplified

Sounds like you failed to notice the new /etc/httpd/conf.modules.d/ directory.
The configuration has been split out some, with some bits removed entirely.
Reply With Quote
  #3  
Old 13th December 2012, 08:29 PM
muep Offline
Registered User
 
Join Date: Jun 2006
Posts: 121
linuxfirefox
Re: httpd.conf overly simplified

All configuration syntax that you can use with Apache 2.2 of Fedora 17 will not work with Apache 2.4 of Fedora 18.

Regardless of what the default configuration looks like, you should be able to apply the full range of configuration supported by Apache Httpd 2.4. Documentation for it is available on Apache documentation website.
Reply With Quote
  #4  
Old 13th December 2012, 11:53 PM
gjwalsh Offline
Registered User
 
Join Date: Feb 2011
Posts: 38
linuxfirefox
Re: httpd.conf overly simplified

Thanks for responding.

I began with the f17 httpd.conf file and commented out the Load Modules in favor of those in /etc/httpd/conf.d/conf.modules.d/00-base.conf .. so yes, I'm familiar with the 'new' conf.modules.d directory.

Now configtest complains that MPM is not set. Since apache states that MPM is set by default unless I overrule it, my next step is to try to determine with what options the fedora system was built and use that as a starting point to address this 'mess'.

Aside from needing to set the most basic options I do not see how I have changed much in the way of syntax. I was simply trying to preserve what has served me well for years, including DSO modules, but there is no visible attempt to provide for this in the compressed httpd.conf of F18 in any event, so it will be hit and miss.

Unless I can determine how httpd was bulit and with what options, there isn't much I can do when configtest reports knowing nothing of MPM .....

---------- Post added at 03:11 PM ---------- Previous post was at 02:43 PM ----------

Regarding MPM not being loaded:

Here is the /etc/httpd tree:

/etc/httpd
|-- conf
| |-- httpd.conf
| |-- httpd.conf.fedora
| `-- magic
|-- conf.d
| |-- autoindex.conf
| |-- awstats.conf
| |-- geoip.conf
| |-- mod_security.conf
| |-- php.conf
| |-- phpPgAdmin.conf
| |-- README
| |-- ssl.conf
| |-- ssl.conf.fedora
| |-- userdir.conf
| |-- w3c-markup-validator.conf
| `-- welcome.conf
|-- conf.modules.d
| |-- 00-base.conf
| |-- 00-dav.conf
| |-- 00-lua.conf
| |-- 00-mpm.conf
| |-- 00-proxy.conf
| |-- 00-ssl.conf
| |-- 00-systemd.conf
| |-- 01-cgi.conf
| |-- 10-geoip.conf
| |-- 10-mod_security.conf
| `-- 10-php.conf
|-- logs -> ../../var/log/httpd
|-- modsecurity.d
| `-- activated_rules
|-- modules -> ../../usr/lib64/httpd/modules
`-- run -> /run/httpd

and here is the content of 00-mpm.conf:

# Select the MPM module which should be used by uncommenting exactly
# one of the following LoadModule lines:

# prefork MPM: Implements a non-threaded, pre-forking web server
# See: http://httpd.apache.org/docs/2.4/mod/prefork.html
LoadModule mpm_prefork_module modules/mod_mpm_prefork.so

# worker MPM: Multi-Processing Module implementing a hybrid
# multi-threaded multi-process web server
# See: http://httpd.apache.org/docs/2.4/mod/worker.html
#
#LoadModule mpm_worker_module modules/mod_mpm_worker.so

# event MPM: A variant of the worker MPM with the goal of consuming
# threads only for connections with active processing
# See: http://httpd.apache.org/docs/2.4/mod/event.html
#
#LoadModule mpm_event_module modules/mod_mpm_event.so

..... which would supposedly load mod_mpm_prefork ....

---------- Post added at 03:53 PM ---------- Previous post was at 03:11 PM ----------

Finally:

mod_mpm_prefork.so appears in /usr/lib64/httpd/modules listing

I installed conf 'out-of-the-box' without edits of any kind and configtest still reports: 'no mpm loaded'.

So I am satisfied that no changes I might have made are present at this point.

Last edited by gjwalsh; 13th December 2012 at 10:44 PM. Reason: typos
Reply With Quote
  #5  
Old 14th December 2012, 06:21 PM
vallimar Online
Registered User
 
Join Date: Jul 2008
Posts: 809
windows_7chrome
Re: httpd.conf overly simplified

I've had no such issues for the past few months running httpd in F18.
Check the DSO section in /etc/httpd/conf/httpd.conf and make sure that
you didn't disable or remove the line that says: Include conf.modules.d/*.conf
That line is what loads all those split-config files, which tell Apache what mpm to load, etc.
Reply With Quote
  #6  
Old 14th December 2012, 11:14 PM
gjwalsh Offline
Registered User
 
Join Date: Feb 2011
Posts: 38
linuxfirefox
Re: httpd.conf overly simplified

Oh its there, OK, line 56 of the /etc/httpd/conf/httpd.conf file as it came from fedora, without editing.

3 full days of this is far too much aggravation, even for me. I've been running apache servers since the early 1970's and except for a problem 6 years or so back, which I finally resolved by simply getting rid of the distro's version and building/compiling from source, it looks like I might find myself in that position once more. It took all of 25 minutes to edit the F17 conf file, the ssl.conf file and the virtual hosts.

What has changed? Inability to load rpms at the package level, and what looks like an absence of required handlers which used to be in httpd.conf. Lord knows where they are now ..... but I'm not putting them in at this stage. I'll worry about a functional httpd later.
Reply With Quote
Reply

Tags
httpdconf, overly, simplified

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
httpd: Syntax error on line 53 of /usr/local/apache2/conf/httpd.conf: Cannot load /us Kingtu Servers & Networking 2 5th April 2007 12:54 AM
ci problems with /etc/httpd/conf/httpd.conf lonelylost_brar Servers & Networking 2 8th June 2005 08:17 PM


Current GMT-time: 13:15 (Saturday, 25-05-2013)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat