Package: apache Version: 1.3.33-2 Severity: normal
The last three times I have upgraded apache (to testing), it has failed to come back up after being restarted. Running apache -F shows a segfault. Eventually, I figured out that by removing a bunch of virtual hosts from httpd.conf, I could bring apache back up. The strangest thing is that I could then add those virtual hosts back into httpd.conf, and apache would continue to come up with no problem. This has occurred at least three times now. Unfortunately, I don't have a backtrace from any of the segfaults, and I can't reproduce this problem. But the fact that it's happened more than once, and that it's so bizarre, lead me to think I should report it, just in case the behavior is more widespread, especially with sarge release coming up. If anyone has any clue as to what might explain this behavior, I'd be quite interested. There is nothing nonstandard about this installation; just a small web hosting service running for the most part on Debian testing. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages apache depends on: ii apache-common 1.3.33-2 Support files for all Apache webse ii debconf 1.4.30.10 Debian configuration management sy ii dpkg 1.10.25 Package maintenance system for Deb ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an ii libdb4.2 4.2.52-17 Berkeley v4.2 Database Libraries [ ii libexpat1 1.95.8-1 XML parsing C library - runtime li ii libmagic1 4.10-3 File type determination library us ii logrotate 3.7-2 Log rotation utility ii mime-support 3.28-1 MIME files 'mime.types' & 'mailcap ii perl 5.8.4-3 Larry Wall's Practical Extraction -- debconf information: * apache/enable-suexec: false * apache/server-name: www.bostoncoop.net * apache/document-root: /var/www * apache/server-port: 80 * apache/init: true * apache/server-admin: [EMAIL PROTECTED]
