Xenial has reached its end of standard support.
** Changed in: apache2 (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466926
Title:
reload
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466926
Title:
reload apache2 with mpm_event cause scoreboard is full
To manage notifications about this bug go to:
** Changed in: apache2 (Ubuntu Xenial)
Status: Fix Committed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466926
Title:
reload apache2 with mpm_event cause scoreboard is full
Note: removed from proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466926
Title:
reload apache2 with mpm_event cause scoreboard is full
To manage notifications about this bug go to:
Thanks a lot hloeung for trying in that environment.
This is exactly what we needed.
Too bad thou for the fix, the TL;DR now is:
- there is an issue if users/scripts reload apache too often (bad practice but
existing)
- we have backported the fix that is upstream and tested, but tests show that
We ran with the apache2 package from xenial-proposed on one of the main
Ubuntu Archive servers. It's quite high traffic and what we saw was that
there's quite a lot of processes being killed off (mixture of both
SIGTERM and SIGKILL).
Unfortunately, it was quite user noticeable and we've had to
Hello Branislav, or anyone else affected,
Accepted apache2 into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apache2/2.4.18-2ubuntu3.6 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
With the additional rationale and context I have accepted the apache2
upload into xenial-proposed. But since the change is rather big, please
be sure to do additional exploratory testing of the packages. I would
also request this to age in -proposed for slightly longer than just 7
days, if
We ran into this with the main Ubuntu Archive servers
(archive.ubuntu.com). They were only configured to reload/graceful on
log rotation. Basically workers were held up and eventually all full and
not servicing requests.
We've now switched from MPM event to worker but would like this
backported
On Tue, Mar 13, 2018 at 06:25:35AM -, ChristianEhrhardt wrote:
> Hi Łukasz,
> that is a fair set of questions, but I'm not a high profile webserver admin
> either to give you better answers.
>
> We have a few active bug reporters that are affected subscribed, maybe
> they can try to answer
Hi Łukasz,
that is a fair set of questions, but I'm not a high profile webserver admin
either to give you better answers.
We have a few active bug reporters that are affected subscribed, maybe
they can try to answer the SRU Teams (=Łukasz in this case) questions?
--
You received this bug
With my SRU hat on I am a bit reluctant about accepting this into
xenial. Don't get me wrong: I'm not saying no, but it's certainly
something I need to know a bit more about to make a proper decision.
The reported problem of course does seem like a bug, but my doubts come
from the complexity of
SRU Template prepared and uploaded for the SRU Teams consideration.
** Description changed:
+ [Impact]
+
+ * apache2 reload can fill up the scorecard with graceful reastarting
+workers to an amount that it is unable to serve more requests.
+
+ * Backport fix from upstream to avoid the
14.04 is too far away to be reasonable for the backport for now, If one wants
to try please feel free.
But Xenial is what was prepared and tested, so lets only go for that atm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Tobias for all the tests.
With all that prep done I'll try to push it to SRU review now.
** Changed in: apache2 (Ubuntu Trusty)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The PPA version has been running without a hitch for the last 19 days on
16.04 ... I'd say it works fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466926
Title:
reload apache2 with mpm_event
I have it running on our production server since this morning ... log
rotation will happen every day around 6:25 CET ... I will let you know
in a few days if the problem is gone ... I have not noticed any
regressions in normal operation.
--
You received this bug notification because you are a
Hi Tobias,
thanks for the update - it isn't 100% clear to me, does the ppa completely fix
the issue for you and also shows no other regression that you'd see?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
thanks for the test PPA ... I am running 2.4.18-2ubuntu3.6~ppa1 now on a
system that has been exhibiting the problem every few days ...
It is being triggered by logrotate restarting apache every day btw ...
/etc/logrotate.d/apache2
--
You received this bug notification because you are a member
To make it very clear that I have to rely on feedback of other affected
users in regard to the testcase and the ppa backport to test I'll mark
the X/T tasks incomplete.
** Changed in: apache2 (Ubuntu Xenial)
Status: Triaged => Incomplete
** Changed in: apache2 (Ubuntu Trusty)
First of all I beg your pardon, for this bug being dormant.
We started to clear this kind of bugs recently, but obviously one can't do all
in one day :-/
In this in particular I was made aware of by others being affected.
## CASE ##
For an SRU we need a reproducible case of some sorts.
On first
** Changed in: apache2 (Ubuntu Xenial)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466926
Title:
reload apache2 with mpm_event cause scoreboard is full
To
** Also affects: apache2 (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: apache2 (Ubuntu Zesty)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: apache2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apache2 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: apache2 (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: apache2 (Ubuntu Trusty)
Status:
Yes this is impacting on Xenial - when will this be backported to
currently supported LTS releases?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466926
Title:
reload apache2 with mpm_event cause
Will this be backported to Trusty or Xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466926
Title:
reload apache2 with mpm_event cause scoreboard is full
To manage notifications about
This bug was fixed in the package apache2 - 2.4.25-3ubuntu2
---
apache2 (2.4.25-3ubuntu2) zesty; urgency=medium
* Undrop (LP 1658469):
- Don't build experimental http2 module for LTS:
+ debian/control: removed libnghttp2-dev Build-Depends (in universe).
+
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466926
Title:
reload apache2 with mpm_event cause scoreboard is full
To manage notifications about this bug go to:
Thanks Steward to ping with the issue upstream now being resolved and a
patch available!
** Changed in: apache2 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: apache2 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of
A patch has now been committed to trunk for this bug:
https://bz.apache.org/bugzilla/show_bug.cgi?id=53555#c65
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466926
Title:
reload apache2 with
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apache2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466926
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apache2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
This bug has been discussed on the apache bug tracker :
https://bz.apache.org/bugzilla/show_bug.cgi?id=53555
There seems to be no movement to fix this that I can see. there is a
patch which seems to fix it for users up to a higher usage level.
This bug has been discussed on the apache bug tracker :
https://bz.apache.org/bugzilla/show_bug.cgi?id=53555
There seems to be no movement to fix this that I can see. there is a
patch which seems to fix it for users up to a higher usage level.
34 matches
Mail list logo
