Bug report for Apache httpd-2 [2023/06/25]

2023-06-25 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 66664] New: Request for crl fallback enabling

2023-06-22 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=4 Bug ID: 4 Summary: Request for crl fallback enabling Product: Apache httpd-2 Version: 2.5-HEAD Hardware: All OS: All Status: NEW Severity

[Bug 66626] OCSP Stapling with Revoked Certificate are not Returning Proper Return Value

2023-06-21 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66626 --- Comment #2 from q...@tenable.com --- Just out of curiosity when do the trunk fixes get pulled into the 2.4.x release? Or is that something that will come out in the upcoming 2.6.x release? -- You are receiving this mail because: You

[Bug 66656] JS not loaded in script language - Jmeter ver 5.2.1

2023-06-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66656 Ruediger Pluem changed: What|Removed |Added Resolution|--- |FIXED OS

[Bug 66657] Support for OCSP Caching

2023-06-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66657 --- Comment #3 from Stefan Eissing --- No, this is for adding stapling information to TLS handshake to the client. It will not help you with managing stapling of client certificates. Sorry if I misunderstood your original question. -- You

[Bug 66657] Support for OCSP Caching

2023-06-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66657 --- Comment #2 from davide schiaroli --- Does this work if I don't want stapling? Example: In my configuration, i want to use SSLOCSPEnable On, and SSLUseStapling off -- You are receiving this mail because: You are the assignee for the bug

[Bug 66657] Support for OCSP Caching

2023-06-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66657 --- Comment #1 from Stefan Eissing --- There is an alternative in the `mod_md` module that provides stapling with caching to disk and renewal before the stapling timeout expires. See <https://httpd.apache.org/docs/2.4/mod/mod_md.h

[Bug 66657] New: Support for OCSP Caching

2023-06-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66657 Bug ID: 66657 Summary: Support for OCSP Caching Product: Apache httpd-2 Version: 2.5-HEAD Hardware: All OS: All Status: NEW Severity: enhancement

[Bug 66649] apache http2 endless loop in h2_session_send in httpd-2.4.55/56/57

2023-06-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66649 Stefan Eissing changed: What|Removed |Added Resolution|--- |FIXED Status|NEEDINFO

[Bug 66649] apache http2 endless loop in h2_session_send in httpd-2.4.55/56/57

2023-06-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66649 --- Comment #8 from Barnim Dzwillo --- The patched httpd runs without trigger for an infinite loop since friday. So patch r1910331 + r1910441 seems to fix the problem. Thank you again. -- You are receiving this mail because: You

[Bug 66656] New: JS not loaded in script language - Jmeter ver 5.2.1

2023-06-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66656 Bug ID: 66656 Summary: JS not loaded in script language - Jmeter ver 5.2.1 Product: Apache httpd-test Version: unspecified Hardware: PC Status: NEW Severity: blocker

[Bug 66655] New: Error reading data from upstream server

2023-06-18 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66655 Bug ID: 66655 Summary: Error reading data from upstream server Product: Apache httpd-2 Version: 2.4.6 Hardware: PC Status: NEW Severity: critical Priority

Bug report for Apache httpd-2 [2023/06/18]

2023-06-18 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 66649] apache http2 endless loop in h2_session_send in httpd-2.4.55/56/57

2023-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66649 --- Comment #7 from Barnim Dzwillo --- Ok - I added the r1910441 patch and keep running the test over the weekend now. -- You are receiving this mail because: You are the assignee for the bug

[Bug 66649] apache http2 endless loop in h2_session_send in httpd-2.4.55/56/57

2023-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66649 --- Comment #6 from Stefan Eissing --- Added to trunk as r1910441. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail: bugs

[Bug 66649] apache http2 endless loop in h2_session_send in httpd-2.4.55/56/57

2023-06-16 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66649 --- Comment #5 from Stefan Eissing --- I believe the infinite loop happens when the error is ignored, yes. That was observed in the other PR. But, while that will exit the loop, the connection state in h2_c1_io.c is still in a inconsistent

[Bug 66649] apache http2 endless loop in h2_session_send in httpd-2.4.55/56/57

