I would have wanted to provide the full chain of the reproducer, but days has already passed, here is the information i can provide for now:
I reproduce the crash with a simple: rm failed; for i in $(seq 200); do (curl -qo /dev/null "$URL" || touch failed) & done A single run usually is enough, rarely two. In addition to the curl failure and 'failed' file, there's a error line in Apache's error.log I used the attached script for the consistency checks, tried with and without the sleep. I run all of thoses with our closed source daemon as the backend behind fastcgi with the following directive parameters: FastCgiExternalServer /var/www/proxy -host 127.0.0.1:10000 -flush -idle-timeout 300 So you should be able to reproduce if you have some kind of stub behind fastcgi, which you maybe already have ? ** Attachment added: "apache-client.sh" https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1630413/+attachment/4944614/+files/apache-client.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630413 Title: segfault in server/mpm/event/event.c:process_socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1630413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
