How to enable event MPM Apache 2.4 Ubuntu 14.04 with thread safe PHP?
I upgraded to Ubuntu server 14.04 expecting the default Apache installation would use the new event MPM, but instead I find the old memory-eating prefork.
I've successfully set up event MPM in Arch Linux, but I'm failing to do so on Ubuntu. I keep getting:
Apache is running a threaded MPM, but your PHP Module is not compiled to be threadsafe. You need to recompile PHP.
I've already installed php-fpm, and configured Apache2 to use it, but since the config files for Apache2 are different on Ubuntu, I'm not quite sure whether I'm doing it on the right place.
Any idea on how to make PHP thread safe so I can use Apache2 “event MPM”; without having to manually recompile PHP, of course?
installation php apache-http-server ubuntu-14.04
edited Sep 9 at 0:59
JakeGould
30.9k1093137
asked Apr 23 '14 at 5:32
Towerman
112
add a comment |
I upgraded to Ubuntu server 14.04 expecting the default Apache installation would use the new event MPM, but instead I find the old memory-eating prefork.
I've successfully set up event MPM in Arch Linux, but I'm failing to do so on Ubuntu. I keep getting:
Apache is running a threaded MPM, but your PHP Module is not compiled to be threadsafe. You need to recompile PHP.
I've already installed php-fpm, and configured Apache2 to use it, but since the config files for Apache2 are different on Ubuntu, I'm not quite sure whether I'm doing it on the right place.
Any idea on how to make PHP thread safe so I can use Apache2 “event MPM”; without having to manually recompile PHP, of course?
installation php apache-http-server ubuntu-14.04
edited Sep 9 at 0:59
JakeGould
30.9k1093137
asked Apr 23 '14 at 5:32
Towerman
112
add a comment |
I upgraded to Ubuntu server 14.04 expecting the default Apache installation would use the new event MPM, but instead I find the old memory-eating prefork.
I've successfully set up event MPM in Arch Linux, but I'm failing to do so on Ubuntu. I keep getting:
Apache is running a threaded MPM, but your PHP Module is not compiled to be threadsafe. You need to recompile PHP.
I've already installed php-fpm, and configured Apache2 to use it, but since the config files for Apache2 are different on Ubuntu, I'm not quite sure whether I'm doing it on the right place.
Any idea on how to make PHP thread safe so I can use Apache2 “event MPM”; without having to manually recompile PHP, of course?
installation php apache-http-server ubuntu-14.04
edited Sep 9 at 0:59
JakeGould
30.9k1093137
asked Apr 23 '14 at 5:32
Towerman
112
I upgraded to Ubuntu server 14.04 expecting the default Apache installation would use the new event MPM, but instead I find the old memory-eating prefork.
I've successfully set up event MPM in Arch Linux, but I'm failing to do so on Ubuntu. I keep getting:
Apache is running a threaded MPM, but your PHP Module is not compiled to be threadsafe. You need to recompile PHP.
I've already installed php-fpm, and configured Apache2 to use it, but since the config files for Apache2 are different on Ubuntu, I'm not quite sure whether I'm doing it on the right place.
Any idea on how to make PHP thread safe so I can use Apache2 “event MPM”; without having to manually recompile PHP, of course?
installation php apache-http-server ubuntu-14.04
installation php apache-http-server ubuntu-14.04
edited Sep 9 at 0:59
JakeGould
30.9k1093137
asked Apr 23 '14 at 5:32
Towerman
112
edited Sep 9 at 0:59
JakeGould
30.9k1093137
asked Apr 23 '14 at 5:32
Towerman
112
edited Sep 9 at 0:59
JakeGould
30.9k1093137
edited Sep 9 at 0:59
JakeGould
30.9k1093137
edited Sep 9 at 0:59
JakeGould
30.9k1093137
30.9k1093137
asked Apr 23 '14 at 5:32
Towerman
112
asked Apr 23 '14 at 5:32
Towerman
112
asked Apr 23 '14 at 5:32
Towerman
112
112
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
A small bit of speculation involved here, but I'm guessing that since you upgraded, rather than doing a clean install, your old Apache configuration (including mods-enabled) was not touched, as is typical. On a clean install of 14.04 LTS, event MPM is standard:
foo@CHANGEME-U14LTS:~$ ls /etc/apache2/mods-enabled/|grep mpm
mpm_event.conf
mpm_event.load
Your problem with PHP likely stems from similar in-place upgrade issues. Following the steps here on that same clean install was sufficient in getting PHP-FPM up and running on my test box.
Just to eliminate the obvious, you did remember to disable mod_php in your Apache config... right? Ubuntu's mod_php is not complied thread-safe; and if you still had mpm-prefork loading, there's a good chance that's still there, too. Regardless, I'd highly recommend moving your static web content to a clean install of 14.04, unless you want to sort through disabling all the old cruft and set up all the new best practices yourself.
answered May 2 '14 at 0:44
user5428
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f744907%2fhow-to-enable-event-mpm-apache-2-4-ubuntu-14-04-with-thread-safe-php%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
A small bit of speculation involved here, but I'm guessing that since you upgraded, rather than doing a clean install, your old Apache configuration (including mods-enabled) was not touched, as is typical. On a clean install of 14.04 LTS, event MPM is standard:
foo@CHANGEME-U14LTS:~$ ls /etc/apache2/mods-enabled/|grep mpm
mpm_event.conf
mpm_event.load
Your problem with PHP likely stems from similar in-place upgrade issues. Following the steps here on that same clean install was sufficient in getting PHP-FPM up and running on my test box.
Just to eliminate the obvious, you did remember to disable mod_php in your Apache config... right? Ubuntu's mod_php is not complied thread-safe; and if you still had mpm-prefork loading, there's a good chance that's still there, too. Regardless, I'd highly recommend moving your static web content to a clean install of 14.04, unless you want to sort through disabling all the old cruft and set up all the new best practices yourself.
answered May 2 '14 at 0:44
user5428
1
add a comment |
A small bit of speculation involved here, but I'm guessing that since you upgraded, rather than doing a clean install, your old Apache configuration (including mods-enabled) was not touched, as is typical. On a clean install of 14.04 LTS, event MPM is standard:
foo@CHANGEME-U14LTS:~$ ls /etc/apache2/mods-enabled/|grep mpm
mpm_event.conf
mpm_event.load
Your problem with PHP likely stems from similar in-place upgrade issues. Following the steps here on that same clean install was sufficient in getting PHP-FPM up and running on my test box.
Just to eliminate the obvious, you did remember to disable mod_php in your Apache config... right? Ubuntu's mod_php is not complied thread-safe; and if you still had mpm-prefork loading, there's a good chance that's still there, too. Regardless, I'd highly recommend moving your static web content to a clean install of 14.04, unless you want to sort through disabling all the old cruft and set up all the new best practices yourself.
answered May 2 '14 at 0:44
user5428
1
add a comment |
A small bit of speculation involved here, but I'm guessing that since you upgraded, rather than doing a clean install, your old Apache configuration (including mods-enabled) was not touched, as is typical. On a clean install of 14.04 LTS, event MPM is standard:
foo@CHANGEME-U14LTS:~$ ls /etc/apache2/mods-enabled/|grep mpm
mpm_event.conf
mpm_event.load
Your problem with PHP likely stems from similar in-place upgrade issues. Following the steps here on that same clean install was sufficient in getting PHP-FPM up and running on my test box.
Just to eliminate the obvious, you did remember to disable mod_php in your Apache config... right? Ubuntu's mod_php is not complied thread-safe; and if you still had mpm-prefork loading, there's a good chance that's still there, too. Regardless, I'd highly recommend moving your static web content to a clean install of 14.04, unless you want to sort through disabling all the old cruft and set up all the new best practices yourself.
answered May 2 '14 at 0:44
user5428
1
A small bit of speculation involved here, but I'm guessing that since you upgraded, rather than doing a clean install, your old Apache configuration (including mods-enabled) was not touched, as is typical. On a clean install of 14.04 LTS, event MPM is standard:
foo@CHANGEME-U14LTS:~$ ls /etc/apache2/mods-enabled/|grep mpm
mpm_event.conf
mpm_event.load
Your problem with PHP likely stems from similar in-place upgrade issues. Following the steps here on that same clean install was sufficient in getting PHP-FPM up and running on my test box.
Just to eliminate the obvious, you did remember to disable mod_php in your Apache config... right? Ubuntu's mod_php is not complied thread-safe; and if you still had mpm-prefork loading, there's a good chance that's still there, too. Regardless, I'd highly recommend moving your static web content to a clean install of 14.04, unless you want to sort through disabling all the old cruft and set up all the new best practices yourself.
answered May 2 '14 at 0:44
user5428
1
answered May 2 '14 at 0:44
user5428
1
answered May 2 '14 at 0:44
user5428
1
answered May 2 '14 at 0:44
user5428
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f744907%2fhow-to-enable-event-mpm-apache-2-4-ubuntu-14-04-with-thread-safe-php%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
