[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#240961: apache segfaults on start

hi David,

On Mon, 29 Mar 2004, David Stipp wrote:

> On Tue, Mar 30, 2004 at 07:08:47AM +0200, Fabio Massimo Di Nitto wrote:
> > On Mon, 29 Mar 2004, David Stipp wrote:
> > > stat64("/dev/urandom", {st_mode=S_IFCHR|0666, st_rdev=makedev(1, 9),
> > > ...}) = 0
> > > --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> > > Process 11374 detached
> > >
> > > There was a bug where someone else encountered a SEGV (#230539) caused
> > > by recursively including the config files. I purged all of my config
> > > files and clean installed the package, and the problem persists.
> >
> > Not only. Which modules are you loading? (usual bunch of questions) did
> > you try to disable php4? did you try to disable mod_perl?
> Well, I seem to have traced down this problem here. When apache started
> working once I disabled php4, I started to twiddle with the php4 modules
> that were being loaded. I traced down the problem to the php4-imap
> module.
> Looks like this ticket should get bounced over that way.
> Thanks for your fast response.

It is a well known problem that goes way down to libc6. A temporary
workaround is to install libapache-mod-ssl and load it. There is no need
to configure it.

I am closing this bug since all the maintainers from php4 down to libc6
are aware and working actively on this problem. You can check the progress
directly from the BTS on the php4 page.


<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: