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

Bug#820953: marked as done (problem with mpm_worker and ssl)

Your message dated Sat, 31 Mar 2018 14:55:38 +0200 (CEST)
with message-id <alpine.DEB.2.11.1803311455240.22988@manul.sfritsch.de>
and subject line Re: Bug#820953: apache2 in debian v8
has caused the Debian Bug report #820953,
regarding problem with mpm_worker and ssl
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.)


-- 
820953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820953
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apache2
Version: 2.4.10-10+deb8u4

I'd ask for the debian apache team to have a look at this one:
https://bz.apache.org/bugzilla/show_bug.cgi?id=53999

problem as described: mpm_worker has trouble with SSL while mpm_prefork is
fine, though prefork eats database-connections for breakfast.

thx
hk

Attachment: smime.p7s
Description: S/MIME cryptographic signature


--- End Message ---
--- Begin Message --- 
No response from submitter. Closing.

On Mon, 18 Apr 2016, Stefan Fritsch wrote:

> On Wednesday 13 April 2016 23:19:08, Harald Kapper wrote:
> > I'd ask for the debian apache team to have a look at this one:
> > https://bz.apache.org/bugzilla/show_bug.cgi?id=53999
> > 
> > problem as described: mpm_worker has trouble with SSL while
> > mpm_prefork is fine, though prefork eats database-connections for
> > breakfast.
> 
> Please try commenting out the "Mutex" line in 
> /etc/apache2/apache2.conf . This should result in pthread mutexes 
> being used instead of fcntl. The apache2.conf in 2.4.20-1 has been 
> changed in that way, and I would be interested if that fixes your 
> problem.
> 
> 
>

--- End Message ---
Reply to: