[Catalyst] Apache2 and mod_perl deployment issue

Tomas Doran bobtfish at bobtfish.net
Mon Nov 14 22:31:31 GMT 2011


On 14 Nov 2011, at 19:24, Adam Jimerson wrote:
> Would strace be able to follow the fork, or would I be in the same  
> boat there?  The only thing that I can see that would be causing it  
> is a couple of lines like this:


Yes, it totally is (strace -f) - you just get the PID added..

> {SIG_DFL, [], SA_RESTORER|SA_RESTART, 0x7f6cbf4b9e10}, 8) = 0
> wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 23937
> wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 1}], 0, NULL) = 23938

Right - to it's waiting for child processes (as you're only seeing the  
parent without -f)

> Without the <Perl> block I get this error when trying to start  
> Apache2:
>
> startproc:  exit status of parent of /usr/sbin/httpd2-prefork: 1
>
> Without the PerlSwitches line that is what causes it to segfault.

This is just totally broken. You can segfault your apache/mod_perl by  
pushing onto @INC or similar..

You are using the prefork mpm, right?

Assuming you are - your distro's mod_perl is totally broken. Try their  
mod_fastcgi instead? Why are you deploying with mod_perl anyway?

Cheers
t0m




More information about the Catalyst mailing list