2023-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66649 --- Comment #4 from Barnim Dzwillo --- Lets see - i am testing the patch now. If there is a situation where h2_c1_io_assure_flushed() returns just once a status != APR_SUCCESS, then the patch could help. -- You are receiving this mail

[Bug 66649] apache http2 endless loop in h2_session_send in httpd-2.4.55/56/57

2023-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66649 --- Comment #3 from Stefan Eissing --- Hmm, that would mean `h2_c1_io_needs_flush()` returns TRUE and `h2_c1_io_pending()` is FALSE on your system? Or do we have a case where `nghttp2_session_send()` always blocks, but there is nothing

[Bug 66649] apache http2 endless loop in h2_session_send in httpd-2.4.55/56/57

2023-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66649 --- Comment #2 from Barnim Dzwillo --- I can try this patch, but at first glance it looks as if this will not help for this situation: - rv = h2_c1_io_assure_flushed(>io) will check for 'if (h2_c1_io_pending(io) || io->unf

[Bug 66649] apache http2 endless loop in h2_session_send in httpd-2.4.55/56/57

2023-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66649 Stefan Eissing changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #1 from Stefan

[Bug 66649] New: apache http2 endless loop in h2_session_send in httpd-2.4.55/56/57

2023-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66649 Bug ID: 66649 Summary: apache http2 endless loop in h2_session_send in httpd-2.4.55/56/57 Product: Apache httpd-2 Version: 2.4.57 Hardware: PC OS: Linux

[Bug 60503] Feature request: mod_macro - allow optional parameters

2023-06-15 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60503 --- Comment #2 from Marc Stern --- What about a simple syntax like this: Simple to write, simple to read, reasonably compact. If everybody agrees I'm ready to help adapting the code and testing. -- You are receiving this mail because: You

[Bug 66646] apache http2 h2eos bucket corruption in httpd-2.4.55/56/57 (with workaround)

2023-06-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66646 --- Comment #10 from Barnim Dzwillo --- Hello, the patched httpd runs without problems for nearly one day now. It didn't crash and didn't trigger the debug-messages, so the bugfix seems to work. Thank you again. It would be nice

[Bug 66642] invalid response treated as http/0.9 by proxy

2023-06-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66642 --- Comment #6 from Ruediger Pluem --- I guess we need to have an option to deny HTTP/0.9 responses. I am not sure if we could disable them by default for compatibility reasons. -- You are receiving this mail because: You are the assignee

[Bug 66642] invalid response treated as http/0.9 by proxy

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66642 Eric Covener changed: What|Removed |Added Summary|If apache is acting as a|invalid response treated

[Bug 66642] If apache is acting as a reverse proxy, and the downstream service it's proxying for returns a malformed response then apache returns 200, Instead I would expect apache to either handle th

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66642 Eric Covener changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #5 from Eric Covener

[Bug 66642] If apache is acting as a reverse proxy, and the downstream service it's proxying for returns a malformed response then apache returns 200, Instead I would expect apache to either handle th

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66642 --- Comment #4 from shashank --- This is the info related to app: https://github.com/hmshashank/malformed-http This is the related Discussion we opened in github: https://github.com/apache/airflow/issues/29167 This is the only info i could

[Bug 66642] If apache is acting as a reverse proxy, and the downstream service it's proxying for returns a malformed response then apache returns 200, Instead I would expect apache to either handle th

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66642 --- Comment #3 from Eric Covener --- (In reply to shashank from comment #2) > Apache should return whatever response it gets from the app side. Because of > the presence of the b' in the response body apache is not able to unde

[Bug 66646] apache http2 h2eos bucket corruption in httpd-2.4.55/56/57 (with workaround)

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66646 --- Comment #9 from Barnim Dzwillo --- Thank you for the fast feedback Stefan. I applied your patch, disabled my workaround and kept my check-code active. This runs for 30 minutes now, and nether my check nor the 'Denied to prevent..' check

[Bug 66642] If apache is acting as a reverse proxy, and the downstream service it's proxying for returns a malformed response then apache returns 200, Instead I would expect apache to either handle th

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66642 --- Comment #2 from shashank --- Apache should return whatever response it gets from the app side. Because of the presence of the b' in the response body apache is not able to understand or parse that and by-default its returning 200

[Bug 66646] apache http2 h2eos bucket corruption in httpd-2.4.55/56/57 (with workaround)

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66646 --- Comment #8 from Stefan Eissing --- Thanks Barnim, I was able to reproduce the problem and write a fix. Added as r1910386. Also, this available in <https://github.com/icing/mod_h2/releases/tag/v2.0.19>. Looking forward to he

[Bug 66646] apache http2 h2eos bucket corruption in httpd-2.4.55/56/57 (with workaround)

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66646 --- Comment #7 from Barnim Dzwillo --- Created attachment 38588 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38588=edit combined check and workaround for h2eos bucket corruption (for 2.4.57) -- You are receiving this mail beca

[Bug 66646] apache http2 h2eos bucket corruption in httpd-2.4.55/56/57 (with workaround)

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66646 --- Comment #6 from Barnim Dzwillo --- I added a version of the first 'check'-patch for the 2.4.57 tree now. Hope this helps.. -- You are receiving this mail because: You are the assignee for the bug

[Bug 66646] apache http2 h2eos bucket corruption in httpd-2.4.55/56/57 (with workaround)

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66646 --- Comment #5 from Barnim Dzwillo --- Created attachment 38587 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38587=edit check for h2eos bucket corruption (for 2.4.57 instead of trunk) same as the first patch - applies to svn 2.4

[Bug 66646] apache http2 h2eos bucket corruption in httpd-2.4.55/56/57 (with workaround)

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66646 --- Comment #4 from Barnim Dzwillo --- I rebased the patch to httpd-trunk from the svn repo: https://svn.apache.org/repos/asf/httpd/httpd/trunk In the 2.4.57 version just 'apr_bucket_delete(bucket)' is called instead of 'delete_meta_bucket

[Bug 66646] apache http2 h2eos bucket corruption in httpd-2.4.55/56/57 (with workaround)

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66646 --- Comment #3 from Stefan Eissing --- The first patch, the check, does not apply to your 2.4.x sources. There is a "delete_meta_bucket()" function referenced that does not exist. Is this some other change by your not included or d

[Bug 66646] apache http2 h2eos bucket corruption in httpd-2.4.55/56/57 (with workaround)

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66646 --- Comment #2 from Stefan Eissing --- Thanks for the report with the detailed analysis and patched. I'll try to analyse what the root cause here is. -- You are receiving this mail because: You are the assignee for the bug

[Bug 66642] If apache is acting as a reverse proxy, and the downstream service it's proxying for returns a malformed response then apache returns 200, Instead I would expect apache to either handle th

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66642 Eric Covener changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #1 from Eric

[Bug 66646] apache http2 h2eos bucket corruption in httpd-2.4.55/56/57 (with workaround)

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66646 --- Comment #1 from Barnim Dzwillo --- Created attachment 38586 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38586=edit workaround for h2eos bucket corruption -- You are receiving this mail because: You are the assignee for the

[Bug 66646] New: apache http2 h2eos bucket corruption in httpd-2.4.55/56/57 (with workaround)

2023-06-13 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66646 Bug ID: 66646 Summary: apache http2 h2eos bucket corruption in httpd-2.4.55/56/57 (with workaround) Product: Apache httpd-2 Version: 2.4.57 Hardware: PC

[Bug 66642] If apache is acting as a reverse proxy, and the downstream service it's proxying for returns a malformed response then apache returns 200, Instead I would expect apache to either handle th

2023-06-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66642 shashank changed: What|Removed |Added Summary|If apache is acting as a|If apache is acting

[Bug 66624] Using 100% CPU

2023-06-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #35 from Pascal --- (In reply to Stefan Eissing from comment #34) > Fix added to trunk as r1910331. Thank you very much! I'm wondering if you know if there are some special requests that can trigger the behavi

[Bug 66640] Fix spelling errors in libapreq2

2023-06-12 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66640 Ruediger Pluem changed: What|Removed |Added Version|HEAD|2.5-HEAD Priority|P2

[Bug 66642] If apache is acting as a reverse proxy, and the downstream service it's proxying for returns a malformed response, apache returns 200, I would expect apache to either handle that badly and

2023-06-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66642 shashank changed: What|Removed |Added CC||hmshashank2...@gmail.com

