You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Jim Jagielski <ji...@jaguNET.com> on 2017/09/25 12:13:39 UTC
[VOTE] Release Apache httpd 2.4.28 as GA
The pre-release test tarballs for Apache httpd
version 2.4.28 can be found at the usual place:
http://httpd.apache.org/dev/dist/
I'm calling a VOTE on releasing these as Apache httpd 2.4.28 GA.
[ ] +1: Good to go
[ ] +0: meh
[ ] -1: Danger Will Robinson. And why.
Vote will last the normal 72 hrs.
NOTE: The *-deps are only there for convenience.
Thx!
Re: [CLOSED] [VOTE] Release Apache httpd 2.4.28 as GA
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
Thanks.
Now forwarded to users@. Hopefully anyone on dev@ read your vote results
post.
On Oct 8, 2017 10:31, "Reindl Harald" <h....@thelounge.net> wrote:
>
>
> Am 08.10.2017 um 15:22 schrieb Jim Jagielski:
>
>> Hrm... looks like it was already announced? At least the
>> website sez it was, and it looks like an Email was
>> sent to announce@a.o but I'm not seeing anything on
>> the httpd lists
>>
>
> -------- Weitergeleitete Nachricht --------
> Betreff: [Announcement] Apache HTTP Server 2.4.28 Released
> Datum: Thu, 5 Oct 2017 13:49:10 -0500
> Von: William A Rowe Jr <wr...@apache.org>
> An: announce@httpd.apache.org
>
>
>
> Apache HTTP Server 2.4.28 Released
>
> October 5, 2017
>
> The Apache Software Foundation and the Apache HTTP Server Project
> are pleased to announce the release of version 2.4.28 of the Apache
> HTTP Server ("Apache"). This version of Apache is our latest GA
> release of the new generation 2.4.x branch of Apache HTTPD and
> represents fifteen years of innovation by the project, and is
> recommended over all previous releases. This release of Apache is
> a security, feature, and bug fix release.
>
>
Re: [CLOSED] [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Reindl Harald <h....@thelounge.net>.
Am 08.10.2017 um 15:22 schrieb Jim Jagielski:
> Hrm... looks like it was already announced? At least the
> website sez it was, and it looks like an Email was
> sent to announce@a.o but I'm not seeing anything on
> the httpd lists
-------- Weitergeleitete Nachricht --------
Betreff: [Announcement] Apache HTTP Server 2.4.28 Released
Datum: Thu, 5 Oct 2017 13:49:10 -0500
Von: William A Rowe Jr <wr...@apache.org>
An: announce@httpd.apache.org
Apache HTTP Server 2.4.28 Released
October 5, 2017
The Apache Software Foundation and the Apache HTTP Server Project
are pleased to announce the release of version 2.4.28 of the Apache
HTTP Server ("Apache"). This version of Apache is our latest GA
release of the new generation 2.4.x branch of Apache HTTPD and
represents fifteen years of innovation by the project, and is
recommended over all previous releases. This release of Apache is
a security, feature, and bug fix release.
Re: [CLOSED] [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Jim Jagielski <ji...@jaguNET.com>.
Hrm... looks like it was already announced? At least the
website sez it was, and it looks like an Email was
sent to announce@a.o but I'm not seeing anything on
the httpd lists.
Re: [CLOSED] [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Jim Jagielski <ji...@jaguNET.com>.
FYI: I'll be announcing tomorrow
Re: [CLOSED] [VOTE] Release Apache httpd 2.4.28 as GA
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
Sorry I ran out of cycles to jump on this on the 4th, and didn't see anyone
step up,
so I went ahead and still pushed it out a day late/day early this
afternoon. Hope you
had a worthwhile conference. Please help me double check any errors or
omissions,
I think it was already staged correctly.
You're welcome, for the bounce/"unsubscribe me" traffic save :) The noise
was
actually tolerable, I think our efforts to unsub unroutable accounts is
having some
impact. I just wish we got more feedback by default of whether this was the
@a.o
or @httpd.a.o traffic responses.
On Wed, Oct 4, 2017 at 7:41 AM, Jim Jagielski <ji...@jagunet.com> wrote:
> Sure. Anyone who wants to announce, please do so!! :)
>
> > On Oct 3, 2017, at 11:47 AM, William A Rowe Jr <wr...@rowe-clan.net>
> wrote:
> >
> > On Tue, Oct 3, 2017 at 6:46 AM, Jim Jagielski <ji...@jagunet.com> wrote:
> >> With more than the required 3 +1 (binding) votes, and no
> >> vetos, I call this vote CLOSED with the result that
> >> the vote passes.
> >>
> >> I will start moving the artifacts for mirror sync and
> >> let's plan on announcing on Friday.
> >
> > Uhm, why?
> >
> > I understand you are travelling for conference, so someone else might
> > need to step up to broadcast the messages. But it only takes 24 hours
> > for all mirrors to catch up... why ask the community to wait till Friday?
> > E.g. jchampion stepped in last time I had to be AFK so we could push
> > out an announcement, I'm certain someone will step up.
> >
> > Footnote - thank you for providing some extra time to hopefully identify
> > the mod_http2 load issues. Once identified and patched, and I'm happy
> > to tag 2.4.29 immediately, if you aren't available, so we can offer fewer
> > stress exceptions in this GA code.
>
>
Re: [CLOSED] [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Jim Jagielski <ji...@jaguNET.com>.
Sure. Anyone who wants to announce, please do so!! :)
> On Oct 3, 2017, at 11:47 AM, William A Rowe Jr <wr...@rowe-clan.net> wrote:
>
> On Tue, Oct 3, 2017 at 6:46 AM, Jim Jagielski <ji...@jagunet.com> wrote:
>> With more than the required 3 +1 (binding) votes, and no
>> vetos, I call this vote CLOSED with the result that
>> the vote passes.
>>
>> I will start moving the artifacts for mirror sync and
>> let's plan on announcing on Friday.
>
> Uhm, why?
>
> I understand you are travelling for conference, so someone else might
> need to step up to broadcast the messages. But it only takes 24 hours
> for all mirrors to catch up... why ask the community to wait till Friday?
> E.g. jchampion stepped in last time I had to be AFK so we could push
> out an announcement, I'm certain someone will step up.
>
> Footnote - thank you for providing some extra time to hopefully identify
> the mod_http2 load issues. Once identified and patched, and I'm happy
> to tag 2.4.29 immediately, if you aren't available, so we can offer fewer
> stress exceptions in this GA code.
Re: [CLOSED] Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
On Tue, Oct 3, 2017 at 6:46 AM, Jim Jagielski <ji...@jagunet.com> wrote:
> With more than the required 3 +1 (binding) votes, and no
> vetos, I call this vote CLOSED with the result that
> the vote passes.
>
> I will start moving the artifacts for mirror sync and
> let's plan on announcing on Friday.
Uhm, why?
I understand you are travelling for conference, so someone else might
need to step up to broadcast the messages. But it only takes 24 hours
for all mirrors to catch up... why ask the community to wait till Friday?
E.g. jchampion stepped in last time I had to be AFK so we could push
out an announcement, I'm certain someone will step up.
Footnote - thank you for providing some extra time to hopefully identify
the mod_http2 load issues. Once identified and patched, and I'm happy
to tag 2.4.29 immediately, if you aren't available, so we can offer fewer
stress exceptions in this GA code.
[CLOSED] Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Jim Jagielski <ji...@jaguNET.com>.
With more than the required 3 +1 (binding) votes, and no
vetos, I call this vote CLOSED with the result that
the vote passes.
I will start moving the artifacts for mirror sync and
let's plan on announcing on Friday.
> On Sep 25, 2017, at 8:13 AM, Jim Jagielski <ji...@jaguNET.com> wrote:
>
> The pre-release test tarballs for Apache httpd
> version 2.4.28 can be found at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.28 GA.
>
> [ ] +1: Good to go
> [ ] +0: meh
> [ ] -1: Danger Will Robinson. And why.
>
> Vote will last the normal 72 hrs.
>
> NOTE: The *-deps are only there for convenience.
>
> Thx!
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Yann Ylavic <yl...@gmail.com>.
On Mon, Sep 25, 2017 at 2:13 PM, Jim Jagielski <ji...@jagunet.com> wrote:
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.28 GA.
>
[X] +1: Good to go
Tested on Debian(s) 7.11, 8.9, 9.1 (with http2): all PASS.
Note: spurious warning in ap_parse_form_data(): "'escaped_char[0]' may
be used uninitialized in this function [-Wmaybe-uninitialized]" (needs
backport of r1798785 for 2.4.next to silence gcc).
Thanks Jim for RMing.
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by "Helmut K. C. Tessarek" <te...@evermeet.cx>.
On 2017-10-01 18:08, Rainer Jung wrote:
> Since I can only observe it with prefork in combination with http2 which
> is not a good combination in any way, I am not too concerned. Still it
> could be useful to understand whats going on.
How can this even be? http2 is automatically deactivated when mpm is
prefork. Stefan added this in 2.4.27.
There is no h2 with prefork anymore.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
Solaris prefork proxy failures (Was: [VOTE] Release Apache httpd
2.4.28 as GA)
Posted by Rainer Jung <ra...@kippdata.de>.
I observe sporadic failures in the proxy tests for 2.4.x.
They only happen on Solaris (Sparc) and only for prefork MPM. Although
they are not strictly reproducible, I think they only happen with APR
1.6 an with mod_http2/mod_proxy_http2 loaded (although they do not
happen during their test cases).
The failure pattern is, that one child process gets the request it
should (reverse) proxy. The process connects to the server to forward
the request and then hangs until the proxy timeout triggers. Then it
returns a proxy timeout but in addition once the timeout has been sent
to the client, the same process starts to work on the backend request.
Example excerpt from the error log:
[Sun Oct 01 14:22:56.980082 2017] [core:trace5] [pid 1310]
protocol.c(645): [client 127.0.0.1:44963] Request received from client:
GET /reverse/modules/cgi/nph-102.pl HTTP/1.1
...
[Sun Oct 01 14:22:56.981065 2017] [proxy:trace2] [pid 1310]
proxy_util.c(1962): [client 127.0.0.1:44963] http: found worker
http://localhost:8529/ for http://localhost:8529/modules/cgi/nph-102.pl
...
[Sun Oct 01 14:22:56.981552 2017] [proxy:debug] [pid 1310]
proxy_util.c(2887): AH02824: HTTP: connection established with
127.0.0.1:8529 (localhost)
[Sun Oct 01 14:22:56.982969 2017] [proxy:debug] [pid 1310]
proxy_util.c(3054): AH00962: HTTP: connection complete to 127.0.0.1:8529
(localhost)
[Sun Oct 01 14:22:56.983142 2017] [core:trace6] [pid 1310]
core_filters.c(525): [remote 127.0.0.1:8529] core_output_filter:
flushing because of FLUSH bucket
- here 60 seconds nothing happening or in the log -
[Sun Oct 01 14:23:56.983933 2017] [proxy_http:error] [pid 1310]
(70007)The timeout specified has expired: [client 127.0.0.1:44963]
AH01102: error reading status line from remote server localhost:8529
[Sun Oct 01 14:23:56.984150 2017] [proxy_http:debug] [pid 1310]
mod_proxy_http.c(1265): [client 127.0.0.1:44963] AH01103: read timeout
[Sun Oct 01 14:23:56.984178 2017] [proxy_http:debug] [pid 1310]
mod_proxy_http.c(1324): [client 127.0.0.1:44963] AH01105: NOT Closing
connection to client although reading from backend server localhost:8529
failed.
...
[Sun Oct 01 14:23:56.995756 2017] [http:trace3] [pid 1310]
http_filters.c(1128): [client 127.0.0.1:44963] Response sent with status
502, headers:
...
[Sun Oct 01 14:23:56.996158 2017] [core:trace6] [pid 1310]
core_filters.c(525): [client 127.0.0.1:44963] core_output_filter:
flushing because of FLUSH bucket
- and then suddenly (but too late) work on the original backend request
starts -
[Sun Oct 01 14:23:56.999866 2017] [core:trace5] [pid 1310]
protocol.c(645): [client 127.0.0.1:44966] Request received from client:
GET /modules/cgi/nph-102.pl HTTP/1.1
...
[Sun Oct 01 14:23:57.103062 2017] [core:trace6] [pid 1310]
core_filters.c(525): [client 127.0.0.1:44966] core_output_filter:
flushing because of FLUSH bucket
Note that during the time that the one child waits on the backend
response, the two other prefork child processes were hanging in
accept_mutex_on(), waiting for the lock. One also has to run bigger
parts of the test suite. Just running the proxy part does not suffice.
So it seems for some reason the proxy module can't effectively forward
the request to the idle children, instead it likely connects to the
kernel doing the accept and once the first child times out and tries to
acquire the accept mutex, it gets it and processes the old forwarded
request. The accept mutex used was pthread. It seems maybe the single
remaining child process that actually does work might not have unlocked
the accept mutex due to some race or error during an earlier test case.
Possible ingredients could be (speculation):
- APR 1.6 mutex changes and possible defaults changes
- HTTP2 additional mutex use somehow interfering on Solaris
- Accept handling changes
Since I can only observe it with prefork in combination with http2 which
is not a good combination in any way, I am not too concerned. Still it
could be useful to understand whats going on.
I will try to look further, but I am not too optimistic to get to the
bottom of this.
Regards,
Rainer
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Rainer Jung <ra...@kippdata.de>.
An update concerning the sporadic proxy test failures for prefork on
Solaris that I observed:
These are a bit difficult to nail down, because running only the proxy
tests does not fail. One has to run a relatively big part of the test
suite to have a chance of triggering the problem during the proxy test.
I can reproduce in about 50% of the test runs.
Currently I have the impression, that the problem only happens with apr
1.6.x (in about 50% of the test runs), but never with apr 1.5.x. Whether
I use apu 1.5.x or apu 1.6.x does not seem to matter.
So I need to dig deeper, what behavioral changes are expected between
apr 1.5.x and 1.6.x especially on Solaris (and which only matter for
prefork).
Still IMHO not a show-stopper but of course worth fixing.
Regards,
Rainer
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Rainer Jung <ra...@kippdata.de>.
Am 25.09.2017 um 14:13 schrieb Jim Jagielski:
> The pre-release test tarballs for Apache httpd
> version 2.4.28 can be found at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.28 GA.
>
> [X] +1: Good to go
> [ ] +0: meh
> [ ] -1: Danger Will Robinson. And why.
>
> Vote will last the normal 72 hrs.
>
> NOTE: The *-deps are only there for convenience.
+1 to release and thanks a bunch for RMing and to all who contributed to
the release.
In short: No regressions found.
Detailed report:
- Sigs and hashes OK
- contents of tarballs identical
- contents of tag and tarballs identical
except for expected deltas
Built on
- Solaris 10 Sparc as 32 Bit Binaries
- SLES 11+12 (64 Bits)
- RHEL 6+7 (64 Bits)
For all platforms built
- with default (shared), shared and static modules
- with module sets none, few, most, all, reallyall and default
(always mod_privileges disabled)
- using --enable-load-all-modules
- against "included" APR/APU from deps tarball,
plus external APR/APU 1.6.2/1.6.0, 1.5.2/1.5.4,
1.6.x branches head and trunk head.
- using external libraries
- expat 2.2.4
- pcre 8.41
- openssl 1.0.2k plus patches
- lua 5.3.4 (compiled with LUA_COMPAT_MODULE)
- distcache 1.5.1
- libxml2 2.9.5
- libnghttp2 1.26.0
- brotli 1.0.1
- Tool chain:
- platform gcc except on Solaris
(gcc 4.1.2 for Solaris 8 and 7.1.0 Solaris 10 (only older APR/APU
1.5.x compiled with older gcc 4.9.2)
- CFLAGS: -O2 -g -Wall -fno-strict-aliasing
- on Solaris additionally -mpcu=v9, -D_XOPEN_SOURCE,
-D_XOPEN_SOURCE_EXTENDED=1 and -D__EXTENSIONS__
plus -D_XPG6 when using gcc 7.1.0
350 build succeeded, 2 builds both on SLES 11 crashed due to
segmentation faults in ksh during make, but could be completed by
restarting make. Not a regression.
- compiler warnings:
- modules/core/mod_watchdog.c:436: warning: 'rv' may be used
uninitialized in this function
-> warning is correct but nt critical (debug log), will fix this soon;
not a regression
and only on Solaris (gcc 7.1.0)
- server/util.c:2667:10: warning: 'escaped_char[0]' may be used
uninitialized in this function [-Wmaybe-uninitialized]
- srclib/apr-util/xlate/xlate.c:120:38: warning: passing argument 2 of
'iconv' from incompatible pointer type
[-Wincompatible-pointer-types]
- srclib/apr-util/xlate/xlate.c:343:42: warning: passing argument 2 of
'iconv' from incompatible pointer type
[-Wincompatible-pointer-types]
Tested for
- Solaris 10, SLES 11+12, RHEL 6+7
- MPMs prefork, worker, event
- default, shared and static modules
- log level trace8
- module set reallyall (125 modules plus MPMs)
The following test failures were seen:
a Lots of tests in t/module/session.t fail always for static builds
The whole setup for the /sesiontest uri is missing in the generated
t/conf/httpd.conf. This is due to it missing from the also generated
filet/conf/apache_test_config.pm. I do not know yet, why it is missing
there, but this seems to be a test framework problem.
Not a regression.
b Test 5 in t/modules/dav.t:
Happens for 7 out of about 225 runs
Creation, modified and now times not in the correct order.
This seems to be a system issue, all tests done on NFS,
many tested on virtualized guests.
Not a regression.
c Test 59 of t/modules/include.t only and always on
Solaris.
This is due to a bug in the test, which uses strftime()
with a "%s" pattern that is not supported on Solaris.
Until recently the server and the test client both returned
verbatim "%s" and the test succeeded. After updating some
Perl modules for the http2 tests, the perl client even
on Solaris now supports "%s" in strftime and the test starts
to fail. It seems we have to fix the test.
Not a regression
d Various tests in t/apache/expr_string.t: (3, 6, 11, 14, 17, 20 ,23)
Happens for 8 out of about 225 runs (this time all on RHEL6).
The failure is always on line 68, where the error_log contents
are checked.
Not a regression.
e Only on Solaris and only with prefork proxy tests sometimes
seem to hang until timeout. Some test runs complete without
the issue. Once the issue hits, all remaining proxy tests during
that run face that issue.
Not observed for static builds. Of the 8 non-static builds using
APR/APU 1.6 or trunk, 5 had the problem. The two APR/APU builds did
not have it. First observed when testing 2.4.26.
I'll try to investigate further, but IMHO this is not a show-stopper.
All in all I don't see a critical problem.
Regards,
Rainer
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Stefan Eissing <st...@greenbytes.de>.
> Am 02.10.2017 um 19:53 schrieb William A Rowe Jr <wr...@rowe-clan.net>:
>
> On Thu, Sep 28, 2017 at 7:44 AM, Stefan Eissing
> <st...@greenbytes.de> wrote:
>> Update: disregard the man behind the curtain - for now.
>>
>> I have the strangest effects on my main machine under native macOS 10.12.6, which
>> do not happen on my parallels ubuntu image and my laptop with macOS 10.13.0. I tested
>> with hyperthreading disabled to exclude the Intel *lake bugs, but it made no difference.
>>
>> I will upgrade the machine over night to macOS 10.13.0 and check again tomorrow if
>> that had any effect.
>
> Interesting. Any further word on this, or more comments that we might
> help brainstorm?
With the fix that has also been accepted for backporting, I do not see these assertion failures any longer. There was a race with an unlock of a free mutex that triggered a pthread assertion.
BUT: I still see one *one* machine, may recent iMac, that a signal for graceful restart triggers *something* in the process to spawn new threads endlessly until it exhausts system limits and dies. That is happening on this one machine on MacOS 10.12.6 and also 10.13.0. I suspect this is some 3rd party/os library linked. I checked that it is not a http2 related thread. Need to check for MPMs. I do not believe this to be hardware related since it did not happen at all for months before.
I do not see it on my laptop for the same OS versions. I strongly suspect some mess-up of my machine now.
Cheers,
Stefan
>
>> Regardless of all this, I managed to find an edge case assertion fail and made a fix
>> on trunk. If we go for 2.4.29, I'll propose that for inclusion. It is not a regression to
>> 2.4.27, so no veto from me on 2.4.28.
>
> Thanks for that find and backport. I was wondering if this was related
> to the report.
>
> Which machines / os do you observe the load test asserts on?
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
On Thu, Sep 28, 2017 at 7:44 AM, Stefan Eissing
<st...@greenbytes.de> wrote:
> Update: disregard the man behind the curtain - for now.
>
> I have the strangest effects on my main machine under native macOS 10.12.6, which
> do not happen on my parallels ubuntu image and my laptop with macOS 10.13.0. I tested
> with hyperthreading disabled to exclude the Intel *lake bugs, but it made no difference.
>
> I will upgrade the machine over night to macOS 10.13.0 and check again tomorrow if
> that had any effect.
Interesting. Any further word on this, or more comments that we might
help brainstorm?
> Regardless of all this, I managed to find an edge case assertion fail and made a fix
> on trunk. If we go for 2.4.29, I'll propose that for inclusion. It is not a regression to
> 2.4.27, so no veto from me on 2.4.28.
Thanks for that find and backport. I was wondering if this was related
to the report.
Which machines / os do you observe the load test asserts on?
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Stefan Eissing <st...@greenbytes.de>.
Update: disregard the man behind the curtain - for now.
I have the strangest effects on my main machine under native macOS 10.12.6, which
do not happen on my parallels ubuntu image and my laptop with macOS 10.13.0. I tested
with hyperthreading disabled to exclude the Intel *lake bugs, but it made no difference.
I will upgrade the machine over night to macOS 10.13.0 and check again tomorrow if
that had any effect.
Regardless of all this, I managed to find an edge case assertion fail and made a fix
on trunk. If we go for 2.4.29, I'll propose that for inclusion. It is not a regression to
2.4.27, so no veto from me on 2.4.28.
Cheers,
Stefan
> Am 28.09.2017 um 09:54 schrieb Stefan Eissing <st...@greenbytes.de>:
>
> Analyzing...
>
> my checkout of branch/2.4.x does not show this.
> my buildt of 2.4.28 with -deps as provided, does after while of letting:
>
> while true; do h2load -t 8 -c 100 -n 10000 -m 5 -d gen/data-10k http://test.example.org:12345/; done
>
> run (data-10k is a 10k text file). The whole server setup is according to the mod_http2 test cases
> in https://svn.apache.org/repos/asf/httpd/test/mod_h2/trunk
>
> In 2.4.28 I have apr 1.6.2 and in my branch/2.4.x is a 1.5.x (which shows 1.5.3 in its header).
>
> Will check if that is connected or not. Will also check if this happens for me on my Ubuntu.
>
> Sporadically (less frequent), I can also see (not both 2.4.x and 2.4.28):
> Thread 3 Crashed:
> 0 libsystem_kernel.dylib 0x00007fffd3c34d42 __pthread_kill + 10
> 1 libsystem_pthread.dylib 0x00007fffd3d22457 pthread_kill + 90
> 2 libsystem_c.dylib 0x00007fffd3b9a4bb __abort + 140
> 3 libsystem_c.dylib 0x00007fffd3b9a42f abort + 144
> 4 libsystem_pthread.dylib 0x00007fffd3d23bc7 __pthread_abort + 49
> 5 libsystem_pthread.dylib 0x00007fffd3d23c7b __pthread_abort_reason + 180
> 6 libsystem_pthread.dylib 0x00007fffd3d1fd93 _pthread_mutex_unlock_drop + 167
> 7 mod_http2.so 0x000000010cb42b2b h2_beam_send + 1819 (h2_bucket_beam.c:965)
> 8 mod_http2.so 0x000000010cb59d31 send_out + 257 (h2_task.c:100)
> 9 mod_http2.so 0x000000010cb59146 h2_filter_slave_output + 294 (h2_task.c:176)
> 10 httpd 0x000000010c598829 ap_process_request_after_handler + 89 (http_request.c:366)
> 11 httpd 0x000000010c598ab6 ap_process_request + 22 (http_request.c:473)
> 12 mod_http2.so 0x000000010cb5874e h2_task_process_conn + 398 (h2_task.c:682)
> 13 httpd 0x000000010c5705f7 ap_run_process_connection + 55 (connection.c:42)
> 14 mod_http2.so 0x000000010cb599db h2_task_do + 539 (h2_task.c:640)
> 15 mod_http2.so 0x000000010cb5df24 slot_run + 260 (h2_workers.c:233)
> 16 libsystem_pthread.dylib 0x00007fffd3d1f93b _pthread_body + 180
> 17 libsystem_pthread.dylib 0x00007fffd3d1f887 _pthread_start + 286
> 18 libsystem_pthread.dylib 0x00007fffd3d1f08d thread_start + 13
>
> which is a call to apr_thread_mutex_unlock(). Without having checkinto pthread version, the closest
> similar report I could find on the net is https://sourceware.org/bugzilla/show_bug.cgi?id=17514
>
> Will report when I know more.
>
> -Stefan
>
>> Am 27.09.2017 um 18:04 schrieb Luca Toscano <to...@gmail.com>:
>>
>> Hi Stefan,
>>
>> 2017-09-27 17:32 GMT+02:00 Stefan Eissing <st...@greenbytes.de>:
>> On my h2 load tests, the server sometimes crashes in an assertion failure (build in maintainer mode):
>>
>> How did you make the tests? It would be good for people to attempt to reproduce..
>>
>>
>> macOS crash reporter:
>> Thread 54 Crashed:
>> 0 libsystem_kernel.dylib 0x00007fffd3c34d42 __pthread_kill + 10
>> 1 libsystem_pthread.dylib 0x00007fffd3d22457 pthread_kill + 90
>> 2 libsystem_c.dylib 0x00007fffd3b9a4bb __abort + 140
>> 3 libsystem_c.dylib 0x00007fffd3b9a42f abort + 144
>> 4 httpd 0x000000010be99282 ap_log_assert + 130 (log.c:1696)
>> 5 mod_mpm_event.so 0x000000010c50b51c ap_queue_push + 188
>> 6 mod_mpm_event.so 0x000000010c509be2 listener_thread + 2226 (event.c:1749)
>> 7 libsystem_pthread.dylib 0x00007fffd3d1f93b _pthread_body + 180
>> 8 libsystem_pthread.dylib 0x00007fffd3d1f887 _pthread_start + 286
>> 9 libsystem_pthread.dylib 0x00007fffd3d1f08d thread_start + 13
>>
>> error_log:
>> [Wed Sep 27 17:27:09.941040 2017] [mpm_event:notice] [pid 23404:tid 140736895005632] AH00489: Apache/2.4.28 (Unix) OpenSSL/1.1.0e configured -- resuming normal operations
>> [Wed Sep 27 17:27:09.941055 2017] [core:notice] [pid 23404:tid 140736895005632] AH00094: Command line: '/opt/apache-2.4.x/bin/httpd -d /Users/sei/projects/httpd/test/mod_h2/2.4.x/gen/apache'
>> [Wed Sep 27 17:29:43.207923 2017] [mpm_event:alert] [pid 30381:tid 123145361334272] (35)Resource temporarily unavailable: AH03104: apr_thread_create: unable to create worker thread
>> [Wed Sep 27 17:29:43.208904 2017] [mpm_event:crit] [pid 30381:tid 123145369382912] (9)Bad file descriptor: apr_pollset_poll failed. Attempting to shutdown process gracefully
>> [Wed Sep 27 17:29:44.000147 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 30381 exit signal Segmentation fault (11)
>> [Wed Sep 27 17:29:44.208035 2017] [mpm_event:alert] [pid 30382:tid 123145438388224] (35)Resource temporarily unavailable: AH03104: apr_thread_create: unable to create worker thread
>> [Wed Sep 27 17:29:44.208925 2017] [mpm_event:crit] [pid 30382:tid 123145446436864] (9)Bad file descriptor: apr_pollset_poll failed. Attempting to shutdown process gracefully
>> [Wed Sep 27 17:29:45.001702 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 30382 exit signal Segmentation fault (11)
>> [Wed Sep 27 17:29:48.881247 2017] [core:crit] [pid 32841:tid 123145544712192] AH00102: [Wed Sep 27 17:29:48 2017] file fdqueue.c, line 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
>> [Wed Sep 27 17:29:50.004871 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 32841 exit signal Abort trap (6)
>> [Wed Sep 27 17:29:52.366672 2017] [core:crit] [pid 35505:tid 123145420349440] AH00102: [Wed Sep 27 17:29:52 2017] file fdqueue.c, line 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
>> [Wed Sep 27 17:29:52.368902 2017] [core:crit] [pid 35488:tid 123145392611328] AH00102: [Wed Sep 27 17:29:52 2017] file fdqueue.c, line 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
>> [Wed Sep 27 17:29:53.007664 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 35505 exit signal Abort trap (6)
>> [Wed Sep 27 17:29:53.007741 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 35488 exit signal Abort trap (6)
>>
>>
>> Any relevant stacktrace or lead about where the problem might reside?
>>
>> Luca
>
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Stefan Eissing <st...@greenbytes.de>.
Analyzing...
my checkout of branch/2.4.x does not show this.
my buildt of 2.4.28 with -deps as provided, does after while of letting:
while true; do h2load -t 8 -c 100 -n 10000 -m 5 -d gen/data-10k http://test.example.org:12345/; done
run (data-10k is a 10k text file). The whole server setup is according to the mod_http2 test cases
in https://svn.apache.org/repos/asf/httpd/test/mod_h2/trunk
In 2.4.28 I have apr 1.6.2 and in my branch/2.4.x is a 1.5.x (which shows 1.5.3 in its header).
Will check if that is connected or not. Will also check if this happens for me on my Ubuntu.
Sporadically (less frequent), I can also see (not both 2.4.x and 2.4.28):
Thread 3 Crashed:
0 libsystem_kernel.dylib 0x00007fffd3c34d42 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fffd3d22457 pthread_kill + 90
2 libsystem_c.dylib 0x00007fffd3b9a4bb __abort + 140
3 libsystem_c.dylib 0x00007fffd3b9a42f abort + 144
4 libsystem_pthread.dylib 0x00007fffd3d23bc7 __pthread_abort + 49
5 libsystem_pthread.dylib 0x00007fffd3d23c7b __pthread_abort_reason + 180
6 libsystem_pthread.dylib 0x00007fffd3d1fd93 _pthread_mutex_unlock_drop + 167
7 mod_http2.so 0x000000010cb42b2b h2_beam_send + 1819 (h2_bucket_beam.c:965)
8 mod_http2.so 0x000000010cb59d31 send_out + 257 (h2_task.c:100)
9 mod_http2.so 0x000000010cb59146 h2_filter_slave_output + 294 (h2_task.c:176)
10 httpd 0x000000010c598829 ap_process_request_after_handler + 89 (http_request.c:366)
11 httpd 0x000000010c598ab6 ap_process_request + 22 (http_request.c:473)
12 mod_http2.so 0x000000010cb5874e h2_task_process_conn + 398 (h2_task.c:682)
13 httpd 0x000000010c5705f7 ap_run_process_connection + 55 (connection.c:42)
14 mod_http2.so 0x000000010cb599db h2_task_do + 539 (h2_task.c:640)
15 mod_http2.so 0x000000010cb5df24 slot_run + 260 (h2_workers.c:233)
16 libsystem_pthread.dylib 0x00007fffd3d1f93b _pthread_body + 180
17 libsystem_pthread.dylib 0x00007fffd3d1f887 _pthread_start + 286
18 libsystem_pthread.dylib 0x00007fffd3d1f08d thread_start + 13
which is a call to apr_thread_mutex_unlock(). Without having checkinto pthread version, the closest
similar report I could find on the net is https://sourceware.org/bugzilla/show_bug.cgi?id=17514
Will report when I know more.
-Stefan
> Am 27.09.2017 um 18:04 schrieb Luca Toscano <to...@gmail.com>:
>
> Hi Stefan,
>
> 2017-09-27 17:32 GMT+02:00 Stefan Eissing <st...@greenbytes.de>:
> On my h2 load tests, the server sometimes crashes in an assertion failure (build in maintainer mode):
>
> How did you make the tests? It would be good for people to attempt to reproduce..
>
>
> macOS crash reporter:
> Thread 54 Crashed:
> 0 libsystem_kernel.dylib 0x00007fffd3c34d42 __pthread_kill + 10
> 1 libsystem_pthread.dylib 0x00007fffd3d22457 pthread_kill + 90
> 2 libsystem_c.dylib 0x00007fffd3b9a4bb __abort + 140
> 3 libsystem_c.dylib 0x00007fffd3b9a42f abort + 144
> 4 httpd 0x000000010be99282 ap_log_assert + 130 (log.c:1696)
> 5 mod_mpm_event.so 0x000000010c50b51c ap_queue_push + 188
> 6 mod_mpm_event.so 0x000000010c509be2 listener_thread + 2226 (event.c:1749)
> 7 libsystem_pthread.dylib 0x00007fffd3d1f93b _pthread_body + 180
> 8 libsystem_pthread.dylib 0x00007fffd3d1f887 _pthread_start + 286
> 9 libsystem_pthread.dylib 0x00007fffd3d1f08d thread_start + 13
>
> error_log:
> [Wed Sep 27 17:27:09.941040 2017] [mpm_event:notice] [pid 23404:tid 140736895005632] AH00489: Apache/2.4.28 (Unix) OpenSSL/1.1.0e configured -- resuming normal operations
> [Wed Sep 27 17:27:09.941055 2017] [core:notice] [pid 23404:tid 140736895005632] AH00094: Command line: '/opt/apache-2.4.x/bin/httpd -d /Users/sei/projects/httpd/test/mod_h2/2.4.x/gen/apache'
> [Wed Sep 27 17:29:43.207923 2017] [mpm_event:alert] [pid 30381:tid 123145361334272] (35)Resource temporarily unavailable: AH03104: apr_thread_create: unable to create worker thread
> [Wed Sep 27 17:29:43.208904 2017] [mpm_event:crit] [pid 30381:tid 123145369382912] (9)Bad file descriptor: apr_pollset_poll failed. Attempting to shutdown process gracefully
> [Wed Sep 27 17:29:44.000147 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 30381 exit signal Segmentation fault (11)
> [Wed Sep 27 17:29:44.208035 2017] [mpm_event:alert] [pid 30382:tid 123145438388224] (35)Resource temporarily unavailable: AH03104: apr_thread_create: unable to create worker thread
> [Wed Sep 27 17:29:44.208925 2017] [mpm_event:crit] [pid 30382:tid 123145446436864] (9)Bad file descriptor: apr_pollset_poll failed. Attempting to shutdown process gracefully
> [Wed Sep 27 17:29:45.001702 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 30382 exit signal Segmentation fault (11)
> [Wed Sep 27 17:29:48.881247 2017] [core:crit] [pid 32841:tid 123145544712192] AH00102: [Wed Sep 27 17:29:48 2017] file fdqueue.c, line 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
> [Wed Sep 27 17:29:50.004871 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 32841 exit signal Abort trap (6)
> [Wed Sep 27 17:29:52.366672 2017] [core:crit] [pid 35505:tid 123145420349440] AH00102: [Wed Sep 27 17:29:52 2017] file fdqueue.c, line 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
> [Wed Sep 27 17:29:52.368902 2017] [core:crit] [pid 35488:tid 123145392611328] AH00102: [Wed Sep 27 17:29:52 2017] file fdqueue.c, line 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
> [Wed Sep 27 17:29:53.007664 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 35505 exit signal Abort trap (6)
> [Wed Sep 27 17:29:53.007741 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 35488 exit signal Abort trap (6)
>
>
> Any relevant stacktrace or lead about where the problem might reside?
>
> Luca
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Jim Jagielski <ji...@jaguNET.com>.
fdqueue.c, line 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
> On Sep 27, 2017, at 11:04 AM, Luca Toscano <to...@gmail.com> wrote:
>
> Hi Stefan,
>
> 2017-09-27 17:32 GMT+02:00 Stefan Eissing <st...@greenbytes.de>:
> On my h2 load tests, the server sometimes crashes in an assertion failure (build in maintainer mode):
>
> How did you make the tests? It would be good for people to attempt to reproduce..
>
>
> macOS crash reporter:
> Thread 54 Crashed:
> 0 libsystem_kernel.dylib 0x00007fffd3c34d42 __pthread_kill + 10
> 1 libsystem_pthread.dylib 0x00007fffd3d22457 pthread_kill + 90
> 2 libsystem_c.dylib 0x00007fffd3b9a4bb __abort + 140
> 3 libsystem_c.dylib 0x00007fffd3b9a42f abort + 144
> 4 httpd 0x000000010be99282 ap_log_assert + 130 (log.c:1696)
> 5 mod_mpm_event.so 0x000000010c50b51c ap_queue_push + 188
> 6 mod_mpm_event.so 0x000000010c509be2 listener_thread + 2226 (event.c:1749)
> 7 libsystem_pthread.dylib 0x00007fffd3d1f93b _pthread_body + 180
> 8 libsystem_pthread.dylib 0x00007fffd3d1f887 _pthread_start + 286
> 9 libsystem_pthread.dylib 0x00007fffd3d1f08d thread_start + 13
>
> error_log:
> [Wed Sep 27 17:27:09.941040 2017] [mpm_event:notice] [pid 23404:tid 140736895005632] AH00489: Apache/2.4.28 (Unix) OpenSSL/1.1.0e configured -- resuming normal operations
> [Wed Sep 27 17:27:09.941055 2017] [core:notice] [pid 23404:tid 140736895005632] AH00094: Command line: '/opt/apache-2.4.x/bin/httpd -d /Users/sei/projects/httpd/test/mod_h2/2.4.x/gen/apache'
> [Wed Sep 27 17:29:43.207923 2017] [mpm_event:alert] [pid 30381:tid 123145361334272] (35)Resource temporarily unavailable: AH03104: apr_thread_create: unable to create worker thread
> [Wed Sep 27 17:29:43.208904 2017] [mpm_event:crit] [pid 30381:tid 123145369382912] (9)Bad file descriptor: apr_pollset_poll failed. Attempting to shutdown process gracefully
> [Wed Sep 27 17:29:44.000147 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 30381 exit signal Segmentation fault (11)
> [Wed Sep 27 17:29:44.208035 2017] [mpm_event:alert] [pid 30382:tid 123145438388224] (35)Resource temporarily unavailable: AH03104: apr_thread_create: unable to create worker thread
> [Wed Sep 27 17:29:44.208925 2017] [mpm_event:crit] [pid 30382:tid 123145446436864] (9)Bad file descriptor: apr_pollset_poll failed. Attempting to shutdown process gracefully
> [Wed Sep 27 17:29:45.001702 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 30382 exit signal Segmentation fault (11)
> [Wed Sep 27 17:29:48.881247 2017] [core:crit] [pid 32841:tid 123145544712192] AH00102: [Wed Sep 27 17:29:48 2017] file fdqueue.c, line 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
> [Wed Sep 27 17:29:50.004871 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 32841 exit signal Abort trap (6)
> [Wed Sep 27 17:29:52.366672 2017] [core:crit] [pid 35505:tid 123145420349440] AH00102: [Wed Sep 27 17:29:52 2017] file fdqueue.c, line 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
> [Wed Sep 27 17:29:52.368902 2017] [core:crit] [pid 35488:tid 123145392611328] AH00102: [Wed Sep 27 17:29:52 2017] file fdqueue.c, line 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
> [Wed Sep 27 17:29:53.007664 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 35505 exit signal Abort trap (6)
> [Wed Sep 27 17:29:53.007741 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 35488 exit signal Abort trap (6)
>
>
> Any relevant stacktrace or lead about where the problem might reside?
>
> Luca
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Luca Toscano <to...@gmail.com>.
Hi Stefan,
2017-09-27 17:32 GMT+02:00 Stefan Eissing <st...@greenbytes.de>:
> On my h2 load tests, the server sometimes crashes in an assertion failure
> (build in maintainer mode):
>
How did you make the tests? It would be good for people to attempt to
reproduce..
>
> macOS crash reporter:
> Thread 54 Crashed:
> 0 libsystem_kernel.dylib 0x00007fffd3c34d42 __pthread_kill
> + 10
> 1 libsystem_pthread.dylib 0x00007fffd3d22457 pthread_kill +
> 90
> 2 libsystem_c.dylib 0x00007fffd3b9a4bb __abort + 140
> 3 libsystem_c.dylib 0x00007fffd3b9a42f abort + 144
> 4 httpd 0x000000010be99282 ap_log_assert +
> 130 (log.c:1696)
> 5 mod_mpm_event.so 0x000000010c50b51c ap_queue_push +
> 188
> 6 mod_mpm_event.so 0x000000010c509be2 listener_thread
> + 2226 (event.c:1749)
> 7 libsystem_pthread.dylib 0x00007fffd3d1f93b _pthread_body +
> 180
> 8 libsystem_pthread.dylib 0x00007fffd3d1f887 _pthread_start
> + 286
> 9 libsystem_pthread.dylib 0x00007fffd3d1f08d thread_start +
> 13
>
> error_log:
> [Wed Sep 27 17:27:09.941040 2017] [mpm_event:notice] [pid 23404:tid
> 140736895005632] AH00489: Apache/2.4.28 (Unix) OpenSSL/1.1.0e configured --
> resuming normal operations
> [Wed Sep 27 17:27:09.941055 2017] [core:notice] [pid 23404:tid
> 140736895005632] AH00094: Command line: '/opt/apache-2.4.x/bin/httpd -d
> /Users/sei/projects/httpd/test/mod_h2/2.4.x/gen/apache'
> [Wed Sep 27 17:29:43.207923 2017] [mpm_event:alert] [pid 30381:tid
> 123145361334272] (35)Resource temporarily unavailable: AH03104:
> apr_thread_create: unable to create worker thread
> [Wed Sep 27 17:29:43.208904 2017] [mpm_event:crit] [pid 30381:tid
> 123145369382912] (9)Bad file descriptor: apr_pollset_poll failed.
> Attempting to shutdown process gracefully
> [Wed Sep 27 17:29:44.000147 2017] [core:notice] [pid 23404:tid
> 140736895005632] AH00052: child pid 30381 exit signal Segmentation fault
> (11)
> [Wed Sep 27 17:29:44.208035 2017] [mpm_event:alert] [pid 30382:tid
> 123145438388224] (35)Resource temporarily unavailable: AH03104:
> apr_thread_create: unable to create worker thread
> [Wed Sep 27 17:29:44.208925 2017] [mpm_event:crit] [pid 30382:tid
> 123145446436864] (9)Bad file descriptor: apr_pollset_poll failed.
> Attempting to shutdown process gracefully
> [Wed Sep 27 17:29:45.001702 2017] [core:notice] [pid 23404:tid
> 140736895005632] AH00052: child pid 30382 exit signal Segmentation fault
> (11)
> [Wed Sep 27 17:29:48.881247 2017] [core:crit] [pid 32841:tid
> 123145544712192] AH00102: [Wed Sep 27 17:29:48 2017] file fdqueue.c, line
> 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
> [Wed Sep 27 17:29:50.004871 2017] [core:notice] [pid 23404:tid
> 140736895005632] AH00052: child pid 32841 exit signal Abort trap (6)
> [Wed Sep 27 17:29:52.366672 2017] [core:crit] [pid 35505:tid
> 123145420349440] AH00102: [Wed Sep 27 17:29:52 2017] file fdqueue.c, line
> 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
> [Wed Sep 27 17:29:52.368902 2017] [core:crit] [pid 35488:tid
> 123145392611328] AH00102: [Wed Sep 27 17:29:52 2017] file fdqueue.c, line
> 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
> [Wed Sep 27 17:29:53.007664 2017] [core:notice] [pid 23404:tid
> 140736895005632] AH00052: child pid 35505 exit signal Abort trap (6)
> [Wed Sep 27 17:29:53.007741 2017] [core:notice] [pid 23404:tid
> 140736895005632] AH00052: child pid 35488 exit signal Abort trap (6)
>
>
Any relevant stacktrace or lead about where the problem might reside?
Luca
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Stefan Eissing <st...@greenbytes.de>.
On my h2 load tests, the server sometimes crashes in an assertion failure (build in maintainer mode):
macOS crash reporter:
Thread 54 Crashed:
0 libsystem_kernel.dylib 0x00007fffd3c34d42 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fffd3d22457 pthread_kill + 90
2 libsystem_c.dylib 0x00007fffd3b9a4bb __abort + 140
3 libsystem_c.dylib 0x00007fffd3b9a42f abort + 144
4 httpd 0x000000010be99282 ap_log_assert + 130 (log.c:1696)
5 mod_mpm_event.so 0x000000010c50b51c ap_queue_push + 188
6 mod_mpm_event.so 0x000000010c509be2 listener_thread + 2226 (event.c:1749)
7 libsystem_pthread.dylib 0x00007fffd3d1f93b _pthread_body + 180
8 libsystem_pthread.dylib 0x00007fffd3d1f887 _pthread_start + 286
9 libsystem_pthread.dylib 0x00007fffd3d1f08d thread_start + 13
error_log:
[Wed Sep 27 17:27:09.941040 2017] [mpm_event:notice] [pid 23404:tid 140736895005632] AH00489: Apache/2.4.28 (Unix) OpenSSL/1.1.0e configured -- resuming normal operations
[Wed Sep 27 17:27:09.941055 2017] [core:notice] [pid 23404:tid 140736895005632] AH00094: Command line: '/opt/apache-2.4.x/bin/httpd -d /Users/sei/projects/httpd/test/mod_h2/2.4.x/gen/apache'
[Wed Sep 27 17:29:43.207923 2017] [mpm_event:alert] [pid 30381:tid 123145361334272] (35)Resource temporarily unavailable: AH03104: apr_thread_create: unable to create worker thread
[Wed Sep 27 17:29:43.208904 2017] [mpm_event:crit] [pid 30381:tid 123145369382912] (9)Bad file descriptor: apr_pollset_poll failed. Attempting to shutdown process gracefully
[Wed Sep 27 17:29:44.000147 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 30381 exit signal Segmentation fault (11)
[Wed Sep 27 17:29:44.208035 2017] [mpm_event:alert] [pid 30382:tid 123145438388224] (35)Resource temporarily unavailable: AH03104: apr_thread_create: unable to create worker thread
[Wed Sep 27 17:29:44.208925 2017] [mpm_event:crit] [pid 30382:tid 123145446436864] (9)Bad file descriptor: apr_pollset_poll failed. Attempting to shutdown process gracefully
[Wed Sep 27 17:29:45.001702 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 30382 exit signal Segmentation fault (11)
[Wed Sep 27 17:29:48.881247 2017] [core:crit] [pid 32841:tid 123145544712192] AH00102: [Wed Sep 27 17:29:48 2017] file fdqueue.c, line 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
[Wed Sep 27 17:29:50.004871 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 32841 exit signal Abort trap (6)
[Wed Sep 27 17:29:52.366672 2017] [core:crit] [pid 35505:tid 123145420349440] AH00102: [Wed Sep 27 17:29:52 2017] file fdqueue.c, line 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
[Wed Sep 27 17:29:52.368902 2017] [core:crit] [pid 35488:tid 123145392611328] AH00102: [Wed Sep 27 17:29:52 2017] file fdqueue.c, line 390, assertion "!((queue)->nelts == (queue)->bounds)" failed
[Wed Sep 27 17:29:53.007664 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 35505 exit signal Abort trap (6)
[Wed Sep 27 17:29:53.007741 2017] [core:notice] [pid 23404:tid 140736895005632] AH00052: child pid 35488 exit signal Abort trap (6)
> Am 27.09.2017 um 08:46 schrieb Luca Toscano <to...@gmail.com>:
>
> Hi Jim,
>
> 2017-09-25 14:13 GMT+02:00 Jim Jagielski <ji...@jagunet.com>:
> The pre-release test tarballs for Apache httpd
> version 2.4.28 can be found at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.28 GA.
>
> [ ] +1: Good to go
> [ ] +0: meh
> [ ] -1: Danger Will Robinson. And why.
>
> Vote will last the normal 72 hrs.
>
> NOTE: The *-deps are only there for convenience.
>
> +1, tested on Debian Stretch with the latest svn for apr 1.6.x, all tests are running fine.
>
> One nit - got the following error while running the test suite:
>
> t/apache/http_strict.t .. Undefined subroutine &main::need_min_apache_fix called at t/apache/http_strict.t line 122
>
> and patched with
>
> -my $test_fold = need_min_apache_fix("2.2.33", "2.4.26", "2.5.0");
> +my $test_fold = need_min_apache_version("2.2.33")
> + or need_min_apache_version("2.4.26")
> + or need_min_apache_version("2.5.0");
>
> But since nobody is reporting the same problem it is probably an issue with my testing environment.
>
> Thanks for RMing!
>
> Luca
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Luca Toscano <to...@gmail.com>.
Hi Jim,
2017-09-25 14:13 GMT+02:00 Jim Jagielski <ji...@jagunet.com>:
> The pre-release test tarballs for Apache httpd
> version 2.4.28 can be found at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.28 GA.
>
> [ ] +1: Good to go
> [ ] +0: meh
> [ ] -1: Danger Will Robinson. And why.
>
> Vote will last the normal 72 hrs.
>
> NOTE: The *-deps are only there for convenience.
>
+1, tested on Debian Stretch with the latest svn for apr 1.6.x, all tests
are running fine.
One nit - got the following error while running the test suite:
t/apache/http_strict.t .. Undefined subroutine &main::need_min_apache_fix
called at t/apache/http_strict.t line 122
and patched with
-my $test_fold = need_min_apache_fix("2.2.33", "2.4.26", "2.5.0");
+my $test_fold = need_min_apache_version("2.2.33")
+ or need_min_apache_version("2.4.26")
+ or need_min_apache_version("2.5.0");
But since nobody is reporting the same problem it is probably an issue with
my testing environment.
Thanks for RMing!
Luca
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Reindl Harald <h....@thelounge.net>.
Am 29.09.2017 um 14:16 schrieb Eric Covener:
> On Fri, Sep 29, 2017 at 6:57 AM, Reindl Harald <h....@thelounge.net> wrote:
>>
>> Am 29.09.2017 um 12:35 schrieb Graham Leggett:
>>>
>>> On 29 Sep 2017, at 12:25 PM, Reindl Harald <h....@thelounge.net> wrote:
>>>
>>>> it's not about cheap - it's just questionable that after 2.4.12 the next
>>>> release is 2.4.16 because it looks not really sane
>>>
>>>
>>> Looks perfectly sensible to me
>>
>> in your world where you know the background, without the context it looks
>> like "are they not capable to count?"
>
> What kind of user do you think this confusion affects? They'd have to
> care that N-1 wasn't released, but not be reading the changelog
frankly, i personally don't care but it's strange what is the point of
discuss there when alpha.beta,rc,ga is surrounding us over decades (yes,
i know in the modern world there is only 1,2,3,4,5,50,60...)
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Jim Jagielski <ji...@jaguNET.com>.
Leaving it open for another ~24 hours... I don't want
to go thru the process of "releasing" it if someone is
going to gripe after the fact.
FWIW: I'll be at Grace Hopper the rest of the week so
my online time will be sporadic.
> On Sep 30, 2017, at 4:23 PM, Jim Jagielski <ji...@jaguNET.com> wrote:
>
> Can we discuss this on a sep thread. The question now is really
> whether 2.4.28 is DOA or not.
>
> I'm not seeing any -1s... nor have I seen any more info related
> to the assert bug (but I admit I may have missed that)
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Jim Jagielski <ji...@jaguNET.com>.
Can we discuss this on a sep thread. The question now is really
whether 2.4.28 is DOA or not.
I'm not seeing any -1s... nor have I seen any more info related
to the assert bug (but I admit I may have missed that)
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Daniel Ruggeri <dr...@primary.net>.
It's fair to reiterate first that most folks here don't care and "get it"... but let me offer another perspective that folks may have to deal with. Devil's advocate here, and all that.
1.2.4 is released. It contains security fixes
1.2.5 is burned during RM
1.2.6 is burned during RM
1.2.7 is released. It contains bug fixes
1.2.8 is burned during RM
1.2.9 is released. It contains security fixes
Let's say I choose not to build and deploy 1.2.7 since I am not using any of the modules the bug fixes address.
To the uneducated eye (AKA: the auditor, the security engineer not familiar with httpd's versioning idiosyncrasies, the manager, etc), it may appear as a serious lapse in patching if five releases were between deployed versions. "9 is MUCH higher than 4! What have you been DOING all day?" they might ask.
Another angle is the unspoken angst of upgrading five point releases versus one point release. It *shouldn't* be scary... but it can be for someone who doesn't fully trust us to avoid releasing regressions.
Granted, both represent shaky logic that can be fixed by RTFM... but are things I've seen in the field (and have answered with a 301 to the CHANGES file).
--
Daniel Ruggeri
-------- Original Message --------
From: Eric Covener <co...@gmail.com>
Sent: September 29, 2017 7:16:51 AM CDT
To: Apache HTTP Server Development List <de...@httpd.apache.org>
Subject: Re: [VOTE] Release Apache httpd 2.4.28 as GA
On Fri, Sep 29, 2017 at 6:57 AM, Reindl Harald <h....@thelounge.net> wrote:
>
>
> Am 29.09.2017 um 12:35 schrieb Graham Leggett:
>>
>> On 29 Sep 2017, at 12:25 PM, Reindl Harald <h....@thelounge.net> wrote:
>>
>>> it's not about cheap - it's just questionable that after 2.4.12 the next
>>> release is 2.4.16 because it looks not really sane
>>
>>
>> Looks perfectly sensible to me
>
>
> in your world where you know the background, without the context it looks
> like "are they not capable to count?"
What kind of user do you think this confusion affects? They'd have to
care that N-1 wasn't released, but not be reading the changelog.
--
Eric Covener
covener@gmail.com
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Eric Covener <co...@gmail.com>.
On Fri, Sep 29, 2017 at 6:57 AM, Reindl Harald <h....@thelounge.net> wrote:
>
>
> Am 29.09.2017 um 12:35 schrieb Graham Leggett:
>>
>> On 29 Sep 2017, at 12:25 PM, Reindl Harald <h....@thelounge.net> wrote:
>>
>>> it's not about cheap - it's just questionable that after 2.4.12 the next
>>> release is 2.4.16 because it looks not really sane
>>
>>
>> Looks perfectly sensible to me
>
>
> in your world where you know the background, without the context it looks
> like "are they not capable to count?"
What kind of user do you think this confusion affects? They'd have to
care that N-1 wasn't released, but not be reading the changelog.
--
Eric Covener
covener@gmail.com
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Reindl Harald <h....@thelounge.net>.
Am 29.09.2017 um 12:35 schrieb Graham Leggett:
> On 29 Sep 2017, at 12:25 PM, Reindl Harald <h....@thelounge.net> wrote:
>
>> it's not about cheap - it's just questionable that after 2.4.12 the next release is 2.4.16 because it looks not really sane
>
> Looks perfectly sensible to me
in your world where you know the background, without the context it
looks like "are they not capable to count?"
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Graham Leggett <mi...@sharp.fm>.
On 29 Sep 2017, at 12:25 PM, Reindl Harald <h....@thelounge.net> wrote:
> it's not about cheap - it's just questionable that after 2.4.12 the next release is 2.4.16 because it looks not really sane
Looks perfectly sensible to me.
Regards,
Graham
—
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Reindl Harald <h....@thelounge.net>.
Am 29.09.2017 um 12:16 schrieb Graham Leggett:
> On 28 Sep 2017, at 7:10 PM, Helmut K. C. Tessarek <te...@evermeet.cx> wrote:
>
>> I have a question. Why are you tagging a release and do testing? Most of
>> the time a problem is found and a new release is tagged and it starts
>> over (I think the max was a 3 or 4 patch level jump).
>>
>> Why not tagging an RC? People test the RC. When all is ok, the RC is
>> released. If not a new RC is tagged.
>
> Because version numbers are cheap. If you call it RC, or call it the next patch version, it doesn’t ultimately matter
it's not about cheap - it's just questionable that after 2.4.12 the next
release is 2.4.16 because it looks not really sane
* Fr Jul 10 2015 Reindl Harald <h....@thelounge.net>
- update to 2.4.16 (2.4.13, 2.4.14 and 2.4.15 was skipped upstream)
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Graham Leggett <mi...@sharp.fm>.
On 28 Sep 2017, at 7:10 PM, Helmut K. C. Tessarek <te...@evermeet.cx> wrote:
> I have a question. Why are you tagging a release and do testing? Most of
> the time a problem is found and a new release is tagged and it starts
> over (I think the max was a 3 or 4 patch level jump).
>
> Why not tagging an RC? People test the RC. When all is ok, the RC is
> released. If not a new RC is tagged.
Because version numbers are cheap. If you call it RC, or call it the next patch version, it doesn’t ultimately matter.
Regards,
Graham
—
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by "Helmut K. C. Tessarek" <te...@evermeet.cx>.
On 2017-09-28 09:51, Jim Jagielski wrote:
> Personally, I don't think the age or heritage of the build-logic is the issue,
> but rather a lack of people *really* testing 2.4.x until a release is tagged.
> It's for that reason that I tend to pre-announce a T&R well in advance of actually
> DOING the T&R so that people can test HEAD in hopes that the tag will already
> have had some good testing beforehand.
I have a question. Why are you tagging a release and do testing? Most of
the time a problem is found and a new release is tagged and it starts
over (I think the max was a 3 or 4 patch level jump).
Why not tagging an RC? People test the RC. When all is ok, the RC is
released. If not a new RC is tagged.
Cheers,
K. C.
--
regards Helmut K. C. Tessarek KeyID 0xF7832007C11F128D
Key fingerprint = 28A3 1666 4FE8 D72C CFD5 8B23 F783 2007 C11F 128D
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Jim Jagielski <ji...@jaguNET.com>.
If the issue is "real" and a patch is forthcoming, I agree that we
mark 2.4.28 as DOA and proceed w/ 2.4.29 next week. I am comfortable keeping
the VOTE open longer that the normal/required 72hours to be sure one way
or another.
Personally, I don't think the age or heritage of the build-logic is the issue,
but rather a lack of people *really* testing 2.4.x until a release is tagged.
It's for that reason that I tend to pre-announce a T&R well in advance of actually
DOING the T&R so that people can test HEAD in hopes that the tag will already
have had some good testing beforehand.
> On Sep 27, 2017, at 11:21 PM, William A Rowe Jr <wr...@rowe-clan.net> wrote:
>
> The assert() has me concerned, and Steffen's report is problematic. He has a vote but hasn't cast it. At this moment I'm -0 and would spin a 2.4.29 next week to address these issues, unless you decide to respin before this release, yourself.
>
> Nothing I've changed today altered the httpd tarball significantly. Studying Steffen's report next, along with some apparently missing glue for brotli.
>
> My solution is going to be radical, shove every last d*mned modules/foo into the /I path includes list so this can't happen again during 2.4, and hopefully not until 20 year old build logic is discarded. One less thing to worry about or pre-review when RM's loudly announce an upcoming tag.
>
>
>
>
> On Sep 25, 2017 07:13, "Jim Jagielski" <ji...@jagunet.com> wrote:
> The pre-release test tarballs for Apache httpd
> version 2.4.28 can be found at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.28 GA.
>
> [ ] +1: Good to go
> [ ] +0: meh
> [ ] -1: Danger Will Robinson. And why.
>
> Vote will last the normal 72 hrs.
>
> NOTE: The *-deps are only there for convenience.
>
> Thx!
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Gregg Smith <gl...@gknw.net>.
+1 to doing a 2.4.29 next week with these issues fixed.
On 9/27/2017 9:21 PM, William A Rowe Jr wrote:
> The assert() has me concerned, and Steffen's report is problematic. He has
> a vote but hasn't cast it. At this moment I'm -0 and would spin a 2.4.29
> next week to address these issues, unless you decide to respin before this
> release, yourself.
>
> Nothing I've changed today altered the httpd tarball significantly.
> Studying Steffen's report next, along with some apparently missing glue for
> brotli.
>
> My solution is going to be radical, shove every last d*mned modules/foo
> into the /I path includes list so this can't happen again during 2.4, and
> hopefully not until 20 year old build logic is discarded. One less thing to
> worry about or pre-review when RM's loudly announce an upcoming tag.
>
>
>
>
> On Sep 25, 2017 07:13, "Jim Jagielski" <ji...@jagunet.com> wrote:
>
>> The pre-release test tarballs for Apache httpd
>> version 2.4.28 can be found at the usual place:
>>
>> http://httpd.apache.org/dev/dist/
>>
>> I'm calling a VOTE on releasing these as Apache httpd 2.4.28 GA.
>>
>> [ ] +1: Good to go
>> [ ] +0: meh
>> [ ] -1: Danger Will Robinson. And why.
>>
>> Vote will last the normal 72 hrs.
>>
>> NOTE: The *-deps are only there for convenience.
>>
>> Thx!
>>
>
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
The assert() has me concerned, and Steffen's report is problematic. He has
a vote but hasn't cast it. At this moment I'm -0 and would spin a 2.4.29
next week to address these issues, unless you decide to respin before this
release, yourself.
Nothing I've changed today altered the httpd tarball significantly.
Studying Steffen's report next, along with some apparently missing glue for
brotli.
My solution is going to be radical, shove every last d*mned modules/foo
into the /I path includes list so this can't happen again during 2.4, and
hopefully not until 20 year old build logic is discarded. One less thing to
worry about or pre-review when RM's loudly announce an upcoming tag.
On Sep 25, 2017 07:13, "Jim Jagielski" <ji...@jagunet.com> wrote:
> The pre-release test tarballs for Apache httpd
> version 2.4.28 can be found at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.28 GA.
>
> [ ] +1: Good to go
> [ ] +0: meh
> [ ] -1: Danger Will Robinson. And why.
>
> Vote will last the normal 72 hrs.
>
> NOTE: The *-deps are only there for convenience.
>
> Thx!
>
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Noel Butler <no...@ausics.net>.
On 25/09/2017 22:13, Jim Jagielski wrote:
> The pre-release test tarballs for Apache httpd
> version 2.4.28 can be found at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.28 GA.
>
> [ ] +1: Good to go
> [ ] +0: meh
> [ ] -1: Danger Will Robinson. And why.
>
> Vote will last the normal 72 hrs.
>
> NOTE: The *-deps are only there for convenience.
>
> Thx!
Hi Jim,
Good to go slackware 13+
--
Kind Regards,
Noel Butler
This Email, including any attachments, may contain legally privileged
information, therefore remains confidential and subject to copyright
protected under international law. You may not disseminate, discuss, or
reveal, any part, to anyone, without the authors express written
authority to do so. If you are not the intended recipient, please notify
the sender then delete all copies of this message including attachments,
immediately. Confidentiality, copyright, and legal privilege are not
waived or lost by reason of the mistaken delivery of this message. Only
PDF [1] and ODF [2] documents accepted, please do not send proprietary
formatted documents
Links:
------
[1] http://www.adobe.com/
[2] http://en.wikipedia.org/wiki/OpenDocument
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Jim Jagielski <ji...@jaguNET.com>.
> On Sep 25, 2017, at 7:13 AM, Jim Jagielski <ji...@jaguNET.com> wrote:
>
> The pre-release test tarballs for Apache httpd
> version 2.4.28 can be found at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.28 GA.
>
> [ ] +1: Good to go
> [ ] +0: meh
> [ ] -1: Danger Will Robinson. And why.
>
> Vote will last the normal 72 hrs.
>
> NOTE: The *-deps are only there for convenience.
>
> Thx!
+1: macOS 10.12.6 / Xcode 8.3.3
CentOS 6, 64bit
Ubuntu 14.01 LTS, 64bit
Ubuntu 16.01 LTS, 64bit
Fedora 22, 64bit
Re: [VOTE] Release Apache httpd 2.4.28 as GA
Posted by Eric Covener <co...@gmail.com>.
On Mon, Sep 25, 2017 at 8:13 AM, Jim Jagielski <ji...@jagunet.com> wrote:
> The pre-release test tarballs for Apache httpd
> version 2.4.28 can be found at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.28 GA.
>
> [ ] +1: Good to go
+1 AIX/xlc/ppc64 w/ openssl 1.1.
Does not run clean on my systems anymore, but no regressions.