Re: Bug#237377: apache: Apache parent process dies at reload
Hej Rasmus,
On Thu, 11 Mar 2004, Rasmus Bøg Hansen wrote:
> Package: apache
> Version: 1.3.26-0woody3
> Severity: important
> Tags: woody
>
[SNIP]
>
> I have loaded PHP4 and mod_ssl; no other external modules are configured
> nor installed.
>
> A log snippet from this morning:
>
> [Thu Mar 11 07:00:31 2004] [notice] SIGUSR1 received. Doing graceful restart
> accept_mutex_on: Identifier removed
> [Thu Mar 11 07:00:36 2004] [notice] Apache/1.3.26 (Unix) Debian GNU/Linux PHP/4.1.2 mod_ssl/2.8.9 OpenSSL/0.9.6g configured -
> - resuming normal operations
> [Thu Mar 11 07:00:36 2004] [notice] suEXEC mechanism enabled (wrapper: /usr/lib/apache/suexec)
> [Thu Mar 11 07:00:36 2004] [notice] Accept mutex: sysvsem (Default: sysvsem)
> [Thu Mar 11 07:00:36 2004] [alert] Child 31317 returned a Fatal error...
> Apache is exiting!
>
> No other logs tell anything about where the problem comes from.
> Logrotate just runs "/etc/init.d/apache reload".
>
> The server is not busy in any way; nor does it serve large files. It
> runs a simple web page and some php webmail (IMP2) over ssl; nothing fancy.
Unfortunatly this is a known problem that seems to be caused by several
different factors (php4, ssl, libcrypto and libc) and it can't be fixed in
woody. We are still waiting for a fix in sid (where bugs have been filed
towards the relevant packages). A possible workaround could be to change
the restart with a stop and start but this behaviour is unpredictable and
not always reproducible.
Mange Tak
Fabio
--
<user> fajita: step one
<fajita> Whatever the problem, step one is always to look in the error log.
<user> fajita: step two
<fajita> When in danger or in doubt, step two is to scream and shout.
Reply to: