[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452 --- Comment #9 from Yann Ylavic --- Comment on attachment 37252 --> https://bz.apache.org/bugzilla/attachment.cgi?id=37252 gdb procedure >(gdb) run >Starting program: /path/to/httpd -f /path/to/httpd.conf -X >[...] ># here httpd is waiting

[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452 --- Comment #8 from Yann Ylavic --- Created attachment 37252 --> https://bz.apache.org/bugzilla/attachment.cgi?id=37252=edit gdb procedure Here are the gdb steps for me to reach the cleanup point, does it work the same for you? -- You are

[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452 --- Comment #7 from Bernhard Friedreich --- Here are the modules loaded (apachectl -M): Loaded Modules: core_module (static) so_module (static) http_module (static) logio_module (shared) mime_magic_module (shared) expires_module (shared)

[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452 --- Comment #6 from Yann Ylavic --- Also, since you can reproduce easily (I can't), can you run a debugger with some instructions? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452 --- Comment #5 from Yann Ylavic --- I can only see a reason for the file to not be cleaned up: another request cleanup that runs before and fails (killing the cleanup chain). Which modules are in use? -- You are receiving this mail

[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452 --- Comment #4 from Bernhard Friedreich --- This is from the "main" errorlog. As already stated we are using a self compiled Apache. There is nothing related in the vhost error logs.. -- You are receiving this mail because: You are the

[Bug 61090] mod_proxy gives 502 on early HTTP response (3xx, 4xx, 5xx)

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=61090 Michael Osipov changed: What|Removed |Added CC||micha...@apache.org -- You are

[Bug 64016] Apache HTTPD intermittently report errors AH01084 and AH01097 with 502

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64016 Michael Osipov changed: What|Removed |Added CC||micha...@apache.org -- You are

[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452 --- Comment #3 from Yann Ylavic --- Did you also look at the main error log? I don't know if RHEL uses a single error log file or one per vhost (plus the main one), so I ask.. -- You are receiving this mail because: You are the assignee for

[Bug 60717] mod_proxy_http fails with 502 when backend sends 401 and closes connection immediately

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=60717 --- Comment #2 from Michael Osipov --- I must revert my comment. It is not fixed by the noted issue. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452 --- Comment #2 from Bernhard Friedreich --- No nothing in error log. Only as disk was already full: [Tue May 12 07:17:10.399683 2020] [proxy_http:error] [pid 31956:tid 139971851650816] (20014)Internal error (specific information not

[Bug 64452] modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452 --- Comment #1 from Yann Ylavic --- Any particular message in error_log file (like "child pid xxx exit signal..")? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 64452] New: modproxy.tmp Files filling up /tmp after upgrade to 2.4.43

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64452 Bug ID: 64452 Summary: modproxy.tmp Files filling up /tmp after upgrade to 2.4.43 Product: Apache httpd-2 Version: 2.4.43 Hardware: PC OS: Linux

[Bug 64451] New: mod_reqtimeout + rewriteengine

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64451 Bug ID: 64451 Summary: mod_reqtimeout + rewriteengine Product: Apache httpd-2 Version: 2.4.29 Hardware: PC OS: Linux Status: NEW Severity: normal

[Bug 64449] semaphore leak on restart

2020-05-19 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=64449 --- Comment #2 from iko...@yandex.ru --- (In reply to Eric Covener from comment #1) > What modules are in use? In a sandbox can you get it to stop leaking by > removing any module or directive? I use almost standard EL7 config. # httpd -M