https://bz.apache.org/bugzilla/show_bug.cgi?id=58524
--- Comment #5 from Cedric Roijakkers <cedric.roijakk...@qnh.nl> --- Hi, I have applied your patch on one production server and left it running there for some time. I'm now getting less error logging, but still the occasional segfault: [Tue Oct 27 14:13:08.126175 2015] [core:notice] [pid 26297:tid 47021196566720] AH00052: child pid 26583 exit signal Segmentation fault (11) [Tue Oct 27 14:13:54.135349 2015] [core:notice] [pid 26297:tid 47021196566720] AH00052: child pid 26305 exit signal Segmentation fault (11) Is there any logging that I can switch on that would help you? Interestingly enough, I still see lots of connections stuck in CLOSE_WAIT while the mod_http2 is running. On the other production servers, at the same time, there are around 10-15 connections in CLOSE_WAIT, with mod_http2 enabled the value hangs between 200 and 300, which still indicates something wrong. The reason why we have so many would probably be because our setup includes a lot of mod_proxy usage, we proxy to varnish, which proxies back to apache after applying caching. For a subset of calls, we then later proxy to Tomcat, so there is quite a lot of proxying going on, and when a process dies, I can imagine the connection stays open in CLOSE_WAIT. Restarting apache immediately closes all the CLOSE_WAIT connections. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