[Bug 66643] After connecting to the CDN, the backend log of website access records 403. The error log shows that SSL handshake failed, and accessing without connecting to the CDN is normal

2023-06-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66643 李 <1557387...@qq.com> changed: What|Removed |Added OS||All -- You are rec

[Bug 66643] New: After connecting to the CDN, the backend log of website access records 403. The error log shows that SSL handshake failed, and accessing without connecting to the CDN is normal

2023-06-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66643 Bug ID: 66643 Summary: After connecting to the CDN, the backend log of website access records 403. The error log shows that SSL handshake failed, and accessing without connecting

[Bug 66642] New: If apache is acting as a reverse proxy, and the downstream service it's proxying for returns a malformed response, apache returns 200, I would expect apache to either handle that badl

2023-06-11 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66642 Bug ID: 66642 Summary: If apache is acting as a reverse proxy, and the downstream service it's proxying for returns a malformed response, apache returns 200, I would expect

Bug report for Apache httpd-2 [2023/06/11]

2023-06-11 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 66639] SEGV on strlen-avx2.S:65

2023-06-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66639 --- Comment #1 from Giovanni Bechis --- Sendinghtdbm.c Transmitting file data .done Committing transaction... Committed revision 1910334. -- You are receiving this mail because: You are the assignee for the bug

[Bug 66624] Using 100% CPU

2023-06-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #34 from Stefan Eissing --- Fix added to trunk as r1910331. -- You are receiving this mail because: You are the assignee for the bug. - To unsubscribe, e-mail

[Bug 66639] New: SEGV on strlen-avx2.S:65

2023-06-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66639 Bug ID: 66639 Summary: SEGV on strlen-avx2.S:65 Product: Apache httpd-2 Version: 2.4.54 Hardware: PC OS: Linux Status: NEW Severity: normal

[Bug 66638] New: SEGV in in apr_dbm_firstkey

2023-06-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66638 Bug ID: 66638 Summary: SEGV in in apr_dbm_firstkey Product: Apache httpd-2 Version: 2.4.54 Hardware: PC OS: Linux Status: NEW Severity: normal

[Bug 66637] New: SEGV in apr_dbm_exists

2023-06-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66637 Bug ID: 66637 Summary: SEGV in apr_dbm_exists Product: Apache httpd-2 Version: 2.4.54 Hardware: PC OS: Linux Status: NEW Severity: normal

[Bug 66636] hc https handshake tls1.0 (expecting tls1.2)

2023-06-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66636 --- Comment #1 from ferry --- OpenSSL 3.0.8 7 Feb 2023 (Library: OpenSSL 3.0.8 7 Feb 2023 -- You are receiving this mail because: You are the assignee for the bug

[Bug 66636] New: hc https handshake tls1.0 (expecting tls1.2)

2023-06-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66636 Bug ID: 66636 Summary: hc https handshake tls1.0 (expecting tls1.2) Product: Apache httpd-2 Version: 2.4.55 Hardware: PC OS: Linux Status: NEW Severity

[Bug 66624] Using 100% CPU

2023-06-09 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #33 from Stefan Eissing --- Yes, this patch should be safe on the last released version. -- You are receiving this mail because: You are the assignee for the bug

[Bug 66624] Using 100% CPU

2023-06-08 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #32 from Pascal --- (In reply to Pascal from comment #15) > We also have problems like this (since Apache 2.4.55 - FreeBSD) where > afterwards processes are in the "uwait" state and are using 100% CPU. I'm >

[Bug 66624] Using 100% CPU

2023-06-07 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #31 from chris --- (In reply to Eric Covener from comment #30) > did you overlay one w/ patched version built outside of the distro? Size > could be debug symbols? oh yep, that be the one I built won't it. Not su

[Bug 66624] Using 100% CPU

2023-06-07 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #30 from Eric Covener --- (In reply to chris from comment #29) > Created attachment 38581 [details] > mod filesize different > > Isn't this odd ? the one on the right (new server but same distro) is a > much lower

[Bug 66624] Using 100% CPU

2023-06-07 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #29 from chris --- Created attachment 38581 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38581=edit mod filesize different Isn't this odd ? the one on the right (new server but same distro) is a much lower file s

