There is one remaining compile-time if-branch, which is not about database access 
though. It takes care of choosing %/d%lld as format string for (potentially) large 
integers in the SQL query (the one that retrieves hashes).  apr-1.2 knew only %d, 
while apr-1.3 knows %lld for 64-bit integers. 


#if (APR_MAJOR_VERSION == 1 && APR_MINOR_VERSION == 2)
#define DBD_LLD_FMT "d"
#else
#define DBD_LLD_FMT "lld"
#endif

I'm leaving that as is, since the consequences are much less relevant (if it 
results in breakage at all). Hence, I close this issue as resolved.

mod_mirrorbrain now has the same fix (r8107).
http://svn.mirrorbrain.org/viewvc/mirrorbrain?view=revision&revision=8107

mod_asn got a fix for this now (r86).
http://svn.mirrorbrain.org/viewvc/mod_asn?view=revision&revision=86

The check could be done at runtime, rather than at compile time.

That would protect the user in scenarios where a wrong package is installed (one 
that is compiled against a different APR version that what the system has).

There is apr_version() which returns the runtime APR version. See apr_version.h.

Apache uses it:
 # httpd2 -V | grep "APR "
Server loaded:  APR 1.4.2, APR-Util 1.3.9
Compiled using: APR 1.4.2, APR-Util 1.3.9

It would also allow us to log the versions to the error log at Apache's start.

See also issue 29.

Fixed in trunk:
http://svn.mirrorbrain.org/viewvc/mirrorbrain/trunk/mod_mirrorbrain/mod_mirrorbrai
n.c?r1=7887&r2=7886&pathrev=7887

Will be in the next release.

After sugarlabs is running with the fix for a month already, I think we can close 
this as fixed. 

And since it is easy to do compile time detection of the APR version, I'll commit 
a fix that does just that, so we can drop the patch from the Debian and Ubuntu 
packages.

The packages with the fix are scheduled to be built in the openSUSE build service. They might 
turn up later today, but as the build service is extremely slow currently, I have put manually 
built packages here:

http://www.poeml.de/~poeml/DEBS/

I'm adding the proposed fix to the Ubuntu/Debian packages.

I have not learnt yet how to properly add the change as patch when packaging Debian packages in the openSUSE build 
service, but a simple & stupid

    sed -i 's/&row, i);$$/\&row, i-1);/' mod_mirrorbrain.c

in the debian/rules file has the desired effect at the moment. Not nice, but for pragmatical reasons (also because 
I'll be away for vacation for a while) I'm fixing it this way now.

The following patch seemingly makes mod_mirrorbrain work with the old libaprutil:


--- mod_mirrorbrain.c   (revision 7798)
+++ mod_mirrorbrain.c   (working copy)
@@ -1127,7 +1127,7 @@
         const char *val = NULL;
         short col = 0; /* incremented for the column we are reading out */

-        rv = apr_dbd_get_row(dbd->driver, r->pool, res, &row, i);
+        rv = apr_dbd_get_row(dbd->driver, r->pool, res, &row, i-1);
         if (rv != 0) {
             ap_log_rerror(APLOG_MARK, APLOG_ERR, rv, r,
                       "[mod_mirrorbrain] Error looking up %s in database", filename);


I think we can quite easily change mod_mirrorbrain to work with both APR versions, 
either by detecting the APR version at build time, or by adding the patch to the Ubuntu
packages.

I don't know whether this fix works _well_, I can't really promise that at the 
moment, without looking into the database adapter (and its changelog) 
again.

> the next issues....
> I am getting the following error report when trying to download

Ah. Interesting one.

> -----------------------
> [Tue Oct 06 11:53:46 2009] [warn] [client 96.42.62.145] [mod_mirrorbrain] MirrorBrainEngine On, 
mirror_base '/var/www/downloads/', referer: http://mirrorbrain-
testing.sugarlabs.org/sources/honey/InfoSlicer/
> [Tue Oct 06 11:53:46 2009] [warn] [client 96.42.62.145] [mod_mirrorbrain] URI: 
'/sources/honey/InfoSlicer/InfoSlicer-4.tar.bz2', referer: http://mirrorbrain-
testing.sugarlabs.org/sources/honey/InfoSlicer/
> [Tue Oct 06 11:53:46 2009] [warn] [client 96.42.62.145] [mod_mirrorbrain] filename: 
'/var/www/downloads/sources/honey/InfoSlicer/InfoSlicer-4.tar.bz2', referer: http://mirrorbrain-
testing.sugarlabs.org/sources/honey/InfoSlicer/
> [Tue Oct 06 11:53:46 2009] [error] [client 96.42.62.145] [mod_mirrorbrain] could not resolve continent, 
referer: http://mirrorbrain-testing.sugarlabs.org/sources/honey/InfoSlicer/
> [Tue Oct 06 11:53:46 2009] [warn] [client 96.42.62.145] [mod_mirrorbrain] Country 'US', Continent '--', 
referer: http://mirrorbrain-testing.sugarlabs.org/sources/honey/InfoSlicer/
> [Tue Oct 06 11:53:46 2009] [warn] [client 96.42.62.145] [mod_mirrorbrain] AS '--', Prefix '--', referer: 
http://mirrorbrain-testing.sugarlabs.org/sources/honey/InfoSlicer/
> [Tue Oct 06 11:53:46 2009] [warn] [client 96.42.62.145] [mod_mirrorbrain] Successfully acquired database 
connection., referer: http://mirrorbrain-testing.sugarlabs.org/sources/honey/InfoSlicer/
> [Tue Oct 06 11:53:46 2009] [warn] [client 96.42.62.145] [mod_mirrorbrain] SQL lookup for (canonicalized) 
'sources/honey/InfoSlicer/InfoSlicer-4.tar.bz2', referer: http://mirrorbrain-
testing.sugarlabs.org/sources/honey/InfoSlicer/
> [Tue Oct 06 11:53:46 2009] [warn] [client 96.42.62.145] [mod_mirrorbrain] Found 2 mirrors, referer: 
http://mirrorbrain-testing.sugarlabs.org/sources/honey/InfoSlicer/

Apache successcully connects and talks to the database, and it does find the file on two
mirrors. That's great, and everything should work but...

> [Tue Oct 06 11:53:46 2009] [error] [client 96.42.62.145] (-1)Unknown error 18446744073709551615: 
[mod_mirrorbrain] Error looking up sources/honey/InfoSlicer/InfoSlicer-4.tar.bz2 in database, referer: 
http://mirrorbrain-testing.sugarlabs.org/sources/honey/InfoSlicer/

...something else seems wrong, and I'm quite puzzled by this one.

In fact, after reading mod_mirrorbrain.c back and forth I'm quite sure
that this means that reading result lines from the database query fails.

The module correctly gets (and logs) the number of rows in the result,
but iterating over the result set fails (apr_dbd_get_row() call).

I suspect that the Apache Portable Runtime version of Ubuntu 9.04, and
the shipped PostgreSQL database adapter are a little bit too old (or
missing a bug fix) so it results in different behaviour.


Yes, this is probably the reason. On my Ubuntu 9.04 system I see a
libaprutil1 package with version 1.2.12, and in the ChangeLog I see:

- update to 1.3.0
[...]
  * ) All DBD drivers now count rows from 1, which affects PostgreSQL and MySQL
    drivers in particular. Using row number zero is an error.
    [Bojan Smojver]

That would explain the error.

I can probably come up with a workaround. Sorry about the inconvenience...