[bts-link] source package apache2

2013-03-21 Thread bts-link-upstream 
#
# bts-link upstream status pull for source package apache2
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #703252 (http://bugs.debian.org/703252)
# Bug title: apache2-mpm-prefork: exiting prefork child doesn't clear request 
pool, fixed in upstream - see 43857
#  * http://issues.apache.org/bugzilla/show_bug.cgi?id=43857
#  * remote status changed: (?) -> RESOLVED
#  * remote resolution changed: (?) -> FIXED
#  * closed upstream
tags 703252 + fixed-upstream
usertags 703252 + status-RESOLVED resolution-FIXED

thanks


--
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130321164051.1741.9006.btsl...@sonntag.debian.org

Processed: [bts-link] source package apache2

2013-03-21 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package apache2
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #703252 (http://bugs.debian.org/703252)
> # Bug title: apache2-mpm-prefork: exiting prefork child doesn't clear request 
> pool, fixed in upstream - see 43857
> #  * http://issues.apache.org/bugzilla/show_bug.cgi?id=43857
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 703252 + fixed-upstream
Bug #703252 [apache2-mpm-prefork] apache2-mpm-prefork: exiting prefork child 
doesn't clear request pool, fixed in upstream - see 43857
Added tag(s) fixed-upstream.
> usertags 703252 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
703252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.13638840544468.transcr...@bugs.debian.org

Bug#703617: htcacheclean: fails to clean expired entries

2013-03-21 Thread Helmut Grohne 
Package: apache2-utils
Version: 2.2.22-12
Severity: normal

Hi,

I noticed that my mod_disk_cache would grow and don't stop growing. It
was configured for 300M and broke 2GB. Situation did not improve when
running it manually:

# htcacheclean -t -l300M -v -p/var/cache/apache2/mod_disk_cache
Statistics:
size limit 300.0M
total size was 135.7M, total size now 135.7M
total entries was 75460, total entries now 75460
#

At this point the cache was still consuming about 2GB. Looking into the
cache I dug up an example .header file:

000: 0400  c800  4100     A...
010: c15e 39e0 f7d7 0400 4057 9bd4 0cd8 0400  .^9.@W..
020: 529d 38e0 f7d7 0400 c15e 39e0 f7d7 0400  R.8..^9.

The second line contains two apr_time_t (uint64 microseconds since
epoch) values. (Header format is explained in
modules/cache/cache_disk_common.h.) The first one is creation time (Fri
Mar 15 15:58:45 2013) the second one is expiration time (Sat Mar 16
16:58:45 2013). The time of running htcacheclean was about Thu Mar 21
10:00:00 2013. It clearly should have cleaned this file.

So I had a deeper look at the hierarchy. Here is a typical directory:

# ls -lA /var/cache/apache2/mod_disk_cache/d/_
total 40
drwx-- 3 www-data www-data 4096 Mar 12 09:02 
@_f539kGhNQGJ_guMCww.header.vary
drwx-- 3 www-data www-data 4096 Mar 12 09:08 
NQgutNqbacBdUddOpAoQ.header.vary
-rw--- 1 www-data www-data   31 Mar 20 14:10 O8QbyHhBIhMWpZOYfXrQ.header
drwx-- 3 www-data www-data 4096 Mar 20 14:10 
O8QbyHhBIhMWpZOYfXrQ.header.vary
drwx-- 3 www-data www-data 4096 Mar 17 17:19 
uk_qglq66qxl...@waya.header.vary
drwx-- 3 www-data www-data 4096 Mar  1 09:50 
Ubj90WYK54LyPSAfYlsw.header.vary
drwx-- 3 www-data www-data 4096 Mar 11 10:44 
Z7_PZVkqnCk70Do7JECw.header.vary
drwx-- 3 www-data www-data 4096 Mar  4 06:38 
__S2V0aQIdtqX5YEOvIA.header.vary
drwx-- 3 www-data www-data 4096 Mar 19 17:08 
ilyj4...@nva3d2erhza.header.vary
drwx-- 3 www-data www-data 4096 Feb 24 01:41 
oqisphh7jl...@i4m1yg.header.vary
# 

As you can see there are a number of expired (CacheMaxExpire = 1day)
*.header.vary directories and one which is not expired. The one that is
not expired also has a .header file. Presumably the other header files
were cleaned by htcacheclean.

I am not 100% sure that this is not a problem on my behalf, but the data
suggests otherwise at this point. Can you assist me with debugging this
issue? What steps can I try to track down this problem?

Workarounds (besides disabling mod_disk_cache) are welcome.

System information: wheezy i386

Helmut


-- 
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130321112420.ga17...@alf.mars