Arch Linux

jwm-art

Member

Registered: 2011-02-01

Posts: 87

PHP, Apache and FastCGI segfault

Hi,

Background: I'm trying to setup a web-dev environment similar to the shared hosting environment it eventually will go live on (ignoring I'm using Arch, and my webhost is using Debian). From some investigation I found my webhost has PHP running through Fast CGI, and that my PHP scripts are running as my user and my group (Debian: groupname == username). This is basically one of the things I want to do so that when I upload  my PHP scripts I'm not presented with any nasty surprises, I'd also like to setup custom 404 pages etc before going live too.

After a lot of searching I found this post: http://blog.foaa.de/2010/11/php-apache- … -overview/ which I followed with some customization after help from various related articles from the Arch Wiki.

However PHP files are not served, /usr/bin/php5-cgi segfaults:

Wed Oct 19 20:20:31 2011] [notice] caught SIGTERM, shutting down
[Wed Oct 19 20:22:34 2011] [warn] Init: Session Cache is not configured [hint: SSLSessionCache]
[Wed Oct 19 20:22:34 2011] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed Oct 19 20:22:34 2011] [notice] Digest: generating secret for digest authentication ...
[Wed Oct 19 20:22:34 2011] [notice] Digest: done
[Wed Oct 19 20:22:35 2011] [notice] FastCGI: wrapper mechanism enabled (wrapper: /usr/lib/httpd/modules/mod_suexec.so)
[Wed Oct 19 20:22:35 2011] [notice] FastCGI: process manager initialized (pid 1321)
[Wed Oct 19 20:22:35 2011] [warn] FastCGI: server "/srv/http/wrapper/fastcgi" (uid 1100, gid 1100) started (pid 1323)
[Wed Oct 19 20:22:35 2011] [warn] FastCGI: server "/srv/http/wrapper/fastcgi" (pid 1323) terminated due to uncaught signal '11' (Segmentation fault)
[Wed Oct 19 20:22:35 2011] [notice] Apache/2.2.21 (Unix) mod_ssl/2.2.21 OpenSSL/1.0.0e DAV/2 PHP/5.3.8 with Suhosin-Patch mod_fastcgi/2.4.6 configured -- resuming normal operations
[Wed Oct 19 20:22:40 2011] [warn] FastCGI: server "/srv/http/wrapper/fastcgi" (uid 1100, gid 1100) restarted (pid 1328)
[Wed Oct 19 20:22:40 2011] [warn] FastCGI: server "/srv/http/wrapper/fastcgi" (pid 1328) terminated due to uncaught signal '11' (Segmentation fault)
[Wed Oct 19 20:22:45 2011] [warn] FastCGI: server "/srv/http/wrapper/fastcgi" (uid 1100, gid 1100) restarted (pid 1330)
[Wed Oct 19 20:22:45 2011] [warn] FastCGI: server "/srv/http/wrapper/fastcgi" (pid 1330) terminated due to uncaught signal '11' (Segmentation fault)
[Wed Oct 19 20:22:50 2011] [notice] caught SIGTERM, shutting down

I don't know enough about server configuration to know what the problem is here... Is it my bad configuration causing the seg-fault, or is it a software bug somewhere (don't know where to start to get a backtrace or core dump)? Surely bad configuration (no matter how bad) shouldn't cause a seg-fault?

Thanks,
James.