net-www/apache-2.0.54-r30 (+apache2 +mpm-peruser +ssl) segfaults repeatedly at startup and fails to service any requests. The listening port is opened, but apache seems to segfault when trying to spawn a child process to handle any incoming requests, any connection to the apache listening port seems to just hang. Reproducible: Always Steps to Reproduce: 1. USE="mpm-peruser" emerge apache 2. configure the peruser section of httpd.conf adding a couple of users 3. add a couple of vhosts in /etc/apache2/vhosts.d/ and configure peruser to use a seperate userid for each 4. start apache 5. tail -f /var/log/apache2/error_log Actual Results: error_log reports: [Tue Sep 13 10:12:31 2005] [notice] child pid 31595 exit signal Segmentation fault (11), possible coredump in /usr/lib/apache2 repeatedly This happens on both alpha and sparc but not on x86, i`m not sure how to flag it as an issue for 2 architectures (the only option presented is all) Expected Results: Apache should start and accept requests normally. gdb stacktrace: (gdb) bt #0 0x00000200004234e4 in apr_os_sock_put () from /usr/lib/libapr-0.so.0 #1 0x0000000120029704 in cleanup_server_environments () #2 0x000000012002b1a4 in cleanup_server_environments () #3 0x000000012002b82c in ap_mpm_run () #4 0x0000000120036b40 in main () emerge info: Portage 2.0.51.22-r2 (default-linux/alpha/2005.0, gcc-3.4.4, glibc-2.3.5-r1, 2.6.12 alpha) ================================================================= System uname: 2.6.12 alpha EV6 Gentoo Base System version 1.12.0_pre6 dev-lang/python: 2.3.5, 2.4.1-r1 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.8.1-r4 ACCEPT_KEYWORDS="alpha ~alpha" AUTOCLEAN="yes" CBUILD="alpha-unknown-linux-gnu" CFLAGS="-O3 -mcpu=ev6 -fomit-frame-pointer -pipe" CHOST="alpha-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O3 -mcpu=ev6 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.blueyonder.co.uk/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://192.168.100.1/gentoo-portage" USE="alpha 16bit X a52 aac apache2 arts berkdb bitmap-fonts cdparanoia cdr crypt cups curl dlloader dts dvd dvdr dvdread eds encode ev6 fam flac flash font-server foomaticdb fortran gdbm gif gnome gnutls gpm gstreamer gtk gtk2 imagemagick imlib insecure-drivers ithreads jpeg kde libg++ libwww mad mikmod motif mozilla mozsvg mp3 mpeg mpm-peruser ncurses nls ogg oggvorbis opengl oss pam pam_chroot pdflib perl png python qt quicktime readline samba sdl slang spell ssl tetex theora tiff truetype truetype-fonts type1-fonts vorbis xine xml2 xmms xprint xv xvid zaptel zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Ahem... ebuild snip: <snip> ewarn " -BIG- -FAT- -WARNING-" ewarn "" ewarn "The peruser (USE=mpm-peruser) MPM is considered highly experimental" ewarn "and are not (yet) supported, nor are they recommended for production" ewarn "use. You have been warned!" ewarn ewarn "Continuing in 5 seconds.." </snip>
If it's known to be broken for certain archs, that use-flag should be masked for that arch. sparc and alpha teams: I'm not sure what the procedure for that is, please determine if you want to use-mask this.
Normal procedure is what you did, ask us to test it and act accordingly. mpm-peruser appears to be broken on sparc so I've masked the use flag in the SPARC profiles.
Created attachment 69012 [details, diff] Patch to correct mpm-peruser on alpha This patch corrects mpm-peruser on alpha.. the following urls are running this patch on an alpha: http://tw1.ev6.net/test.php http://tw2.ev6.net/test.php http://tw3.ev6.net/test.php http://tw4.ev6.net/test.php
I masked mpm-peruser on alpha until I can test the patch properly. Hopefully that won't be too long as I quite like the idea of peruser :)
Apache 2.0.58 has a new version of the mpm-peruser patch (version 0.2.0). Perhaps it is time to do additional testing and see if the issues from before are resolved?
(In reply to comment #6) > Apache 2.0.58 has a new version of the mpm-peruser patch (version 0.2.0). > Perhaps it is time to do additional testing and see if the issues from before > are resolved? > I have tested mpm-peruser 0.2.0 with Apache 2.0.55 and had the same problem, the patch I proposed still applies to 0.2.0 however, and still corrects the problem on Alpha and Sparc. I also heard that AMD64 suffers the same problem, and is also corrected by my patch, but i've not verified this myself.
(In reply to comment #7) > (In reply to comment #6) > > Apache 2.0.58 has a new version of the mpm-peruser patch (version 0.2.0). > > Perhaps it is time to do additional testing and see if the issues from before > > are resolved? > > > > I have tested mpm-peruser 0.2.0 with Apache 2.0.55 and had the same problem, > the patch I proposed still applies to 0.2.0 however, and still corrects the > problem on Alpha and Sparc. > > I also heard that AMD64 suffers the same problem, and is also corrected by my > patch, but i've not verified this myself. Is this still an issue with current (>=net-www/apache-2.0.58-r2) ?
