[Bug 225499] www/apache24: child pid exit signal Segmentation fault

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Feb 13 10:25:18 UTC 2018


Bernard Spil <brnrd at freebsd.org> changed:

           What    |Removed                     |Added
                 CC|                            |tz at freebsd.org

--- Comment #8 from Bernard Spil <brnrd at freebsd.org> ---
(In reply to O. Hartmann from comment #7)

Added tz@ hoping he can chip in from the PHP side.

So we've established that PHP actually can interpret things. Had't read the
complete thread previously. It also segfaults when running occ upgrade on the

I meant output of `php -m` so you can check if all your modules are loading OK.
Alternatively generate phpinfo() to see what loads and with what params.

I don't really have a clue what triggers this (but I have a port MariaDB 5.5
that doesn't build on CURRENT...). Were any Spectre/Meltdown mitigations added
in the newer CURRENT you use?

If your objective is running Nextcloud, you can run it with PHP 7.2 (after
update to Nextcloud 13, see PR #223778). Works fine for me. Running PHP 5.6
(ancient) on FreeBSD CURRENT (bleeding edge) is kind of weird... You will need
to upgrade PHP by end of this year anyway. You will have more flexibility if
you run PHP-FPM in jails (either unix domain sockets or TCP) as you can run
multiple PHP versions in parallel.

Your apache is built with all modules, I hope you're not loading them all at
runtime. Can you provide output of httpd -M (this one capital M) so we can see
what you load?

If I were to try and fix this for myself, I'd go back to bare minimum config
and enable modules one-by-one to figure out what makes it crash. You now have
both Apache and PHP with dynamically loaded modules, the number of combinations
is pretty much unlimited.

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-apache mailing list