[Bug 66624] Using 100% CPU

2023-06-07 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #28 from chris --- Been running prefork fine for the past couple of days. So switch backed to event just, and immediately start getting gateway timeout errors and everything was running incredibly slow again. The test I'm doing

[Bug 65922] modules/ssl/ssl_util_ssl.c: Add check for BIO_read

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=65922 Giovanni Bechis changed: What|Removed |Added OS||All Keywords

[Bug 66626] OCSP Stapling with Revoked Certificate are not Returning Proper Return Value

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66626 --- Comment #1 from Giovanni Bechis --- This has been fixed in r1875355 (https://svn.apache.org/viewvc/httpd/httpd/trunk/modules/ssl/ssl_util_stapling.c?r1=1874579=1875355_format=h). -- You are receiving this mail because: You

[Bug 66626] OCSP Stapling with Revoked Certificate are not Returning Proper Return Value

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66626 q...@tenable.com changed: What|Removed |Added CC||q...@tenable.com -- You

[Bug 66626] New: OCSP Stapling with Revoked Certificate are not Returning Proper Return Value

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66626 Bug ID: 66626 Summary: OCSP Stapling with Revoked Certificate are not Returning Proper Return Value Product: Apache httpd-2 Version: 2.4-HEAD Hardware: All

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #27 from chris --- I was just running some benchmarks between EVENT and PREFORK. (EVENT) Percentage of the requests served within a certain time (ms) 50% 6936 66% 7376 75% 7726 80% 7904 90% 8548 95% 8972 98% 9320 99% 9536 100

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #26 from chris --- Isn't this bug report the same thing ? https://bz.apache.org/bugzilla/show_bug.cgi?id=65180 -- You are receiving this mail because: You are the assignee for the bug

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #25 from chris --- Created attachment 38577 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38577=edit Single G hung Thanks. The image is what is shown in the status as the current hung "G" connection. This

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #24 from Eric Covener --- (In reply to chris from comment #23) > ah so I needed to type in backtrace then. "thread apply all bt" -- You are receiving this mail because: You are the assigne

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #23 from chris --- ah so I needed to type in backtrace then. This is one connection which is stuck on "G". Rest of the connections are inactive. I did the backtrace a few seconds apart. [Thread debugging using li

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #22 from chris --- This seems new. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". --Type for more, q to quit, c to continue without paging-- _

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #21 from chris --- Ages later it chucked out this. Continuing. [Thread 0x7fd921ffb700 (LWP 177355) exited] [Thread 0x7fd92966a700 (LWP 177349) exited] [Thread 0x7fd91d7f2700 (LWP 177364) exited] [Thread 0x7fd9227fc700 (LWP

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #20 from chris --- Created attachment 38576 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38576=edit More G hung I'm not 100% sure I am doing this trace right, the guy who normally deals with this stuff is a

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #19 from chris --- (In reply to Eric Covener from comment #18) > The G and W are probably the same situation, with the difference that the > process involved in G are trying to exit (and held up by a hung request). > >

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #18 from Eric Covener --- (In reply to chris from comment #17) > Created attachment 38575 [details] > G-connections hung > > Another example how connections seem to get"hung". Currently on "G". Tho

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #17 from chris --- Created attachment 38575 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38575=edit G-connections hung Another example how connections seem to get"hung". Currently on "G". Th

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #16 from chris --- (In reply to Stefan Eissing from comment #14) > My humour sometimes gets me carried away. I hope we have found the problem > that is causing issues for you is what I meant to say. Yes understood. T

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 Pascal changed: What|Removed |Added CC||pascal.christen@hostpoint.c

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #15 from Pascal --- We also have problems like this (since Apache 2.4.55 - FreeBSD) where afterwards processes are in the "uwait" state and are using 100% CPU. I'm currently testing the patch you posted and will give yo

[Bug 66624] Using 100% CPU

2023-06-06 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #14 from Stefan Eissing --- My humour sometimes gets me carried away. I hope we have found the problem that is causing issues for you is what I meant to say. -- You are receiving this mail because: You are the assignee

[Bug 66624] Using 100% CPU

