https://bz.apache.org/bugzilla/show_bug.cgi?id=53579
juniorolald...@gmail.com changed:
What|Removed |Added
Status|REOPENED|NEW
--
You are receiving
https://bz.apache.org/bugzilla/show_bug.cgi?id=53579
ithan changed:
What|Removed |Added
CC|ar...@maven.pl, |ithanr...@gmail.com
https://bz.apache.org/bugzilla/show_bug.cgi?id=53579
Christophe JAILLET changed:
What|Removed |Added
Resolution|LATER |---
Status|RESOLVED
https://bz.apache.org/bugzilla/show_bug.cgi?id=53579
William A. Rowe Jr. changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=53579
--- Comment #13 from Yann Ylavic ---
Created attachment 35795
--> https://bz.apache.org/bugzilla/attachment.cgi?id=35795=edit
Check POD on poll() timeout
Does this patch help?
--
You are receiving this mail because:
https://bz.apache.org/bugzilla/show_bug.cgi?id=53579
Paul Ripke changed:
What|Removed |Added
CC||stix...@gmail.com
--
https://bz.apache.org/bugzilla/show_bug.cgi?id=53579
--- Comment #12 from Paul Ripke ---
+1.
Server version: Apache/2.4.29 (Unix)
Server built: Jan 29 2018 09:45:53
Server's Module Magic Number: 20120211:68
Server loaded: APR 1.6.3, APR-UTIL 1.6.1
Compiled using: APR
https://bz.apache.org/bugzilla/show_bug.cgi?id=53579
Szőgyényi Gábor changed:
What|Removed |Added
CC|
https://bz.apache.org/bugzilla/show_bug.cgi?id=53579
--- Comment #11 from Andrea Leofreddi ---
I could observe this issue with 2.4.6 (default httpd package on CentOS 7).
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=53579
Mahudeeswaran changed:
What|Removed |Added
CC||mahud...@gmail.com
https://bz.apache.org/bugzilla/show_bug.cgi?id=53579
--- Comment #9 from Mark Evans mark_a_ev...@dell.com ---
Any updates on this issue? Still running into it on 2.4.10... Any ideas on how
to force recreation? Looks like there needs to be a way to verify that the pod
writes are being consumed?
https://bz.apache.org/bugzilla/show_bug.cgi?id=53579
Mark Evans mark_a_ev...@dell.com changed:
What|Removed |Added
CC|
https://issues.apache.org/bugzilla/show_bug.cgi?id=53579
--- Comment #8 from Loic Etienne loic.etie...@tech.swisssign.com ---
We observed that some processes try to read from the pipe of death from the
file descriptor 0 (instead of 7 on our system, from which other processes read
the pipe of
https://issues.apache.org/bugzilla/show_bug.cgi?id=53579
--- Comment #7 from Loic Etienne loic.etie...@tech.swisssign.com ---
We could also observe the problem with 2.2.14-5ubuntu8.12
Reading (with cat) from the affected file descriptor (pipe of death) actually
made the parent process stop
https://issues.apache.org/bugzilla/show_bug.cgi?id=53579
Loic Etienne loic.etie...@tech.swisssign.com changed:
What|Removed |Added
CC|
https://issues.apache.org/bugzilla/show_bug.cgi?id=53579
santhosh jacob santhoshmukka...@gmail.com changed:
What|Removed |Added
CC|
https://issues.apache.org/bugzilla/show_bug.cgi?id=53579
--- Comment #6 from george gcm...@gmail.com ---
After looking at the source code and doing some more testing, here are the
results:
-This problem kicks in when the pipe-of-death becomes full (64 kbytes on a
Linux system). When this
https://issues.apache.org/bugzilla/show_bug.cgi?id=53579
--- Comment #5 from george gcm...@gmail.com ---
(In reply to comment #4)
Could reproduce it again. Basically it is writing to the pod (pipe of death)
and is stuck in it forever. All the child processes are in defunct state.
httpd is no
https://issues.apache.org/bugzilla/show_bug.cgi?id=53579
yd yrd...@yahoo.com changed:
What|Removed |Added
Priority|P2 |P1
--
You are receiving
https://issues.apache.org/bugzilla/show_bug.cgi?id=53579
yd yrd...@yahoo.com changed:
What|Removed |Added
Severity|critical|blocker
--- Comment #4 from
https://issues.apache.org/bugzilla/show_bug.cgi?id=53579
--- Comment #3 from yd yrd...@yahoo.com ---
I suspect this has something to do with graceful restart from the logrotate. We
did not see this problem before , but it is more prominent once we started
getting the warning
[warn] (101)Network
https://issues.apache.org/bugzilla/show_bug.cgi?id=53579
--- Comment #2 from yd yrd...@yahoo.com ---
Not very easy to reproduce, happens after around 48 hours of normal testing.
The error log has the following errors.
connect to listener on [::]:443
[Thu Jul 05 00:00:01 2012] [warn] (101)Network
https://issues.apache.org/bugzilla/show_bug.cgi?id=53579
Jeff Trawick traw...@apache.org changed:
What|Removed |Added
OS||All
--- Comment
23 matches
Mail list logo