Apache Signal 11 (5.3-RELEASE-p3/4)

Vlad marchenko at gmail.com
Sat Mar 19 04:58:16 PST 2005


I have the same problem, started at some point since 5.3-p?

I thought something is wrong with the particular server, but since
other people report the same issue, I started to doubt that.

Apache has been built manually, so it has nothing to do with the port.
1.3.33 Apache + mod_ssl + mod_perl

Sorry, have no dumps.

pid 70686 (httpd), uid 65534: exited on signal 11
pid 58127 (httpd), uid 65534: exited on signal 11
pid 58833 (httpd), uid 65534: exited on signal 11
pid 30556 (httpd), uid 65534: exited on signal 11
pid 35877 (httpd), uid 65534: exited on signal 11
pid 95642 (httpd), uid 65534: exited on signal 11



On Thu, 17 Mar 2005 10:35:15 -0800, Michael C. Shultz
<ringworm01 at gmail.com> wrote:
> On Thursday 17 March 2005 10:28 am, Kyle Mott wrote:
> > I've already sent this question to freebsd-questions; forgive me if
> > this is the wrong list.
> >
> > This just very recently started to happen (and I haven't upgraded
> > Apache as of late either, or any other software for that matter). I
> > keep getting this in my kernel.log on 2 different hosts:
> > Mar 17 09:34:16 logsrv pid 38069 (httpd), uid 0: exited on signal 11
> > (core dumped)
> > Mar 17 00:34:25 g1bs0n kernel: pid 9419 (httpd), uid 0: exited on
> > signal 11 (core dumped)
> >
> > Both hosts are running 'apache+mod_ssl-1.3.33+2.8.22' plus
> > 'php4-4.3.10', and a bunch of php modules that I don't want to list.
> > i was able to get Apache running on g1bs0n by not starting ssl;
> > however, Apache won't start on logsrv at all.
> >
> > Looking up man signal, SIGSEGV (11) is a segmentation violation. What
> > can cause this on 2 different machines that haven't been updated in a
> > while? I'm currently running a ports-cvsup, to verify that
> > apache+mod_ssl either does or does not need to be updated.
> >
> >
> >
> > -Kyle Mott
> 
> Just a suggestion....
> 
> Build Apache with debug support, do a back trace on the .core file with
> GDB.  That will let you narrow down the problem a bit. Then notify the
> ports maintainer.
> 


-- 
Vlad


More information about the freebsd-stable mailing list