2023-06-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #13 from Stefan Eissing --- Thanks for testing this. Looking forward to not hearing from you for a long time! -- You are receiving this mail because: You are the assignee for the bug

[Bug 66624] Using 100% CPU

2023-06-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 chris changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #12 from chris

[Bug 66624] Using 100% CPU

2023-06-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #11 from chris --- Created attachment 38574 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38574=edit Patched hung W connections -- You are receiving this mail because: You are the assignee for the

[Bug 66624] Using 100% CPU

2023-06-05 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 chris changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #10 from chris --- I am now

[Bug 66624] Using 100% CPU

2023-06-04 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #9 from chris --- Thanks, I don't know how to compile stuff, but I might know someone who can do it for me. Indeed the connections which get stuck never seem to close, I have had them open for hours. Its those which get stuck

[Bug 66624] Using 100% CPU

2023-06-04 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #8 from Stefan Eissing --- Created attachment 38572 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38572=edit proposed patch to mod_http2 -- You are receiving this mail because: You are the assignee for the

[Bug 66624] Using 100% CPU

2023-06-04 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #7 from Stefan Eissing --- Thanks for the backtrace. In it, I see one http2 connection that tries to send data to the client. All other thread are in `cond_wait()`, afaict. Assuming this thread is causing the 100%, I looked

[Bug 66624] Using 100% CPU

2023-06-04 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #6 from chris --- # gdb -p 182047 GNU gdb (Ubuntu 9.2-0ubuntu1~20.04.1) 9.2 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free softwar

[Bug 66624] Using 100% CPU

2023-06-04 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 Eric Covener changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #5 from Eric

[Bug 66624] Using 100% CPU

2023-06-04 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #4 from chris --- All I can really tell is, A connection opens to download something, mostly small images. The connection sends about 50-60KB then "stalls". It then sits in that state until its manually killed. PHP time

[Bug 66624] Using 100% CPU

2023-06-04 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #3 from chris --- All I can really tell is, A connection opens to download something, mostly small images. The connection sends about 50-60KB then "stalls". It then sits in that state until its manually killed. PHP time

[Bug 66624] Using 100% CPU

2023-06-04 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #2 from chris --- Added a new image. It show a connection (mostly they are from AWS) where it is stuck on "W" on the same link. No figures change other than the CPU time which just goes up constantly, but also consume

[Bug 66624] Using 100% CPU

2023-06-04 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 --- Comment #1 from chris --- Created attachment 38571 --> https://bz.apache.org/bugzilla/attachment.cgi?id=38571=edit CPU usage -- You are receiving this mail because: You are the assignee for the

Bug report for Apache httpd-2 [2023/06/04]

2023-06-04 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 66624] New: Using 100% CPU

2023-06-03 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66624 Bug ID: 66624 Summary: Using 100% CPU Product: Apache httpd-2 Version: 2.4.57 Hardware: Other OS: Linux Status: NEW Severity: critical

[Bug 50669] SIGWINCH kills Apache

2023-05-31 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=50669 --- Comment #4 from Olliver --- @rpluem is this still true 12 years later? Are there no other ways to signal apache without abusing SIGWINCH? Having apache exit after a window change is a bit odd. One work-around could be, to actually

[Bug 66615] httpd kills keepalive connections when idle workers available

2023-05-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66615 --- Comment #4 from mkemp...@xtm-intl.com --- (In reply to Eric Covener from comment #2) > > httpd seems to not register that it has free workers even when I set > > StartServers to 120 > > startservers only controls ho

[Bug 66615] httpd kills keepalive connections when idle workers available

2023-05-30 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66615 --- Comment #3 from Ruediger Pluem --- Did you have a look at https://httpd.apache.org/docs/2.4/mod/event.html#asyncrequestworkerfactor ? -- You are receiving this mail because: You are the assignee for the bug

Bug report for Apache httpd-2 [2023/05/28]

2023-05-28 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

[Bug 66615] httpd kills keepalive connections when idle workers available

2023-05-26 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=66615 --- Comment #2 from Eric Covener --- > httpd seems to not register that it has free workers even when I set > StartServers to 120 startservers only controls how many are created at startup. Every second, min/max spare t

<    2   3   4   5   6   7   8   9   10   11   >