[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: apt-cacher transition from apache to apache2



On Monday 08 November 2004 08:47, martin f krafft wrote:
> also sprach Alexandros Papadopoulos <apapadop@alumni.carnegiemellon.edu> [2004.11.08.0734 +0100]:
> > changing /etc/apt-cacher/apt-cacher.conf and then
> > reloading/restarting apache2 does not honor the changes.
>
> Well, you should not need to restart apache2 since apt-cacher is
> a CGI. Apparently, apache2 loads it permanently though, which is
> news to me.
>
> Does it work at all?

Apparently not. After apt-get removing apt-cacher and re-installing it (to force it to run its install scripts, in hopes that that would fix the problem), it's not working at all.

> > I think it has something to do with the
> > /etc/apt-cacher/apache.conf snippet which I need to install
> > somewhere, but I have no idea where.
>
> Leave it right there and 'include' it from the vhost definition.

There's this already:
helios:/etc/apache2/conf.d# ls -l apt*
lrwxrwxrwx  1 root root 27 Nov  8 08:51 apt-cacher -> /etc/apt-cacher/apache.conf

Does that mean it's included? Since I'm just running an internal website on this, I've never invested the time/effort to (figure out how to) set up virtual hosts or include cgi scripts.

This is what happens on the apt-cacher server when a request to apt-get update comes in from a client:
 1612 ?        Ss     0:00 /usr/sbin/apache2 -k start -DSSL
 1613 ?        S      0:00  \_ /usr/sbin/apache2 -k start -DSSL
 1641 ?        S      0:00  |   \_ /usr/bin/perl /usr/share/apt-cacher/apt-cacher.pl
 1642 ?        S      0:00  |       \_ /usr/bin/perl /usr/share/apt-cacher/apt-cacher.pl
 1643 ?        S      0:00  |           \_ /usr/bin/perl /usr/share/apt-cacher/apt-cacher.pl
 1644 ?        S      0:00  |               \_ /usr/bin/wget -s -nv  -o /var/cache/apt-cacher/private/ftp.ntua.gr_[...]

apt-cacher reports the following:
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: client ipint: 3232235844
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: allowed_startip: 192.168.1.1
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: allowed_endip: 192.168.1.254
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: allowed_startipint: 3232235777
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: allowed_endipint: 3232236030
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: Client passed access control rules 192.168.1.68
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: called with /ftp.ntua.gr/pub/linux/debian/dists/testing/main/binary-i386/Packages.gz
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: new long filename: ftp.ntua.gr_pub_linux_debian_dists_testing_main_binary-i386_Packages.gz
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: cached file: /var/cache/apt-cacher/ftp.ntua.gr_pub_linux_debian_dists_testing_main_binary-i386_Packages.gz
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: looking for /var/cache/apt-cacher/ftp.ntua.gr_pub_linux_debian_dists_testing_main_binary-i386_Packages.gz
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: filename complies: Packages.gz
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: file does not exist, creating it
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: MISS
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: file is not complete
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: fetcher: try to pick up http://ftp.ntua.gr/pub/linux/debian/dists/testing/main/binary-i386/Packages.gz
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: fork complete 0
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: starting to return /var/cache/apt-cacher/ftp.ntua.gr_pub_linux_debian_dists_testing_main_binary-i386_Packages.gz
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: read 0 bytes
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: fork complete 1690
Mon Nov  8 09:39:17 2004|192.168.1.68|debug: parent about to wait, child pid is -1690- 1
Mon Nov  8 09:39:19 2004|192.168.1.68|debug: read 0 bytes
Mon Nov  8 09:39:21 2004|192.168.1.68|debug: read 0 bytes
Mon Nov  8 09:39:23 2004|192.168.1.68|debug: read 0 bytes
Mon Nov  8 09:39:25 2004|192.168.1.68|debug: read 0 bytes
[ad infinitum]

So it seems the cgi is called, but then something (?) goes wrong...

-A



Reply to: