ermes ha scritto:aggiornato ancora.... i problemi sembrano risolti
ho un solo altro problema:
uso librerie pear con php... e dopo questo aggiornamento tutte le applicazioni che usano queste librerie sono inservibili.
succede a qualcun altro ?
ermes ha scritto:uso librerie pear con php... e dopo questo aggiornamento tutte le applicazioni che usano queste librerie sono inservibili.
bash-4.2# /etc/rc.d/rc.httpd restart
[Wed May 23 11:13:19.910042 2012] [:crit] [pid 20648:tid 3070121728] Apache is running a threaded MPM, but your PHP Module is not compiled to be threadsafe. You need to recompile PHP.
AH00013: Pre-configuration failed
# A brief note about mpms:
# "prefork" is the legacy forked mpm, used with mod_php. Starting with httpd
# 2.4.0, new threaded mpms are available, and previously experimental mpms are
# now stable
# Non-threaded mpms are no longer required, since php applications can now be
# deployed with the help of mod_fcgid, essentially a set of fixed dedicated cgi
# processes spawned for the whole purpose of executing dynamic applications
# Threaded mpms, by their very nature, are far more scalable than the
# traditional preforking solution. They consume less memory for the same
# workload, when serving the same amount of clients. httpd 2.4 ships with two
# options, "event" and "worker", where the former is the default mpm used if
# none is specified at the ./configure line
# Lastly, the "prefork" mpm can be used with mod_php as of version 5.4.0,
# which yields a much improved stability, even with most mod_php extensions
# The running mpm can be changed by simply loading the module. Here is a sample:
# LoadModule mpm_event_module lib(64)/httpd/modules/mod_mpm_event.so
# When upgrading from 2.2, please make sure to stop the deamon first, or your
# new instance may segfault.
ponce ha scritto:con la configurazione di default funziona tranquillamente.
probabilmente, ma e' un'ipotesi mia, state provando a farlo girare usando le vecchie.
secondo me, in questo caso, vi conviene mettere da una parte i vecchi file di configurazione e adattare i nuovi spostando solo le parti che vi interessano (sia per php che per apache) dando un'occhiata alle modifiche con diff.
conraid@blackstar:/etc/httpd$ diff httpd.conf httpd.conf.new
< #LoadModule mpm_event_module lib64/httpd/modules/mod_mpm_event.so
< LoadModule mpm_prefork_module lib64/httpd/modules/mod_mpm_prefork.so
> LoadModule mpm_event_module lib64/httpd/modules/mod_mpm_event.so
< DirectoryIndex index.html index.php
> DirectoryIndex index.html
< Include /etc/httpd/mod_php.conf
> #Include /etc/httpd/mod_php.conf
conraid@blackstar:/etc/httpd$ diff php.ini php.ini-development
Why shouldn't I use Apache2 with a threaded MPM in a production environment?
PHP is glue. It is the glue used to build cool web applications by sticking dozens of 3rd-party libraries together and making it all appear as one coherent entity through an intuitive and easy to learn language interface. The flexibility and power of PHP relies on the stability and robustness of the underlying platform. It needs a working OS, a working web server and working 3rd-party libraries to glue together. When any of these stop working PHP needs ways to identify the problems and fix them quickly. When you make the underlying framework more complex by not having completely separate execution threads, completely separate memory segments and a strong sandbox for each request to play in, further weaknesses are introduced into PHP's system.
If you want to use a threaded MPM, look at a FastCGI configuration where PHP is running in its own memory space.
SSH root@asustar:/etc/httpd# apachectl start
[Wed May 23 14:50:07.707395 2012] [:crit] [pid 2282:tid 3070101248] Apache is running a threaded MPM, but your PHP Module is not compiled to be threadsafe. You need to recompile PHP.
AH00013: Pre-configuration failed
Visitano il forum: Nessuno e 1 ospite