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

Bug#290458: marked as done (mod_ssl preventing apache2 from starting (segfault))

Your message dated Fri, 18 Apr 2008 20:22:18 +0100
with message-id <[🔎] 20080418192218.GA19748@steve.org.uk>
and subject line Re: mod_ssl preventing apache2 from starting (segfault)
has caused the Debian Bug report #290458,
regarding mod_ssl preventing apache2 from starting (segfault)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
290458: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=290458
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apache2
Version: 2.0.52-3
Severity: important


Apache2 ends with sigsegv or sigbus when starting with about 500
virtualhosts with ssl using mod_macro. It starts correctly when there is
no ssl vhosts at all, or when there are 2 or 3 vhosts using it.

In order to make it work with my 500 ssl vhosts, I made a configuration
with 2 ssl vhosts, start, alter configuration and add all ssl vhosts,
then restart (not stop start, restart). Thus the problem may be in the
code which differ between apache2ctl start and apache2ctl restart.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.28-grsec
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages apache2 depends on:
ii  apache2-mpm-prefork           2.0.52-3   Traditional model for Apache2

-- no debconf information

--- End Message ---
--- Begin Message --- 
  This bug was first reported over three years ago,
 and hasn't been confirmed.

  It seems likely that it no longer applies.  If you
 can still experience it then please reply to this
 mail and it will be re-opened.

Steve
-- 
Debian GNU/Linux System Administration
http://www.debian-administration.org/

--- End Message ---
Reply to: