The thing is more about stopping the use of mod_php in favor of fcgi
solution such as leave the php processing to php-fpm, that will enable you
to use the so much more performant event mpm in httpd, and from there you
will just have to proxy requests to php files from httpd to php-fpm through
mod_proxy_fcgi.

And yes trying to use anything other than prefork with such thing as
mod_php will be torture.

Move away from mod_php as soon as you can.

Regards

El jue., 29 de enero de 2015 5:37, David Benfell <benf...@parts-unknown.org>
escribió:

> Hi all,
>
> Ick. I still don't really know what my problem was. But I'm back up.
>
> I did recursive rebuilds of PHP and Apache, trying to get all the
> dependencies. I didn't actually make it all the way through Apache and
> I had to install the precompiled version of cmake to get through the
> PHP.
>
> In other words, I took a sledgehammer to it and somehow banged it back
> into shape. If only I could be so successful at this in real life.
>
> But I doubt this offers much help to anybody down the road.
>
> On Wed, Jan 28, 2015 at 08:40:33PM +0000, Daniel wrote:
> > Increase de debug log, those warnings indicate you have more than one
> directive
> > loading the same module, get rid of them too.
> >
> > But without further information and seeing how you use "service" and not
> a
> > httpd own script/binary to start httpd, it could be anything.
> >
> > I would try with apachectl start or running httpd directly to make sure
> and
> > increase the log to debug if you don't get enough info. Might be worth
> to try
> > your OS logs when you run "service".
>
> The maintainer apparently patches the apachectl script to use the
> service script, and the latter is, I have to confess, nearly
> indecipherable to me; I'm attaching it.
>
> I should have spotted this earlier:
>
> [Wed Jan 28 10:14:59.055026 2015] [mime_magic:error] [pid 49948] (2)No
> such file or directory: AH01515: mod_mime_magic: can't read magic file
> /usr/local/etc/apache24/conf/magic
>
> The file exists, but not in conf. Modifying the directive to point
> correctly did not address the problem.
>
> Changing the log level does not seem to have yielded further
> information. I've pasted in log snippets below.
> >
> > And yes, 2.4 + prefork + mod_php is by all means not a good combo.
>
> I tried rebuilding apache24 with worker, but it refused to recognize
> that I had built PHP with zend thread safety. So I tried event. It was
> only after that, that I realized that my problem was with the
> mod_php55 port build--I needed to select the zend thread safety option
> here as well.
>
>
> > Regards
> >
> > El Wed Jan 28 2015 at 19:16:18, David Benfell (<
> benf...@parts-unknown.org>)
> > escribió:
> >
> >     Hi,
> >
> >     This is on FreeBSD:
> >     FreeBSD home.parts-unknown.org 10.1-STABLE FreeBSD 10.1-STABLE #0
> r277815:
> >     Tue Jan 27 16:02:25 PST 2015     r...@home.parts-unknown.org:/
> usr/obj/usr/
> >     src/sys/GENERIC  amd64
> >
> >     [root@home ~]# httpd -V
> >     Server version: Apache/2.4.10 (FreeBSD)
> >     Server built:   Dec  3 2014 05:11:27
> >     Server's Module Magic Number: 20120211:36
> >     Server loaded:  APR 1.5.1, APR-UTIL 1.5.4
> >     Compiled using: APR 1.5.1, APR-UTIL 1.5.4
> >     Architecture:   64-bit
> >     Server MPM:     prefork
> >       threaded:     no
> >         forked:     yes (variable process count)
> >     Server compiled with....
> >      -D APR_HAS_SENDFILE
> >      -D APR_HAS_MMAP
> >      -D APR_HAVE_IPV6 (IPv4-mapped addresses disabled)
> >      -D APR_USE_FLOCK_SERIALIZE
> >      -D APR_USE_PTHREAD_SERIALIZE
> >      -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
> >      -D APR_HAS_OTHER_CHILD
> >      -D AP_HAVE_RELIABLE_PIPED_LOGS
> >      -D DYNAMIC_MODULE_LIMIT=256
> >      -D HTTPD_ROOT="/usr/local"
> >      -D SUEXEC_BIN="/usr/local/bin/suexec"
> >      -D DEFAULT_PIDLOG="/var/run/httpd.pid"
> >      -D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
> >      -D DEFAULT_ERRORLOG="logs/error_log"
> >      -D AP_TYPES_CONFIG_FILE="etc/apache24/mime.types"
> >      -D SERVER_CONFIG_FILE="etc/apache24/httpd.conf"
> >
> >     I think the problem is PHP related, because I've been messing with
> >     that, but nothing is telling me anything.
> >
> >     It's crashing pretty quickly, but this is all I get:
> >
> >     [root@home /usr/home/benfell]# service apache24 start
> >     Performing sanity check on apache24 configuration:
> >     [Wed Jan 28 10:14:58.295980 2015] [so:warn] [pid 49946] AH01574:
> >     module php5_module is already loaded, skipping
> >     Syntax OK
> >     Starting apache24.
> >     [Wed Jan 28 10:14:58.370798 2015] [so:warn] [pid 49947] AH01574:
> >     module php5_module is already loaded, skipping
> >     [root@home /usr/home/benfell]# service apache24 status
> >     apache24 is not running.
> >     [root@home /usr/home/benfell]#
> >
> >
> >     Help?
> >
> >     Thanks!
> >     --
> >     David Benfell <benf...@parts-unknown.org>
> >     See https://parts-unknown.org/node/2 if you don't understand the
> >     attachment.
> >
>
> --
> David Benfell <benf...@parts-unknown.org>
> See https://parts-unknown.org/node/2 if you don't understand the
> attachment.
>

Reply via email to