Bug 1215192

Summary: random segfaults with worker MPM
Product: Red Hat Software Collections Reporter: Martin Frodl <mfrodl>
Component: mod_perlAssignee: perl-maint-list
Status: CLOSED ERRATA QA Contact: Martin Kyral <mkyral>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rh-perl524CC: jplesnik, kanderso
Target Milestone: rc   
Target Release: 2.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rh-perl524-mod_perl-2.0.9-6.el6 rh-perl524-mod_perl-2.0.9-6.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-15 10:05:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
valgrind output none

Description Martin Frodl 2015-04-24 14:15:34 UTC 
Perhaps the same issue as bug 1199779.

Description of problem:

When httpd MPM worker is running with mod_perl enabled, some of the worker processes segfault randomly.

How reproducible:
Sometimes. I ran into this behaviour on several systems, but was not able to reproduce it on others.

Steps to Reproduce:
# echo LoadModule mpm_worker_module modules/mod_mpm_worker.so > /opt/rh/httpd24/root/etc/httpd/conf.modules.d/00-mpm.conf
# service httpd24-httpd restart
Stopping httpd: [  OK  ]
Starting httpd: [  OK  ]
# ab -c 100 -n 50000 http://127.0.0.1/
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking 127.0.0.1 (be patient)
Completed 5000 requests
Completed 10000 requests
Completed 15000 requests
Completed 20000 requests
Completed 25000 requests
Completed 30000 requests
apr_socket_recv: Connection reset by peer (104)
Total of 31218 requests completed
# tail -5 /var/log/httpd24/error_log 
[Fri Apr 24 09:54:30.340402 2015] [autoindex:error] [pid 21366:tid 140616289744640] [client 127.0.0.1:40363] AH01276: Cannot serve directory /opt/rh/httpd24/root/var/www/html/: No matching DirectoryIndex (index.html) found, and server-generated directory index forbidden by Options directive
[Fri Apr 24 09:54:30.340429 2015] [autoindex:error] [pid 21367:tid 140616174356224] [client 127.0.0.1:40364] AH01276: Cannot serve directory /opt/rh/httpd24/root/var/www/html/: No matching DirectoryIndex (index.html) found, and server-generated directory index forbidden by Options directive
[Fri Apr 24 09:54:30.340726 2015] [autoindex:error] [pid 21455:tid 140616090437376] [client 127.0.0.1:40365] AH01276: Cannot serve directory /opt/rh/httpd24/root/var/www/html/: No matching DirectoryIndex (index.html) found, and server-generated directory index forbidden by Options directive
[Fri Apr 24 09:55:10.339283 2015] [autoindex:error] [pid 21366:tid 140616268764928] [client 127.0.0.1:40387] AH01276: Cannot serve directory /opt/rh/httpd24/root/var/www/html/: No matching DirectoryIndex (index.html) found, and server-generated directory index forbidden by Options directive
[Fri Apr 24 09:54:30.764111 2015] [core:notice] [pid 21363:tid 140616681404384] AH00052: child pid 21368 exit signal Segmentation fault (11)

Version-Release number of selected component (if applicable):
rh-perl520-mod_perl-2.0.8-8.20150122svn1653807.el6.x86_64
httpd24-httpd-2.4.12-3.el6.x86_64
Comment 2 Jan Kaluža 2015-04-24 14:42:26 UTC 
I'm not able to reproduce this bug so far. Can you get coredump from the crash? Set CoreDumpDirectory to some directory writable by apache:apache and reproduce the bug.

http://httpd.apache.org/docs/current/mod/mpm_common.html#coredumpdirectory
Comment 4 Jan Kaluža 2015-04-27 07:49:07 UTC 
Created attachment 1019262 [details]
valgrind output
Comment 5 Jan Kaluža 2015-04-28 06:54:02 UTC 
Fix committed upstream:

http://svn.apache.org/viewvc?view=revision&revision=1676417
Comment 10 errata-xmlrpc 2016-11-15 10:05:00 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2729.html