top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

What is the default MPM in apache on CentOS 7?

+1 vote
429 views
What is the default MPM in apache on CentOS 7?
posted Sep 4, 2014 by Jai Prakash

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
0 votes
ssi not working on virtual host, using CentOS 6.0 with Apache 2.2.15

I am using CentOS 6.0 with Apache 2.2.15, and set up Apache with virtual host. The SSI works fine on the first VH, but ssi on the other virtual hosts does not work. I got the following message in the error log: 

mod_include: Options +Includes (or IncludesNoExec) wasnt set, INCLUDES filter removed

Does anyone know how to resolve this problem?

+1 vote
cookie and RewriteCond on Apache

I use apache 2.4 on centos.

I want to protect the access to a page (/my_folder/secure) with a cookie (in my exemple the cookie name is : my_cookie_name)

I would like that some machine with IP 192.1.1.10 and 192.1.1.11 can access the server without the cookie. This two IP address don't need to have the cookie for access to /my_folder/secure)

And all other IP address are redirect to address https://my_register_site.com if they don't have the cookie.

How to write this ? Some example, and of course it does not work. 

Session On 
RewriteEngine on 
RewriteCond %{HTTP_COOKIE} !my_cookie_name 
RewriteCond %{REMOTE_ADDR} !^192.1.1.10$ 
RewriteCond %{REMOTE_ADDR} !^192.1.1.11$ 
RewriteRule ^(.*)$ https://my_register_site.com [NC,L,R=301]
0 votes
Worker MPM with kill in Apache

I started apache server which has worker as mpm in debug mode. I killed the process with kill -9 then it kills the process and stop debug. But when I am using kill -term PID then it is not killing process. Whereas kill -term PID is woking with prefork debug.Â
If I want to use kill -term PID in debug mode of worker then how to do that.

0 votes
Apache 2.2.22 mpm-prefork workers hanging - timeouts

We have apache running over https with a module that provides a proxy to (interalia) websockets and tcp sessions. Source is at:
https://github.com/abligh/apache-websocket (if anyone is interested.)

Following a relatively recent upgrade to apache (sadly I don't know which, but somewhere between Lucid and Precise), we ended up with some worker processes that hang with 100% CPU usage. Investigation with gdb shows this appears to be the destruction of the output bucket brigade going around and around without ever terminating. No data is flowing (obviously). These hung processes will persist for days.

No doubt there is a bug either in our module or apache that causes this, but I'm more interested in how apache kills runaway workers, or more accurately why it's not killing them here.

We are using:

 RequestReadTimeout body=300,minrate=1

This should require a minimum data rate of 1 byte per second. Is RequestReadTimeout only checked if the process actually is in/exiting select()? If so, how do I do a watchdog?

Or is the issue that minrate 1 with a previous sensible datarate generates an enormous timeout value that might be in days? If so is the right approach:

RequestReadTimeout body=300-3600,minrate=1

or similar?

We're now using:

apache2-mpm-prefork 2.2.22-1ubuntu1.2
Server version: Apache/2.2.22 (Ubuntu)
Server built: Nov 8 2012 21:37:30
...