Created attachment 520390 [details]
Description of problem:
mod_auth_kerb doesn't work properly with worker MPM.
There are the following errors in the log (please find whole error_log attached):
[Mon Aug 29 08:23:55 2011] [notice] child pid 12884 exit signal Bus error (7)
[Mon Aug 29 08:23:57 2011] [notice] child pid 12938 exit signal Segmentation fault (11)
[Mon Aug 29 08:24:02 2011] [notice] child pid 12968 exit signal Segmentation fault (11)
[Mon Aug 29 08:24:03 2011] [notice] child pid 12970 exit signal Segmentation fault (11)
*** glibc detected *** /usr/sbin/httpd.worker: double free or corruption (fasttop): 0x00002aaabc000fe0 ***
======= Backtrace: =========
======= Memory map: ========
Version-Release number of selected component (if applicable):
MPM worker, mod_auth_kerb authentication with "KrbMethodK5Passwd on".
ab -n 1000 -c 100 -A username:password http://hostname/
Lot of "Failed requests" in the ab's output. Server error_log is full of errors.
If user try to open real page (with images, styles etc.) in browser, it looks broken - lot of images are missing etc.
No failed requests. No errors in the error_log.
It seems to be fixed in upstream since Oct 2 2008:
Hi, any progress with this issue? It's a blocker for us.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
The mod_auth_kerb module did not use the Kerberos libraries in a thread-safe way. Therefore, if mod_auth_kerb ran under a multi-threaded Apache HTTP Server, authentication requests could terminate unexpectedly with a segmentation fault. With this update, the thread-safety problem has been fixed, and thread crashes no longer occur under these circumstances.
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.