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

Bug#529416: marked as done (apache2.2-common: Apache2 does not start with mod_ssl enabled)

Your message dated Tue, 19 May 2009 20:49:31 +0200
with message-id <200905192049.32179.sf@sfritsch.de>
and subject line Re: Bug#529416: Acknowledgement (apache2.2-common: Apache2 does not  start with mod_ssl enabled)
has caused the Debian Bug report #529416,
regarding apache2.2-common: Apache2 does not start with mod_ssl enabled
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

529416: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529416
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apache2.2-common
Version: 2.2.9-10+lenny2
Severity: normal

Suddenly (not after a change in configuration), apache2 fails to start when mod_ssl is enabled. Disabling mod_ssl makes apache2 start, but is not an option in my case.
I've done an strace with mod_ssl enabled to diagnose to problem but had no luck. It can be grabbed from

-- Package-specific info:
List of enabled modules from 'apache2 -M':
  alias auth_basic authn_file authz_default authz_groupfile
  authz_host authz_user autoindex cgi deflate dir env fcgid mime
  negotiation php5 rewrite setenvif status suexec

-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages apache2.2-common depends on:
ii  apache2-utils          2.2.9-10+lenny2   utility programs for webservers
ii  libapr1                1.2.12-5          The Apache Portable Runtime Librar
ii  libaprutil1            1.2.12+dfsg-8     The Apache Portable Runtime Utilit
ii  libc6                  2.7-18            GNU C Library: Shared libraries
ii  libmagic1              4.26-1            File type determination library us
ii  libssl0.9.8            0.9.8g-15+lenny1  SSL shared libraries
ii  lsb-base               3.2-20            Linux Standard Base 3.2 init scrip
ii  mime-support           3.44-1            MIME files 'mime.types' & 'mailcap
ii  net-tools              1.60-22           The NET-3 networking toolkit
ii  perl                   5.10.0-19         Larry Wall's Practical Extraction 
ii  procps                 1:3.2.7-11        /proc file system utilities
ii  zlib1g                 1: compression library - runtime

Versions of packages apache2.2-common recommends:
ii  ssl-cert                      1.0.23     simple debconf wrapper for OpenSSL

Versions of packages apache2.2-common suggests:
pn  apache2-doc              <none>          (no description available)
ii  apache2-suexec-custom [a 2.2.9-10+lenny2 Configurable suexec program for Ap
pn  www-browser              <none>          (no description available)

Versions of packages apache2.2-common is related to:
pn  apache2-mpm-event        <none>          (no description available)
pn  apache2-mpm-itk          <none>          (no description available)
ii  apache2-mpm-prefork      2.2.9-10+lenny2 Apache HTTP Server - traditional n
pn  apache2-mpm-worker       <none>          (no description available)

-- no debconf information

--- End Message ---
--- Begin Message ---
On Tuesday 19 May 2009, Florian Bender wrote:
> it turned out that this was some kind of misbehaviour of mod_ssl
> concerning wrong configuration with, however, correct syntax.
> In my case this was a file permission issue with the keyfile and a
> missing SSLCertificateKeyFile directive. I would consider this a
> bug, some Error message would be appreciated and apropriate here.

If something goes wrong during startup but after apache has 
daemonized, it is normal that the error message goes into the main 
server log and not to the console. This is not a bug and therefore I 
am closing this report. If there was no log message, please let us 
know. TIA.

--- End Message ---

Reply to: