https://bz.apache.org/bugzilla/show_bug.cgi?id=61485
--- Comment #8 from Luca Toscano <toscano.l...@gmail.com> --- (In reply to sgiraud from comment #7) > Maybe I may add the FB option in order to use completely this module, this > may solve this bug. What is your point of view about this ? I think that it will not solve the issue, mod_logio collects the data anyway, I think that you are hitting a corner case in which the module dereference a null pointer or something similar (but for the moment it is only a speculation). I checked https://github.com/apache/httpd/commits/trunk/modules/loggers/mod_logio.c and I don't see any recent fix for any segfault report, so it might still be an issue with 2.4.x recent versions. > > About the core it will need somme time to reproduce the behaviour. > In produciton context, this bug is reproduced only every 2 month without > apache restart. Another team will build a test environnement in order to > reproduce the behaviour as quickly as possible. > > About the behaviour, I haven't noticed a particular request making this > segfault. It is reproduced on several differents website (3 drupal > websites). > > We have a distributed infrastructure composed of 3 apache. When a segfault > appear on a first apache, approximately 24h after, the two other apache have > the same behaviour. When the segfault appear some static webpages are > already served (GET /). But when the first segfault appear all child are > exit on segfault signal. Thanks, let's wait the coredump then :) -- 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
