Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 02 Apr 2004 08:24:06 -0800
From:      Drew Tomlinson <>
To:        Paul Reece <>
Subject:   Re: apache2 and php4.3.5 - segfault
Message-ID:  <>
In-Reply-To: <000001c4185d$bd91ca50$0402a8c0@penfold>
References:  <000001c4185d$bd91ca50$0402a8c0@penfold>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 4/1/2004 6:53 PM Paul Reece wrote:

>I'm having a few problems with Apache2.0.49 and PHP 4.3.5 - I've done a
>fresh install of both under FreeBSD 4.9-STABLE, but whenever I have PHP
>loaded, any signal sent to Apache2 (eg for a restart) results in the main
>Apache2 process segfaulting.. eg:
>[Fri Apr 02 10:33:27 2004] [notice] suEXEC mechanism enabled (wrapper:
>[Fri Apr 02 10:33:29 2004] [notice] Apache/2.0.49 (Unix) PHP/4.3.5
>mod_jk/1.2.5 mod_ssl/2.0.49 OpenSSL/0.9.7c configured -- resuming normal
>[Fri Apr 02 10:33:44 2004] [notice] SIGUSR1 received.  Doing graceful
>[Fri Apr 02 10:33:44 2004] [notice] seg fault or similar nasty error
>detected in the parent process
>If I simply remove PHP from the Apache configuration (ie, dont load the
>module), the above no longer occurs.
>I've tried with both the prefork and worker MPM's without any change in
>behavior - I've also reproduced this on a second machine, also running
>FreeBSD 4.9-STABLE (no mod_jk on that machine).
>Anyone else seeing the above or know a solution?
Search the archives as this was discussed a few days ago.  I don't use 
this combo but as I recall, the basic advice was to update your ports 
and reinstall PHP.  YMMV.



Want to link to this message? Use this URL: <>