| Author |
|
o6asan
Joined: 27 Aug 2015
Posts: 44
Location: Japan, Fukuoka
|
|
| Back to top |
|
Jan-E
Joined: 09 Mar 2012
Posts: 1266
Location: Amsterdam, NL, EU
|
 Posted: Thu 20 Apr '17 1:16 Post subject: |
 |
|
| Did you have those problems with Apache 2.4.26-dev, downloaded today? |
|
| Back to top |
|
o6asan
Joined: 27 Aug 2015
Posts: 44
Location: Japan, Fukuoka
|
| Posted: Thu 20 Apr '17 2:15 Post subject: |
|
|
| Jan-E wrote: | | Did you have those problems with Apache 2.4.26-dev, downloaded today? |
@Jan-E I have the problem with Apache 2.4.26-dev which I downloaded around 13:00 UTC on April 19. Does this include your today? |
|
| Back to top |
|
Jan-E
Joined: 09 Mar 2012
Posts: 1266
Location: Amsterdam, NL, EU
|
|
| Back to top |
|
o6asan
Joined: 27 Aug 2015
Posts: 44
Location: Japan, Fukuoka
|
| Posted: Thu 20 Apr '17 6:22 Post subject: |
|
|
@Jan-E Thank you for the report https://github.com/icing/mod_h2/issues/133#issuecomment-295507674.
The original author said he could not reproduce the error with v1.10.2.
Steffen said he built Apache 2.4.26-Dev with mod_http2 1.10.1.
So I expect it will be fixed if we have Apache 2.4.26-Dev with mod_http2 1.10.2. |
|
| Back to top |
|
icing
Joined: 22 Sep 2015
Posts: 41
Location: Münster, Germany
|
| Posted: Thu 20 Apr '17 10:15 Post subject: |
|
|
Regarding the mod_proxy_http2 problem, there will be no difference between 1.10.1 and 1.10.2. So, if you see that with the former, expect it to be still there with the latter.
I was unable to reproduce this. If you have a simple setup and requests to trigger the bug, I would be very interested.
Thanks!
-Stefan |
|
| Back to top |
|
Steffen
Moderator
Joined: 15 Oct 2005
Posts: 3092
Location: Hilversum, NL, EU
|
| Posted: Thu 20 Apr '17 10:56 Post subject: |
|
|
| Updated mod_http2 from 1.10.1 to 1.10.2. To confirm Stefan, please check if 1.10.2 not solves it. |
|
| Back to top |
|
Jan-E
Joined: 09 Mar 2012
Posts: 1266
Location: Amsterdam, NL, EU
|
| Posted: Sun 23 Apr '17 17:44 Post subject: |
|
|
| Steffen wrote: | | mod_http2 is now again 1.0.1, coming days it is upgraded to 1.0.3. |
Typo: that must be 1.10.1 and 1.10.3.
Will you continue to build Apache VC14? PHP 7.2 will only be released on Nov 30th this year:
https://wiki.php.net/todo/php72#timetable |
|
| Back to top |
|
o6asan
Joined: 27 Aug 2015
Posts: 44
Location: Japan, Fukuoka
|
| Posted: Sun 30 Apr '17 16:31 Post subject: |
|
|
@icing and @Steffen
I think I should apologize two of you because I was wrong about the error 'AH03467'. Sorry.
Icing said there would be no difference between 1.10.1 and 1.10.2. And I still had the error even after moving from 1.10.1 to 1.10.2. So, I checked out my old logs and found I had the first of this error at 2017 Feb. 09. So the error doesn't depend on neither 1.10.1 nor 1.10.2.
I couldn't know what situation gives the error.
Now I decides to move to a VC15 build, but will keep watching the error after moving. |
|
| Back to top |
|
Steffen
Moderator
Joined: 15 Oct 2005
Posts: 3092
Location: Hilversum, NL, EU
|
| Posted: Sun 30 Apr '17 17:21 Post subject: |
|
|
No problem, that happens.
Hope you keep reporting. |
|
| Back to top |
|
icing
Joined: 22 Sep 2015
Posts: 41
Location: Münster, Germany
|
| Posted: Tue 02 May '17 16:00 Post subject: |
|
|
| @o6asan thanks for the update. And no need for an apology! It helps a lot that you are all testing and reporting. |
|
| Back to top |
|
Jan-E
Joined: 09 Mar 2012
Posts: 1266
Location: Amsterdam, NL, EU
|
| Posted: Thu 04 May '17 21:19 Post subject: Re: Apache 2.4.26-Dev available with Openssl 1.1.0e VC14 |
|
|
| o6asan wrote: | | I had some "AH03467: h2_task(xx-xx): unable to parse status line: \x89PNG" on the Apache log |
There now is a new report on the same problem:
https://github.com/icing/mod_h2/issues/138
Possible explanation: "it seems that mod_http2 thinks that is parsing a serialized http/1.1 response but instead has html, gzipped data, a png file, or basically something that is not an http/1.1 response." |
|
| Back to top |
|
xplode
Joined: 04 Nov 2016
Posts: 3
|
| Posted: Fri 05 May '17 0:17 Post subject: |
|
|
I opened github issue https://github.com/icing/mod_h2/issues/138 . I haven't been able to nail down a recreate scenario in a controlled environment, but am open to ideas.
I am also investigating another h2 issue: Old gen processes which have one h2 request, but nothing is happening. The old gen process just hangs out with with it's single h2 request.
Has anyone has seen this or know if this behavior is fixed in h2 version 1.10.3. Did the deadlock that could occur when connections were terminated early with ongoing streams exhibit itself in this way?
My configuration
apache: 2.4.25
openssl: 1.0.2j
nghttp2: 1.21.1
mod_http2: 1.10.1 |
|
| Back to top |
|
xplode
Joined: 04 Nov 2016
Posts: 3
|
| Posted: Fri 05 May '17 20:05 Post subject: |
|
|
Regarding the old gen h2 process that is left hanging, this thread seems to be related: https://www.mail-archive.com/dev@httpd.apache.org/msg68544.html
UPDATE (5-8-2017) The old gen h2 hanging process problem (which can be seen as an old gen process line in server-status if you have mod_status configured) is reproduce-able by continually reloading apache while the server is under load. This problem appears to be fixed by build 1.10.3 |
|
| Back to top |
|
