Bug#557526: apr: segfault in tests on lenny
On Sun, 2009-11-22 at 19:04 +0100, Stefan Fritsch wrote: > On Sunday 22 November 2009, Sam Morris wrote: > > What architecture are you using Sorry about that. Ran reportbug on my desktop, not the server. :) > > This says i386: > > > cd build-i486-linux-gnu/test && ( ulimit -S -s 8192 ; ./testall -v > > testatomic) testatomic : \Line 280: Failed creating > > threads > > //bin/bash: line 1: 7441 Segmentation fault ./testall -v > > testatomic > > > But this says amd64: > > > -- System Information: > > Debian Release: squeeze/sid > > APT prefers testing > > APT policy: (430, 'testing'), (420, 'unstable'), (410, > > 'experimental') Architecture: amd64 (x86_64) > > In any case: Do you have some virtual memory limit per process set (I > think this is often the case on vservers)? If yes, try changing the > 8192 above to 512. Good suggestion. After increasing the virtual memory resource limit (with ulimit -v) the tests passed just fine. Thanks! > > If you have a per user process limit, you may want to increase that, > too. -- Sam Morris https://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 signature.asc Description: This is a digitally signed message part
Bug#557526: apr: segfault in tests on lenny
Package: apr Version: 1.3.8-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When trying to build apr on lenny, I ran into the following: cd build-i486-linux-gnu/test && ( ulimit -S -s 8192 ; ./testall -v testatomic) testatomic : \Line 280: Failed creating threads //bin/bash: line 1: 7441 Segmentation fault ./testall -v testatomic backtrace from gdb: #0 0xb7e94aa7 in pthread_join () from /lib/i686/cmov/libpthread.so.0 #1 0xb7f17f9c in apr_thread_join () from /home/sam/src/apache2/apr-1.3.8/build-i486-linux-gnu/.libs/libapr-1.so.0 #2 0x08066e81 in test_atomics_threaded () #3 0x0804cf50 in abts_run_test () #4 0x080678da in testatomic () #5 0x0804d8ea in main () Not sure why there isn't any source information. - -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (430, 'testing'), (420, 'unstable'), (410, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAksJaf0ACgkQshl/216gEHiFDQCgnnD1YYY+akagV/ramumdE1WW +SwAoIYh8HCxRE7kqvscnyuvecTUS1kH =z0e3 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#525137: apache2.2-common: "could not get next bucket brigade" while a client is doing a PUT results in data loss
Package: apache2.2-common Version: 2.2.9-10+lenny2 Severity: grave Justification: causes data loss I've got a bunch of calendar clients configured to download and upload icalendar files to a web location backed by mod_dav. Occasionally there will be an error when one client is uploading the calendar file, which cases the file to be deleted: 10.0.0.1 alice [22/Apr/2009:13:42:12 +0100] "GET /cal/bob HTTP/1.1" 200 20480 text/calendar "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.21) Gecko/20090302 Lightning/0.9 Thunderbird/2.0.0.21" 10.0.0.1 alice [22/Apr/2009:13:39:51 +0100] "PUT /cal/bob HTTP/1.1" 500 390 text/html "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.21) Gecko/20090302 Lightning/0.9 Thunderbird/2.0.0.21" 10.0.0.1 bob [22/Apr/2009:13:44:54 +0100] "GET /cal/bob HTTP/1.1" 404 289 text/html "-" "Evolution/2.24.5" Unfortunately, the only message that appears in the error log file is the mysterious message: [Wed Apr 22 13:44:53 2009] [error] [client 10.0.0.1] Could not get next bucket brigade [500, #0] IMO, mod_dav should replace files not by truncating them, but by writing out a temporary file and then renaming it over the original file. That way, files can be replaced atomically, and so the failure to write the file does not result in the loss of the data. Unfortunately I have no way to reproduce this problem on demand. From my recollection, it seems to happen about once every two months. I am erring on the side of cauting WRT the bug severity, please feel free to downgrade if you disagree. -- Package-specific info: Loaded Modules: core_module (static) log_config_module (static) logio_module (static) mpm_worker_module (static) http_module (static) so_module (static) actions_module (shared) alias_module (shared) auth_basic_module (shared) authn_file_module (shared) authz_default_module (shared) authz_groupfile_module (shared) authz_host_module (shared) authz_user_module (shared) autoindex_module (shared) cgid_module (shared) dav_module (shared) dav_fs_module (shared) deflate_module (shared) dir_module (shared) env_module (shared) expires_module (shared) fcgid_module (shared) headers_module (shared) mime_module (shared) negotiation_module (shared) perl_module (shared) python_module (shared) rewrite_module (shared) setenvif_module (shared) ssl_module (shared) status_module (shared) suexec_module (shared) userdir_module (shared) Syntax OK -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#92052: Present in apache 2 & workaround
clone 92052 -1
reassign -1 apache2
found -1 2.2.3-4
thanks
Ideally a granular (at least per-vhost) option to enable or disable this
feature would be useful--I would like to allow certain (fast)cgi scripts
the ability to process HTTP authentication, but I don't want others
having access to the usernames/passwords that my users authenticate
with.
The following mod_rewrite rules implement a workaround:
RewriteCond %{HTTP:Authorization} (.*)
RewriteRule . - [env=HTTP_AUTHORIZATION:%1]
These directives are granular down to the directory/.htaccess level. :)
--
Sam Morris
http://robots.org.uk/
PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
signature.asc
Description: This is a digitally signed message part
Bug#461917: Apache 2.2 TLS-SNI support
On Wed, 2008-04-23 at 20:27 +0200, Stefan Fritsch wrote: > On Wednesday 23 April 2008, Raphaël Rigo wrote: > > is there any chance this feature would make it for lenny's final > > release ? > > The current version of the SNI patch has problems (including a > security issue). Details please? I haven't received anything from upstream's bugzilla... -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 signature.asc Description: This is a digitally signed message part
Bug#461917: Apache 2.2 TLS-SNI support
FYI, OpenSSL in lenny now has TLSEXT enabled. -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 signature.asc Description: This is a digitally signed message part
Bug#469145: apache2-doc: ships empty /var/www/apache2-default
Package: apache2-doc Version: 2.2.8-1 Severity: minor The apache2-doc package still seems to ship an empty /var/www/apache2-default directory. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (520, 'testing'), (510, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#314606: consider moving NameVirtualHost option
I usually move this to /etc/apache2/ports.conf. Another alternative would be /etc/apache2/vhost.conf, along with the addition of another Include directive to /etc/apache2/apache2.conf. -- Sam Morris <[EMAIL PROTECTED]> signature.asc Description: This is a digitally signed message part
Bug#434248: apache2.2-common: TypesConfig could be moved from apache2.conf to mods-available/mime.conf
Package: apache2.2-common Version: 2.2.4-2 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The new cleaned up apache2.conf is really nice! I noticed that it still has a TypesConfig directive. Apparently, this directive is provided by mod_mime, so it too could be moved to /etc/apache2/conf.d/mime.conf. - -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.21-2-k7 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages apache2.2-common depends on: ii apache2- 2.2.3-5 utility programs for webservers ii libapr1 1.2.7-8.2 The Apache Portable Runtime Librar ii libaprut 1.2.7+dfsg-2+b1 The Apache Portable Runtime Utilit ii libc62.6-2 GNU C Library: Shared libraries ii libdb4.4 4.4.20-8Berkeley v4.4 Database Libraries [ ii libexpat 1.95.8-3.4 XML parsing C library - runtime li ii libldap2 2.1.30-13.4 OpenLDAP libraries ii libmagic 4.21-1 File type determination library us ii libpcre3 6.7-1 Perl 5 Compatible Regular Expressi ii libpq5 8.2.4-2 PostgreSQL C client library ii libsqlit 3.3.17-1SQLite 3 shared library ii libssl0. 0.9.8e-5SSL shared libraries ii libuuid1 1.39+1.40-WIP-2006.11.14+dfsg-2 universally unique id library ii lsb-base 3.1-23.1Linux Standard Base 3.1 init scrip ii mime-sup 3.39-1 MIME files 'mime.types' & 'mailcap ii net-tool 1.60-17 The NET-3 networking toolkit ii procps 1:3.2.7-3 /proc file system utilities ii zlib1g 1:1.2.3.3.dfsg-5compression library - runtime apache2.2-common recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGo3lxshl/216gEHgRAk/jAKCLuPTsiwQV+im81NzqqdFVi3oyXgCfUkpb DOZzeA7srfseiALfmHT0iWo= =rwLD -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428058: apache2.2-common: a2enmod's cgi/cgid cleverness does not work with apache2-mpm-itk
Package: apache2.2-common Version: 2.2.3-4 Severity: normal The logic that a2enmod uses to decide whether to replace 'cgi' with 'cgid' is not sufficient to handle cases where the MPM in use is prefork-based, but is not actually named prefork.c. With the ITK MPM, 'apache2 -l' outputs 'itk.c'. Ok, so a2enmod can't be expected to recognise the name of every alternative MPM in use; but it should at least print something out to stderr like this: You do not appear to be using the preform MPM. Replacing mod_cgi with mod_cgid. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (540, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages apache2.2-common depends on: ii apache2-utils2.2.3-4 utility programs for webservers ii libmagic14.17-5etch1 File type determination library us ii lsb-base 3.1-23.1Linux Standard Base 3.1 init scrip ii mime-support 3.39-1 MIME files 'mime.types' & 'mailcap ii net-tools1.60-17 The NET-3 networking toolkit ii procps 1:3.2.7-3 /proc file system utilities apache2.2-common recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#394462: apache2: Obsolete 000-default symlink not removed on upgrade
Package: apache2 Version: 2.2.3-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Having upgraded to Apache 2.2, I was left with two symlinks left in /etc/apache2/sites-enabled: lrwxrwxrwx 1 root root 36 2006-10-21 12:51 000-default -> /etc/apache2/sites-available/default lrwxrwxrwx 1 root root 36 2006-02-08 21:23 default -> /etc/apache2/sites-available/default Running 'a2dissite default' left me with the 000-default symlink, so it appears that the name of the symlink for the default site is no longer special-cased to start with '000-'. If this is the case, then the old symlink is cruft and should be removed when upgrading to Apache 2.2. - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-k7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages apache2 depends on: ii apache2-mpm-worker2.2.3-2High speed threaded model for Apac apache2 recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFOg7dshl/216gEHgRAp2hAJ4svul/HM5+ZiZi+8aMjC6TUVqqswCg0CEQ AHW3EE4L867W+e8LVhmZwQA= =HJW6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374679: apache2: Crashes when VirtualHosts are missing from the config file
Package: apache2 Version: 2.0.54-5 Severity: important While configuring a server I found that apache will crash if a NameVirtualHost directive exists for a port and there are no VirtualHost entries that match that port. $ apache2 -f crash.conf -X & [1] 25146 apache2: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName apache2: Could not determine the server's fully qualified domain name, using 127.0.1.1 for ServerName [Tue Jun 20 16:54:22 2006] [warn] pid file /dev/null overwritten -- Unclean shutdown of previous Apache run? $ GET http://localhost:8123/ 500 Server closed connection without sending any data back [1]+ Segmentation fault apache2 -f crash.conf -X Contents of crash.conf: Listen 8123 NameVirtualHost *:8123 ErrorLog /dev/stdout TypesConfig /etc/mime.types PidFile /dev/null -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-k7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages apache2 depends on: ii apache2-mpm-worker2.0.55-4 high speed threaded model for Apac apache2 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
