Re: Problem with apt maybe related to installation/configuration of apt-cacher-ng

[Dennis Heddicke]

On 5/31/23 14:42, john doe wrote:

On 5/31/23 11:36, Dennis Heddicke wrote:

Yes, after purging apt-cacher-ng the problem was gone. And after i
reinstalled apt-cacher-ng and configured it that way:



For the sake of simplicity and troubleshooting, please modify
sources.list directly.

What does acng.conf look like?


Note that this list uses bottom-posting! :)

--
John Doe



Sorry, that it was confusing. I meant, that there are no erros. It works 
fine.


The sample:

sudo apt update
[sudo] password for dennis:
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://security.debian.org/debian-security bookworm-security 
InRelease

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

And i will try to change the URL for https later, but the problem is 
solved so far.

Re: Problem with apt maybe related to installation/configuration of apt-cacher-ng

[john doe]

On 5/31/23 11:36, Dennis Heddicke wrote:

Yes, after purging apt-cacher-ng the problem was gone. And after i
reinstalled apt-cacher-ng and configured it that way:



For the sake of simplicity and troubleshooting, please modify
sources.list directly.

What does acng.conf look like?


Note that this list uses bottom-posting! :)

--
John Doe

Re: Problem with apt maybe related to installation/configuration of apt-cacher-ng

[Charles Curley]

On Wed, 31 May 2023 11:36:19 +0200
Dennis Heddicke  wrote:

> Acquire::http {Proxy "http://localhost:3142";};
> Acquire::https {Proxy "http://";};

I'm not comfortable with your second line there. First, you have for
https a non-secure http. I suspect they should match. Second, if you
are going to use hhtps, give the complete URL. Like so:

Acquire::https {Proxy "https://localhost:3142";};

But I don't think that's part of your problem.

For what it's worth, my configuration for ACN looks like:

root@chaffee:~# cat /etc/apt/apt.conf.d/02proxy 
Acquire::http::Proxy "http://aptcacherdeb.localdomain:3142";;
Acquire::https::Proxy "https://aptcacherdeb.localdomain:3142";;
root@chaffee:~# 



> 
> there are any errors too, although i don't know what  caused them.
> But thank you for your help.

I'm confused: are there errors or are there no errors? If there are
errors, please show a sample.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: Problem with apt maybe related to installation/configuration of apt-cacher-ng

[Dennis Heddicke]

Yes, after purging apt-cacher-ng the problem was gone. And after i 
reinstalled apt-cacher-ng and configured it that way:


Acquire::http {Proxy "http://localhost:3142";};
Acquire::https {Proxy "http://";};

there are any errors too, although i don't know what  caused them. But 
thank you for your help.


On 5/31/23 08:43, john doe wrote:

On 5/30/23 19:39, Dennis Heddicke wrote:

Hello,

i have a problem with "apt update", everytime i execute the command, i
get the following error messages:

Get:1 http://security.debian.org/debian-security bookworm-security
InRelease [48,0 kB]
Get:2 http://deb.debian.org/debian bookworm InRelease [193 kB]
Err:1 http://security.debian.org/debian-security bookworm-security
InRelease
  The following signatures were invalid: BADSIG 112695A0E562B32A Debian
Security Archive Automatic Signing Key (10/buster) 


Err:2 http://deb.debian.org/debian bookworm InRelease
  The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian
Archive Automatic Signing Key (10/buster) 
Fetched 241 kB in 0s (507 kB/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository
is not updated and the previous index files will be used.
GPG error: http://security.debian.org/debian-security bookworm-security
InRelease: The following signatures were invalid:
BADSIG 112695A0E562B32A Debian Security Archive Automatic Signing Key
(10/buster) 
W: An error occurred during the signature verification. The repository
is not updated and the previous index files will be used.
GPG error: http://deb.debian.org/debian bookworm InRelease: The
following signatures were invalid: BADSIG 648ACFD622F3D
138 Debian Archive Automatic Signing Key (10/buster) 


W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease
  The following signatures were invalid: BADSIG 648ACFD622F3D138
Debian Archive Automatic Signing Key (10/buster) 
W: Failed to fetch
http://security.debian.org/debian-security/dists/bookworm-security/InRelease 
 The following signatures were invalid:

BADSIG 112695A0E562B32A Debian Security Archive Automatic Signing Key
(10/buster) 
W: Some index files failed to download. They have been ignored, or old
ones used instead.

I use Debian 12. The only changes i did before the problem occurred,
were the installation of apt-cacher-ng and i ran "mach bootstrap" in a
chroot.



If you remove apt-cacher-ng, does it work at all?

--
John Doe

Re: Problem with apt maybe related to installation/configuration of apt-cacher-ng

[john doe]

On 5/30/23 19:39, Dennis Heddicke wrote:

Hello,

i have a problem with "apt update", everytime i execute the command, i
get the following error messages:

Get:1 http://security.debian.org/debian-security bookworm-security
InRelease [48,0 kB]
Get:2 http://deb.debian.org/debian bookworm InRelease [193 kB]
Err:1 http://security.debian.org/debian-security bookworm-security
InRelease
  The following signatures were invalid: BADSIG 112695A0E562B32A Debian
Security Archive Automatic Signing Key (10/buster) 
Err:2 http://deb.debian.org/debian bookworm InRelease
  The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian
Archive Automatic Signing Key (10/buster) 
Fetched 241 kB in 0s (507 kB/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository
is not updated and the previous index files will be used.
GPG error: http://security.debian.org/debian-security bookworm-security
InRelease: The following signatures were invalid:
BADSIG 112695A0E562B32A Debian Security Archive Automatic Signing Key
(10/buster) 
W: An error occurred during the signature verification. The repository
is not updated and the previous index files will be used.
GPG error: http://deb.debian.org/debian bookworm InRelease: The
following signatures were invalid: BADSIG 648ACFD622F3D
138 Debian Archive Automatic Signing Key (10/buster) 
W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease
  The following signatures were invalid: BADSIG 648ACFD622F3D138
Debian Archive Automatic Signing Key (10/buster) 
W: Failed to fetch
http://security.debian.org/debian-security/dists/bookworm-security/InRelease  
The following signatures were invalid:
BADSIG 112695A0E562B32A Debian Security Archive Automatic Signing Key
(10/buster) 
W: Some index files failed to download. They have been ignored, or old
ones used instead.

I use Debian 12. The only changes i did before the problem occurred,
were the installation of apt-cacher-ng and i ran "mach bootstrap" in a
chroot.



If you remove apt-cacher-ng, does it work at all?

--
John Doe

Problem with apt maybe related to installation/configuration of apt-cacher-ng

[Dennis Heddicke]

Hello,

i have a problem with "apt update", everytime i execute the command, i 
get the following error messages:


Get:1 http://security.debian.org/debian-security bookworm-security 
InRelease [48,0 kB]

Get:2 http://deb.debian.org/debian bookworm InRelease [193 kB]
Err:1 http://security.debian.org/debian-security bookworm-security 
InRelease
 The following signatures were invalid: BADSIG 112695A0E562B32A Debian 
Security Archive Automatic Signing Key (10/buster) 

Err:2 http://deb.debian.org/debian bookworm InRelease
 The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian 
Archive Automatic Signing Key (10/buster) 

Fetched 241 kB in 0s (507 kB/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository 
is not updated and the previous index files will be used.
GPG error: http://security.debian.org/debian-security bookworm-security 
InRelease: The following signatures were invalid:
BADSIG 112695A0E562B32A Debian Security Archive Automatic Signing Key 
(10/buster) 
W: An error occurred during the signature verification. The repository 
is not updated and the previous index files will be used.
GPG error: http://deb.debian.org/debian bookworm InRelease: The 
following signatures were invalid: BADSIG 648ACFD622F3D

138 Debian Archive Automatic Signing Key (10/buster) 
W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease 
 The following signatures were invalid: BADSIG 648ACFD622F3D138

Debian Archive Automatic Signing Key (10/buster) 
W: Failed to fetch 
http://security.debian.org/debian-security/dists/bookworm-security/InRelease 
 The following signatures were invalid:
BADSIG 112695A0E562B32A Debian Security Archive Automatic Signing Key 
(10/buster) 
W: Some index files failed to download. They have been ignored, or old 
ones used instead.


I use Debian 12. The only changes i did before the problem occurred, 
were the installation of apt-cacher-ng and i ran "mach bootstrap" in a 
chroot. I don't think, the last thing would change this much the 
operating system, although it was a stupid idea. Even more stupid, since 
the solution for my problem  was the installation of "sudo" in the 
chroot. 🙁 So maybe the first one is responsible for the problem.


So far I tried the following configurations for apt-cacher-ng, to 
resolve the problem:


Acquire::http::proxy "http://localhost:3142";;
Acquire::https::proxy "https://";;

and

Acquire::http {Proxy "http://127.0.0.1:3142";; };
Acquire::https {Proxy "https://";; };

but none solved it.

I hope someone can help me with my problem. Thank you in advance.

Best Regards
Dennis

Re: apt-cacher internal error (died)

[Adam Weremczuk]

Thanks David, the server runs 9.2 and clients 9.1 so hopefully it will 
work ok.


Another reason I kept changing sources.list in the client was in the 
aftermath of my recent attempts against apt-cacher.


In apt-cacher you change every line to point to apt-cacher:3142.
At least that's what I have in the legacy config I've inherited.
I'm assuming it worked at some point in the past.

On 21/09/2022 17:49, David Wright wrote:

  "One word of advice: serving to clients running a more recent
   distribution from a server running an older one can cause problems,
   because of minor improvements that are sometimes made in the way
   the archives and the cache are handled and stored."

Re: apt-cacher internal error (died)

[David Wright]

On Wed 21 Sep 2022 at 16:26:25 (+0100), Adam Weremczuk wrote:
> On 21/09/2022 15:36, Darac Marjal wrote:
> > I'm no expert in apt-cacher-ng, but the error here says that's
> > it's trying to look up "debian-security" as a hostname. If I'm
> > reading this page
> > <https://help.ubuntu.com/community/Apt-Cacher%20NG> correctly, you
> > shouldn't be changing /etc/apt/sources.list to point to
> > apt-cacher-ng, instead, you should continue to point it to
> > deb.debian.org or snapshot.debian.org and, instead, tell apt to
> > use apt-cacher-ng as an HTTP proxy.
> > 
> > The protocol that a HTTP server and a HTTP proxy use are
> > _slightly_ different. Instead of a client asking a server "Give me
> > /path/to/index.html", it needs to tell the proxy "Give me
> > /path/to/index.html from example.com". I suspect you problem comes
> > of trying to download packages from apt-cacher-ng, rather than
> > proxying through apt-cacher-ng.
> > 
> Thank you Darac, that was my problem indeed!
> What confused me was the fact that, despite being fundamentally
> misconfigured, it appeared to be almost working. Just complaining
> about one security mirror.

It wasn't "fundamentally" misconfigured: you just kept changing
the sources.list in the client when asked not to. Anyway, glad
that it works now.

BTW, obviously we see that you're running at least one machine
on stretch. I couldn't help wondering whether my musings in
  https://lists.debian.org/debian-user/2021/09/msg00305.html
  https://lists.debian.org/debian-user/2021/08/msg00882.html
were related in any way. (I take it you run a mix of versions.)
That's one of the reasons I wrote this advice:

 "One word of advice: serving to clients running a more recent
  distribution from a server running an older one can cause problems,
  because of minor improvements that are sometimes made in the way
  the archives and the cache are handled and stored."

Cheers,
David.

Re: apt-cacher internal error (died)

[Bob Weber]

On 9/21/22 10:36, Darac Marjal wrote:



On 21/09/2022 14:07, Adam Weremczuk wrote:

Hi David,

There is still something wrong with my /etc/apt/sources.list

Perhaps caused by stretch reaching end of life on 30 June 2022.

Can somebody provide me with a tested list of mirrors for stretch working in 
Sep 2022 for apt-cacher-ng server and clients?


I've tried several different sets getting no errors from "apt update" on the 
server (which has internet connectivity).


Every time I repeat this list in /etc/apt/sources.list on a client replacing 
FQDN (e.g. deb.debian.org or security.debian.org) with my server's IP and 
port (192.168.100.1:3142) I get DNS errors for security mirror as below:


Err:5 http://192.168.100.1:3142/debian-security stretch/updates Release
  503  DNS error for hostname debian-security: Name or service not known. If 
debian-security refers to a configured cache repository, please check the 
corresponding configuration file.


I'm no expert in apt-cacher-ng, but the error here says that's it's trying to 
look up "debian-security" as a hostname. If I'm reading this page 
<https://help.ubuntu.com/community/Apt-Cacher%20NG> correctly, you shouldn't 
be changing /etc/apt/sources.list to point to apt-cacher-ng, instead, you 
should continue to point it to deb.debian.org or snapshot.debian.org and, 
instead, tell apt to use apt-cacher-ng as an HTTP proxy.


The protocol that a HTTP server and a HTTP proxy use are _slightly_ different. 
Instead of a client asking a server "Give me /path/to/index.html", it needs to 
tell the proxy "Give me /path/to/index.html from example.com". I suspect you 
problem comes of trying to download packages from apt-cacher-ng, rather than 
proxying through apt-cacher-ng.





or

503  DNS error for hostname security: No address associated with hostname.

Perhaps /etc/apt-cacher-ng/acng.conf on the server needs amending as well?

I've found a line there that reads:

Remap-debrep: file:deb_mirror*.gz /debian ; file:backends_debian # Debian 
Archives


Regards,
Adam



On 13/09/2022 05:54, David Wright wrote:

Err:5http://192.168.100.1:3142/security stretch/updates Release
    503  DNS error for hostname security: No address associated with
hostname. If security refers to a configured cache repository, please
check the corresponding configuration file.
E: The repository 'http://192.168.100.1:3142/security stretch/updates
Release' does not have a Release file.


I use apt-cacher-ng also.  The apt proxy is setup in each client with the 
following file:


-- /etc/apt/apt.conf.d/000apt-cacher-ng-proxy

# This configuration snipped is intended to be stored in /etc/apt/apt.conf.d/
# on the client system in order to change a regular setup to use apt-cacher-ng.
#
Acquire::http::Proxy "http://172.16.0.1:3142/";;

# Little optimization. A value of 10 has been used in earlier version of
# apt-get but was disabled in the beginning of the second decade because of
# incompatibilities with certain HTTP proxies. However, it still beneficial
# with proxy servers that support it good enough (like apt-cacher-ng).
#
Acquire::http::Pipeline-Depth "23";

-

That tells apt to use a proxy on the server 172.16.0.1 at port 3142.  The source 
list files remain the same.


Like for testing:

deb http://deb.debian.org/debian/ testing main non-free contrib

apt-cacher-ng can even connect to an external proxy (In setup file) but if it is 
running on a machine that can get to the internet it will not need an additional 
proxy (why waist resources).


This makes apt-cacher-ng work just like the client was connected to the internet 
with the exception of adding the above 000apt-cacher-ng-proxy file being the 
only change needed.


...bob

Re: apt-cacher internal error (died)

[Adam Weremczuk]

Thank you Darac, that was my problem indeed!
What confused me was the fact that, despite being fundamentally 
misconfigured, it appeared to be almost working. Just complaining about 
one security mirror.


On 21/09/2022 15:36, Darac Marjal wrote:
I'm no expert in apt-cacher-ng, but the error here says that's it's 
trying to look up "debian-security" as a hostname. If I'm reading this 
page <https://help.ubuntu.com/community/Apt-Cacher%20NG> correctly, you 
shouldn't be changing /etc/apt/sources.list to point to apt-cacher-ng, 
instead, you should continue to point it to deb.debian.org or 
snapshot.debian.org and, instead, tell apt to use apt-cacher-ng as an 
HTTP proxy.


The protocol that a HTTP server and a HTTP proxy use are _slightly_ 
different. Instead of a client asking a server "Give me 
/path/to/index.html", it needs to tell the proxy "Give me 
/path/to/index.html from example.com". I suspect you problem comes of 
trying to download packages from apt-cacher-ng, rather than proxying 
through apt-cacher-ng.

Re: apt-cacher internal error (died)

[Darac Marjal]

On 21/09/2022 14:07, Adam Weremczuk wrote:

Hi David,

There is still something wrong with my /etc/apt/sources.list

Perhaps caused by stretch reaching end of life on 30 June 2022.

Can somebody provide me with a tested list of mirrors for stretch 
working in Sep 2022 for apt-cacher-ng server and clients?


I've tried several different sets getting no errors from "apt update" 
on the server (which has internet connectivity).


Every time I repeat this list in /etc/apt/sources.list on a client 
replacing FQDN (e.g. deb.debian.org or security.debian.org) with my 
server's IP and port (192.168.100.1:3142) I get DNS errors for 
security mirror as below:


Err:5 http://192.168.100.1:3142/debian-security stretch/updates Release
  503  DNS error for hostname debian-security: Name or service not 
known. If debian-security refers to a configured cache repository, 
please check the corresponding configuration file.


I'm no expert in apt-cacher-ng, but the error here says that's it's 
trying to look up "debian-security" as a hostname. If I'm reading this 
page <https://help.ubuntu.com/community/Apt-Cacher%20NG> correctly, you 
shouldn't be changing /etc/apt/sources.list to point to apt-cacher-ng, 
instead, you should continue to point it to deb.debian.org or 
snapshot.debian.org and, instead, tell apt to use apt-cacher-ng as an 
HTTP proxy.


The protocol that a HTTP server and a HTTP proxy use are _slightly_ 
different. Instead of a client asking a server "Give me 
/path/to/index.html", it needs to tell the proxy "Give me 
/path/to/index.html from example.com". I suspect you problem comes of 
trying to download packages from apt-cacher-ng, rather than proxying 
through apt-cacher-ng.





or

503  DNS error for hostname security: No address associated with 
hostname.


Perhaps /etc/apt-cacher-ng/acng.conf on the server needs amending as 
well?


I've found a line there that reads:

Remap-debrep: file:deb_mirror*.gz /debian ; file:backends_debian # 
Debian Archives


Regards,
Adam



On 13/09/2022 05:54, David Wright wrote:

Err:5http://192.168.100.1:3142/security stretch/updates Release
    503  DNS error for hostname security: No address associated with
hostname. If security refers to a configured cache repository, please
check the corresponding configuration file.
E: The repository 'http://192.168.100.1:3142/security stretch/updates
Release' does not have a Release file.




OpenPGP_signature
Description: OpenPGP digital signature

Re: apt-cacher internal error (died)

[Adam Weremczuk]

Hi David,

There is still something wrong with my /etc/apt/sources.list

Perhaps caused by stretch reaching end of life on 30 June 2022.

Can somebody provide me with a tested list of mirrors for stretch 
working in Sep 2022 for apt-cacher-ng server and clients?


I've tried several different sets getting no errors from "apt update" on 
the server (which has internet connectivity).


Every time I repeat this list in /etc/apt/sources.list on a client 
replacing FQDN (e.g. deb.debian.org or security.debian.org) with my 
server's IP and port (192.168.100.1:3142) I get DNS errors for security 
mirror as below:


Err:5 http://192.168.100.1:3142/debian-security stretch/updates Release
  503  DNS error for hostname debian-security: Name or service not 
known. If debian-security refers to a configured cache repository, 
please check the corresponding configuration file.


or

503  DNS error for hostname security: No address associated with hostname.

Perhaps /etc/apt-cacher-ng/acng.conf on the server needs amending as well?

I've found a line there that reads:

Remap-debrep: file:deb_mirror*.gz /debian ; file:backends_debian # 
Debian Archives


Regards,
Adam



On 13/09/2022 05:54, David Wright wrote:

Err:5http://192.168.100.1:3142/security  stretch/updates Release
503  DNS error for hostname security: No address associated with
hostname. If security refers to a configured cache repository, please
check the corresponding configuration file.
E: The repository 'http://192.168.100.1:3142/security  stretch/updates
Release' does not have a Release file.

Re: apt-cacher internal error (died)

[David Wright]

On Mon 12 Sep 2022 at 18:57:40 (+0100), Adam Weremczuk wrote:
> On 12/09/2022 16:42, David Wright wrote:
> > On Mon 12 Sep 2022 at 14:33:59 (+0100), Adam Weremczuk wrote:
> > > Switching to apt-cacher-ng brings no immediate joy :(
> > > 
> > > CLIENT (192.168.100.243)
> > > sudo apt update
> > > Err:5 http://192.168.100.1:3142/security stretch/updates Release
> > >503  DNS error for hostname security: No address associated with
> > > hostname. If security refers to a configured cache repository, please
> > > check the corresponding configuration file.
> > > E: The repository 'http://192.168.100.1:3142/security stretch/updates
> > > Release' does not have a Release file.
> > 
> > I would expect to see lines like:
> > 
> > Get:2 http://security.debian.org/debian-security bullseye-security/main 
> > amd64 libgdk-pixbuf-2.0-0 amd64 2.42.2+dfsg-1+deb11u1 [147 kB]
> > 
> > but with stretch/updates rather than bullseye-security, of course,
> > as the syntax was regularised.
> > 
> > > SERVER (192.168.100.1)
> > > 1662988978|E|769|192.168.100.243|security/dists/stretch/updates/InRelease
> > > [HTTP error, code: 503]
> > > 1662988978|M|Download of security/dists/stretch/updates/Release aborted
> > > 
> > > Why a DNS error if I use IPs internally for this exercise?
> > 
> > AFAIK apt-cacher-ng still needs to make contact with debian-security
> > as part of the process.
> > 
> > > Is there something wrong with sources.list on the SERVER:
> > > 
> > > deb http://ftp.uk.debian.org/debian stretch main contrib non-free
> > > deb-src http://ftp.uk.debian.org/debian stretch main contrib non-free
> > > deb http://security.debian.org/ stretch/updates main contrib non-free
> > > deb-src http://security.debian.org/ stretch/updates main contrib non-free
> > 
> > Mine were as attached, with an extra part to security's address.
> > 
> > > sudo apt update
> > > Ign:1 http://ftp.uk.debian.org/debian stretch InRelease
> > > Ign:2 http://hwraid.le-vert.net/debian stretch InRelease
> > > Hit:3 http://ftp.uk.debian.org/debian stretch Release
> > > Get:4 http://security.debian.org stretch/updates InRelease [59.1 kB]
> > > Fetched 59.1 kB in 0s (119 kB/s)
> > > Reading package lists... Done
> > > Building dependency tree
> > > Reading state information... Done
> > > 381 packages can be upgraded. Run 'apt list --upgradable' to see them.
> 
> I've tried your list and the server updates fine.
> 
> On a client I see again:
> 
> sudo apt update
> Ign:1 http://192.168.100.1:3142/debian stretch InRelease
> Ign:2 http://192.168.100.1:3142/debian-security stretch/updates InRelease
> Hit:3 http://192.168.100.1:3142/debian stretch-updates InRelease
> Hit:4 http://192.168.100.1:3142/debian stretch-backports InRelease
> Hit:5 http://192.168.100.1:3142/debian stretch Release
> Err:6 http://192.168.100.1:3142/debian-security stretch/updates Release
>   503  DNS error for hostname debian-security: Name or service not
> known. If debian-security refers to a configured cache repository,
> please check the corresponding configuration file.
> Reading package lists... Done
> E: The repository 'http://192.168.100.1:3142/debian-security
> stretch/updates Release' does not have a Release file.
> N: Updating from such a repository can't be done securely, and is
> therefore disabled by default.
> N: See apt-secure(8) manpage for repository creation and user
> configuration details.
> 
> It looks like there is something wrong with debian-security repo
> specifically.

Did you change your sources.list on the client to make it the same as
the server's?

In case it's not clear, sources.list is not changed for apt-cacher-ng.
You tell it to use the proxy either manually, eg:

# apt-get -o Acquire::http::Proxy="http://192.168.1.14:3142/"; …

of through /etc/apt/apt.conf (or, better, a file in /etc/apt/apt.conf.d/):

Acquire::http::Proxy "http://192.168.1.14:3142/";;

For a laptop, you can turn proxying on and off with the "tricks" shown in
§8.13 of the User Manual in the docs (if it's not the server, of course).

BTW, from what you have posted, it may have escaped you that the
server should also be a client, with its proxy address set to the same
address as all the other clients. That will halve your bandwidth.
Keep that in mind in the penultimate paragraph.

> Could the fact that the client has no internet connectivity play a role?
> I would imagine this is a typical scenario where you want to use apt-cacher.

Re: apt-cacher internal error (died)

[Adam Weremczuk]

Hi David,

I've tried your list and the server updates fine.

On a client I see again:

sudo apt update
Ign:1 http://192.168.100.1:3142/debian stretch InRelease
Ign:2 http://192.168.100.1:3142/debian-security stretch/updates InRelease
Hit:3 http://192.168.100.1:3142/debian stretch-updates InRelease
Hit:4 http://192.168.100.1:3142/debian stretch-backports InRelease
Hit:5 http://192.168.100.1:3142/debian stretch Release
Err:6 http://192.168.100.1:3142/debian-security stretch/updates Release
  503  DNS error for hostname debian-security: Name or service not 
known. If debian-security refers to a configured cache repository, 
please check the corresponding configuration file.

Reading package lists... Done
E: The repository 'http://192.168.100.1:3142/debian-security 
stretch/updates Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is 
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user 
configuration details.


It looks like there is something wrong with debian-security repo 
specifically.


Could the fact that the client has no internet connectivity play a role?
I would imagine this is a typical scenario where you want to use apt-cacher.

Regards,
Adam


On 12/09/2022 16:42, David Wright wrote:

On Mon 12 Sep 2022 at 14:33:59 (+0100), Adam Weremczuk wrote:

Switching to apt-cacher-ng brings no immediate joy :(

CLIENT (192.168.100.243)
sudo apt update
Err:5 http://192.168.100.1:3142/security stretch/updates Release
   503  DNS error for hostname security: No address associated with
hostname. If security refers to a configured cache repository, please
check the corresponding configuration file.
E: The repository 'http://192.168.100.1:3142/security stretch/updates
Release' does not have a Release file.


I would expect to see lines like:

Get:2 http://security.debian.org/debian-security bullseye-security/main amd64 
libgdk-pixbuf-2.0-0 amd64 2.42.2+dfsg-1+deb11u1 [147 kB]

but with stretch/updates rather than bullseye-security, of course,
as the syntax was regularised.


SERVER (192.168.100.1)
1662988978|E|769|192.168.100.243|security/dists/stretch/updates/InRelease
[HTTP error, code: 503]
1662988978|M|Download of security/dists/stretch/updates/Release aborted

Why a DNS error if I use IPs internally for this exercise?


AFAIK apt-cacher-ng still needs to make contact with debian-security
as part of the process.


Is there something wrong with sources.list on the SERVER:

deb http://ftp.uk.debian.org/debian stretch main contrib non-free
deb-src http://ftp.uk.debian.org/debian stretch main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib non-free


Mine were as attached, with an extra part to security's address.


sudo apt update
Ign:1 http://ftp.uk.debian.org/debian stretch InRelease
Ign:2 http://hwraid.le-vert.net/debian stretch InRelease
Hit:3 http://ftp.uk.debian.org/debian stretch Release
Get:4 http://security.debian.org stretch/updates InRelease [59.1 kB]
Fetched 59.1 kB in 0s (119 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
381 packages can be upgraded. Run 'apt list --upgradable' to see them.


Cheers,
David.

Re: apt-cacher internal error (died)

[David Wright]

On Mon 12 Sep 2022 at 14:33:59 (+0100), Adam Weremczuk wrote:
> Switching to apt-cacher-ng brings no immediate joy :(
> 
> CLIENT (192.168.100.243)
> sudo apt update
> Err:5 http://192.168.100.1:3142/security stretch/updates Release
>   503  DNS error for hostname security: No address associated with
> hostname. If security refers to a configured cache repository, please
> check the corresponding configuration file.
> E: The repository 'http://192.168.100.1:3142/security stretch/updates
> Release' does not have a Release file.

I would expect to see lines like:

Get:2 http://security.debian.org/debian-security bullseye-security/main amd64 
libgdk-pixbuf-2.0-0 amd64 2.42.2+dfsg-1+deb11u1 [147 kB]

but with stretch/updates rather than bullseye-security, of course,
as the syntax was regularised.

> SERVER (192.168.100.1)
> 1662988978|E|769|192.168.100.243|security/dists/stretch/updates/InRelease
> [HTTP error, code: 503]
> 1662988978|M|Download of security/dists/stretch/updates/Release aborted
> 
> Why a DNS error if I use IPs internally for this exercise?

AFAIK apt-cacher-ng still needs to make contact with debian-security
as part of the process.

> Is there something wrong with sources.list on the SERVER:
> 
> deb http://ftp.uk.debian.org/debian stretch main contrib non-free
> deb-src http://ftp.uk.debian.org/debian stretch main contrib non-free
> deb http://security.debian.org/ stretch/updates main contrib non-free
> deb-src http://security.debian.org/ stretch/updates main contrib non-free

Mine were as attached, with an extra part to security's address.

> sudo apt update
> Ign:1 http://ftp.uk.debian.org/debian stretch InRelease
> Ign:2 http://hwraid.le-vert.net/debian stretch InRelease
> Hit:3 http://ftp.uk.debian.org/debian stretch Release
> Get:4 http://security.debian.org stretch/updates InRelease [59.1 kB]
> Fetched 59.1 kB in 0s (119 kB/s)
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> 381 packages can be upgraded. Run 'apt list --upgradable' to see them.

Cheers,
David.
# stretch

# deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 NETINST 
20171209-12:10]/ stretch contrib main non-free

#deb cdrom:[Debian GNU/Linux 9.3.0 _Stretch_ - Official amd64 NETINST 
20171209-12:10]/ stretch contrib main non-free

deb http://ftp.us.debian.org/debian/ stretch main non-free contrib
deb-src http://ftp.us.debian.org/debian/ stretch main non-free contrib

deb http://security.debian.org/debian-security stretch/updates main contrib 
non-free
deb-src http://security.debian.org/debian-security stretch/updates main contrib 
non-free

# stretch-updates, previously known as 'volatile'
deb http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free
deb-src http://ftp.us.debian.org/debian/ stretch-updates main contrib non-free

# stretch-backports, previously on backports.debian.org
deb http://ftp.us.debian.org/debian/ stretch-backports main contrib non-free
deb-src http://ftp.us.debian.org/debian/ stretch-backports main contrib non-free

Re: apt-cacher internal error (died)

[Adam Weremczuk]

Switching to apt-cacher-ng brings no immediate joy :(

CLIENT (192.168.100.243)
sudo apt update
Err:5 http://192.168.100.1:3142/security stretch/updates Release
  503  DNS error for hostname security: No address associated with 
hostname. If security refers to a configured cache repository, please 
check the corresponding configuration file.
E: The repository 'http://192.168.100.1:3142/security stretch/updates 
Release' does not have a Release file.


SERVER (192.168.100.1)
1662988978|E|769|192.168.100.243|security/dists/stretch/updates/InRelease [HTTP 
error, code: 503]

1662988978|M|Download of security/dists/stretch/updates/Release aborted

Why a DNS error if I use IPs internally for this exercise?

Is there something wrong with sources.list on the SERVER:

deb http://ftp.uk.debian.org/debian stretch main contrib non-free
deb-src http://ftp.uk.debian.org/debian stretch main contrib non-free
deb http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib non-free

sudo apt update
Ign:1 http://ftp.uk.debian.org/debian stretch InRelease
Ign:2 http://hwraid.le-vert.net/debian stretch InRelease
Hit:3 http://ftp.uk.debian.org/debian stretch Release
Get:4 http://security.debian.org stretch/updates InRelease [59.1 kB]
Fetched 59.1 kB in 0s (119 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
381 packages can be upgraded. Run 'apt list --upgradable' to see them.

?

Thanks,
Adam


On 08/09/2022 19:12, Adam Weremczuk wrote:

Hi David,

 From SERVER:/etc/apt-cacher/apt-cacher.conf

user = www-data
group = www-data

sudo chown -R www-data:www-data /var/cache/apt/archives/*

Same error on the CLIENT :(

I think I'll give apt-cacher-ng a shot instead although I wouldn't mind 
knowing why apt-cacher keeps failing.


Regards,
Adam

On 08/09/2022 16:28, David Wright wrote:

Disclaimer: I run apt-cacher-ng, and have never looked at apt-cacher.

On Wed 07 Sep 2022 at 17:50:16 (+0100), Adam Weremczuk wrote:


SERVER

Wed Sep  7 17:06:40 2022|error [10088]: Failed to open/create
/var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb for return:
Permission denied at /usr/sbin/apt-cacher line 735,  line 4.
Wed Sep  7 17:07:58 2022|warn [20848]: Warning: unable to close
filehandle __ANONIO__ properly: Bad file descriptor at
/usr/sbin/apt-cacher line 1539.

Permissions seem fine:

ls -al /var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb
lrwxrwxrwx 1 proxy proxy 51 Aug 22 18:13
/var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb ->
/var/cache/apt/archives/memtest86+_5.01-3_amd64.deb

ls -al /var/cache/apt/archives/memtest86+_5.01-3_amd64.deb
-rw-r--r-- 1 myuser users 75142 Nov 18  2021
/var/cache/apt/archives/memtest86+_5.01-3_amd64.deb

All folders in both paths are 755.


I don't understand the commingling of apt-cacher and apt; is this
how apt-cacher is designed to work? When I install a new package
on a client, the server does not use /var/cache/apt/archives/,
but only its /var/cache/apt-cacher/ directories, from which it
will serve clients.

If someone was logged in to a client and installing package foo,
and I happened to be logged in to the server and installing foo
directly (not via apt-cacher), it would appear from your logs
that we'd both be trying to use the same directory. How would
the permissions work then, and if I cleaned apt's cache, where
would apt-cacher serve the deleted foo file from?

BTW Who is myuser and who is apt-cacher running as?

Cheers,
David.

Re: apt-cacher internal error (died)

[Adam Weremczuk]

Hi David,

From SERVER:/etc/apt-cacher/apt-cacher.conf

user = www-data
group = www-data

sudo chown -R www-data:www-data /var/cache/apt/archives/*

Same error on the CLIENT :(

I think I'll give apt-cacher-ng a shot instead although I wouldn't mind 
knowing why apt-cacher keeps failing.


Regards,
Adam

On 08/09/2022 16:28, David Wright wrote:

Disclaimer: I run apt-cacher-ng, and have never looked at apt-cacher.

On Wed 07 Sep 2022 at 17:50:16 (+0100), Adam Weremczuk wrote:


SERVER

Wed Sep  7 17:06:40 2022|error [10088]: Failed to open/create
/var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb for return:
Permission denied at /usr/sbin/apt-cacher line 735,  line 4.
Wed Sep  7 17:07:58 2022|warn [20848]: Warning: unable to close
filehandle __ANONIO__ properly: Bad file descriptor at
/usr/sbin/apt-cacher line 1539.

Permissions seem fine:

ls -al /var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb
lrwxrwxrwx 1 proxy proxy 51 Aug 22 18:13
/var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb ->
/var/cache/apt/archives/memtest86+_5.01-3_amd64.deb

ls -al /var/cache/apt/archives/memtest86+_5.01-3_amd64.deb
-rw-r--r-- 1 myuser users 75142 Nov 18  2021
/var/cache/apt/archives/memtest86+_5.01-3_amd64.deb

All folders in both paths are 755.


I don't understand the commingling of apt-cacher and apt; is this
how apt-cacher is designed to work? When I install a new package
on a client, the server does not use /var/cache/apt/archives/,
but only its /var/cache/apt-cacher/ directories, from which it
will serve clients.

If someone was logged in to a client and installing package foo,
and I happened to be logged in to the server and installing foo
directly (not via apt-cacher), it would appear from your logs
that we'd both be trying to use the same directory. How would
the permissions work then, and if I cleaned apt's cache, where
would apt-cacher serve the deleted foo file from?

BTW Who is myuser and who is apt-cacher running as?

Cheers,
David.

Re: apt-cacher internal error (died)

[David Wright]

Disclaimer: I run apt-cacher-ng, and have never looked at apt-cacher.

On Wed 07 Sep 2022 at 17:50:16 (+0100), Adam Weremczuk wrote:

> SERVER
> 
> Wed Sep  7 17:06:40 2022|error [10088]: Failed to open/create
> /var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb for return:
> Permission denied at /usr/sbin/apt-cacher line 735,  line 4.
> Wed Sep  7 17:07:58 2022|warn [20848]: Warning: unable to close
> filehandle __ANONIO__ properly: Bad file descriptor at
> /usr/sbin/apt-cacher line 1539.
> 
> Permissions seem fine:
> 
> ls -al /var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb
> lrwxrwxrwx 1 proxy proxy 51 Aug 22 18:13
> /var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb ->
> /var/cache/apt/archives/memtest86+_5.01-3_amd64.deb
> 
> ls -al /var/cache/apt/archives/memtest86+_5.01-3_amd64.deb
> -rw-r--r-- 1 myuser users 75142 Nov 18  2021
> /var/cache/apt/archives/memtest86+_5.01-3_amd64.deb
> 
> All folders in both paths are 755.

I don't understand the commingling of apt-cacher and apt; is this
how apt-cacher is designed to work? When I install a new package
on a client, the server does not use /var/cache/apt/archives/,
but only its /var/cache/apt-cacher/ directories, from which it
will serve clients.

If someone was logged in to a client and installing package foo,
and I happened to be logged in to the server and installing foo
directly (not via apt-cacher), it would appear from your logs
that we'd both be trying to use the same directory. How would
the permissions work then, and if I cleaned apt's cache, where
would apt-cacher serve the deleted foo file from?

BTW Who is myuser and who is apt-cacher running as?

Cheers,
David.

Re: apt-cacher internal error (died)

[Charles Curley]

On Wed, 7 Sep 2022 17:50:16 +0100
Adam Weremczuk  wrote:

> The server runs Debian 9.2 and the client Debian 9.1

I remember having problems with apt-cacher-ng on Debian 9 or
there-abouts. Maybe it's time to upgrade to Bullseye?

apt-cacher-ng has a web server, with which you can do some maintenance.
If I recall correctly, so does apt-cacher. Have you tried running that?
You may need to do it several times.


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

apt-cacher internal error (died)

[Adam Weremczuk]

Hi all,

The server runs Debian 9.2 and the client Debian 9.1

My errors:

CLIENT

$ sudo apt update
Ign:1 http://192.168.1.100:3142/debian stretch InRelease
Hit:2 http://192.168.1.100:3142/debian stretch-updates InRelease
Hit:3 http://192.168.1.100:3142/debian stretch Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
91 packages can be upgraded. Run 'apt list --upgradable' to see them.

$ sudo apt install memtest86+
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  hwtools memtester kernel-patch-badram memtest86 mtools
The following NEW packages will be installed:
  memtest86+
0 upgraded, 1 newly installed, 0 to remove and 91 not upgraded.
Need to get 75.1 kB of archives.
After this operation, 2,448 kB of additional disk space will be used.
Err:1 http://192.168.1.100:3142/debian stretch/main amd64 memtest86+ 
amd64 5.01-3

  502  apt-cacher internal error (died)
E: Failed to fetch 
http://192.168.1.100:3142/debian/pool/main/m/memtest86+/memtest86+_5.01-3_amd64.deb 
 502  apt-cacher internal error (died)
E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?


SERVER

Wed Sep  7 17:06:40 2022|error [10088]: Failed to open/create 
/var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb for return: 
Permission denied at /usr/sbin/apt-cacher line 735,  line 4.
Wed Sep  7 17:07:58 2022|warn [20848]: Warning: unable to close 
filehandle __ANONIO__ properly: Bad file descriptor at 
/usr/sbin/apt-cacher line 1539.


Permissions seem fine:

ls -al /var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb
lrwxrwxrwx 1 proxy proxy 51 Aug 22 18:13 
/var/cache/apt-cacher/packages/memtest86+_5.01-3_amd64.deb -> 
/var/cache/apt/archives/memtest86+_5.01-3_amd64.deb


ls -al /var/cache/apt/archives/memtest86+_5.01-3_amd64.deb
-rw-r--r-- 1 myuser users 75142 Nov 18  2021 
/var/cache/apt/archives/memtest86+_5.01-3_amd64.deb


All folders in both paths are 755.

Any ideas?

Regards,
Adam

Re: apt-cacher-ng problems

[Tim Woodall]

On Sun, 7 Aug 2022, David Wright wrote:


On Sun 07 Aug 2022 at 08:46:12 (+0100), Tim Woodall wrote:

I installed acng yesterday. Nothing else has changed.

A script is fetching all of the required packages plus a few others for
amd64,i386,arm64 and armel starting with sid all the way to jessie

Rather complicated setup: (This does make sense although in this
particular failure it looks excessively complicated)

apt(aptmirror17) -> acng (localhost) -> squid (different host) ->
apache(back on aptmirror17)

downloaded all of the i386 packages and was fine for amd64 until
1659848478|O|404276|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/grep_3.7-1_amd64.deb
1659848478|E|632|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/gzip_1.12-1_amd64.deb
 [HTTP error, code: 502]
1659848478|E|632|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/hostname_3.23_amd64.deb
 [HTTP error, code: 502]
etc


So you're caching sid ?


I don't have the exact output from apt for this particular error but it
will have been something like:
Err:129 http://aptmirror17.home.woodall.me.uk/local buster/essential
armel linux-image-4.19.0-21-rpi armel 4.19.249-2
  502  Connection closed [IP: ::1 3128]
...

[ ? ]

I cannot see anything wrong in either of the squid or apache logs.

[ ? ]

Squid checking the file is unchanged is logged by apache.
2001:8b0:bfcd:100:MUNGED:8 - - [07/Aug/2022:05:01:17 +]
"GET /local/pool/essential/sid/amd64/grep_3.7-1_amd64.deb HTTP/1.1" 304
- "-" "Apt-Cacher-NG/3.6.4" "aptmirror17.home.woodall.me.uk"


? and that looks as if you're running acng/bullseye.

Your setup is too complicated for me to give any direct help, but
I can say that running acng/versionN to cache packages from versionN+1
has twice led to a need to upgrade to acng/versionNbackports, once to
acng/versionNsloppybpo, and once where even that wasn't enough.



Thanks, I'm caching packages from everything from jessie to sid. I've
just backported acng. I'll clear the acng cache and rerun the caching of
the essential/required packages and see if the problem is fixed.

I had failures while fetching sid, bullseye, buster and stretch
packages. Only jessie didn't have any failures (which might have just
been luck - plus jessie doesn't have arm64 so a smaller set to fetch)

I'm doing a lot of automatic bootstrap builds which is why I want all of
these packages explicitly cached. I've been keeping a mirror of these
packages but I have to maintain that - acng seemed to be a way to avoid
any need to maintain the cache manually. (and it looks like it will do
the job I want)

I'm bootstrapping using only apt and dpkg and a "essential on a diet"
scheme
https://wiki.debian.org/Proposals/EssentialOnDiet
apt to decide the order to install packages and dpkg to unpack and
install them. In order to confirm that everything is always going to
work I have to ensure that an install in every possible order allowed by
the dependencies will work.

I've had to make changes to a surprisingly small set of packages to make
this work, even for jessie.
Sid only needs changes to apt (dependency change), base-files (slightly
reworked postinst script and dependency change) and util-linux
(dependency change)

Tim.

Re: apt-cacher-ng problems

[David Wright]

On Sun 07 Aug 2022 at 08:46:12 (+0100), Tim Woodall wrote:
> I installed acng yesterday. Nothing else has changed.
> 
> A script is fetching all of the required packages plus a few others for
> amd64,i386,arm64 and armel starting with sid all the way to jessie
> 
> Rather complicated setup: (This does make sense although in this
> particular failure it looks excessively complicated)
> 
> apt(aptmirror17) -> acng (localhost) -> squid (different host) ->
> apache(back on aptmirror17)
> 
> downloaded all of the i386 packages and was fine for amd64 until
> 1659848478|O|404276|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/grep_3.7-1_amd64.deb
> 1659848478|E|632|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/gzip_1.12-1_amd64.deb
>  [HTTP error, code: 502]
> 1659848478|E|632|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/hostname_3.23_amd64.deb
>  [HTTP error, code: 502]
> etc

So you're caching sid …

> I don't have the exact output from apt for this particular error but it
> will have been something like:
> Err:129 http://aptmirror17.home.woodall.me.uk/local buster/essential
> armel linux-image-4.19.0-21-rpi armel 4.19.249-2
>   502  Connection closed [IP: ::1 3128]
> ...
[ … ]
> I cannot see anything wrong in either of the squid or apache logs.
[ … ]
> Squid checking the file is unchanged is logged by apache.
> 2001:8b0:bfcd:100:MUNGED:8 - - [07/Aug/2022:05:01:17 +]
> "GET /local/pool/essential/sid/amd64/grep_3.7-1_amd64.deb HTTP/1.1" 304
> - "-" "Apt-Cacher-NG/3.6.4" "aptmirror17.home.woodall.me.uk"

… and that looks as if you're running acng/bullseye.

Your setup is too complicated for me to give any direct help, but
I can say that running acng/versionN to cache packages from versionN+1
has twice led to a need to upgrade to acng/versionNbackports, once to
acng/versionNsloppybpo, and once where even that wasn't enough.

> It looks very much to me that acng is getting overloaded due to the
> amount of data it is writing.
> 
> I've kept retrying and after about a dozen failures, all the data is now
> cached and I no longer get these 502 errors.
> 
> FTAOD, this has worked flawlessly until I added acng into the mix.
> 
> 
> Anyone got any ideas? I can change logging on all parts of this chain.
> 
> 
> Two other acng questions:
> How can I disable expiry completely? I've set it to 4 days
> currently.
> 
> Can I disable caching for aptmirror17 specifically?
> 
> The documentation isn't great...

Cheers,
David.

Re: apt-cacher-ng problems

[Tim Woodall]

On Sun, 7 Aug 2022, Tim Woodall wrote:


I installed acng yesterday. Nothing else has changed.

A script is fetching all of the required packages plus a few others for
amd64,i386,arm64 and armel starting with sid all the way to jessie

Rather complicated setup: (This does make sense although in this
particular failure it looks excessively complicated)

apt(aptmirror17) -> acng (localhost) -> squid (different host) ->
apache(back on aptmirror17)

downloaded all of the i386 packages and was fine for amd64 until
1659848478|O|404276|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/grep_3.7-1_amd64.deb
1659848478|E|632|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/gzip_1.12-1_amd64.deb 
[HTTP error, code: 502]
1659848478|E|632|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/hostname_3.23_amd64.deb 
[HTTP error, code: 502]

etc



Looks like I've hit this issue:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998705

And someone has suggested that a backport from sid might fix it.

apt-cacher-ng problems

[Tim Woodall]

I installed acng yesterday. Nothing else has changed.

A script is fetching all of the required packages plus a few others for
amd64,i386,arm64 and armel starting with sid all the way to jessie

Rather complicated setup: (This does make sense although in this
particular failure it looks excessively complicated)

apt(aptmirror17) -> acng (localhost) -> squid (different host) ->
apache(back on aptmirror17)

downloaded all of the i386 packages and was fine for amd64 until
1659848478|O|404276|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/grep_3.7-1_amd64.deb
1659848478|E|632|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/gzip_1.12-1_amd64.deb
 [HTTP error, code: 502]
1659848478|E|632|::1|aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/hostname_3.23_amd64.deb
 [HTTP error, code: 502]
etc

I don't have the exact output from apt for this particular error but it
will have been something like:
Err:129 http://aptmirror17.home.woodall.me.uk/local buster/essential
armel linux-image-4.19.0-21-rpi armel 4.19.249-2
  502  Connection closed [IP: ::1 3128]
...
Fetched 39.6 MB in 10s (4058 kB/s)
E: Failed to fetch
http://aptmirror17.home.woodall.me.uk/local/pool/essential/buster/armel/linux-image-4.19.0-21-rpi_4.19.249-2_armel.deb
502  Connection closed [IP: ::1 3128]


I cannot see anything wrong in either of the squid or apache logs.

Squid:
1659848477.523100 2001:8b0:bfcd:100:MUNGED:7
TCP_REFRESH_UNMODIFIED/200 404354 GET
http://aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/grep_3.7-1_amd64.deb
- HIER_DIRECT/2001:8b0:bfcd:100:MUNGED:7
  application/vnd.debian.binary-package
1659848477.539 63 2001:8b0:bfcd:100:MUNGED:7
TCP_REFRESH_UNMODIFIED/200 140762 GET
http://aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/gzip_1.12-1_amd64.deb
- HIER_DIRECT/2001:8b0:bfcd:100:MUNGED:7
  application/vnd.debian.binary-package
1659848477.547 16 2001:8b0:bfcd:100:MUNGED:7
TCP_REFRESH_UNMODIFIED/200 15344 GET
http://aptmirror17.home.woodall.me.uk/local/pool/essential/sid/amd64/hostname_3.23_amd64.deb
- HIER_DIRECT/2001:8b0:bfcd:100:MUNGED:7
  application/vnd.debian.binary-package


Squid checking the file is unchanged is logged by apache.
2001:8b0:bfcd:100:MUNGED:8 - - [07/Aug/2022:05:01:17 +]
"GET /local/pool/essential/sid/amd64/grep_3.7-1_amd64.deb HTTP/1.1" 304
- "-" "Apt-Cacher-NG/3.6.4" "aptmirror17.home.woodall.me.uk"
2001:8b0:bfcd:100:MUNGED:8 - - [07/Aug/2022:05:01:17 +]
"GET /local/pool/essential/sid/amd64/gzip_1.12-1_amd64.deb HTTP/1.1" 304
- "-" "Apt-Cacher-NG/3.6.4" "aptmirror17.home.woodall.me.uk"
2001:8b0:bfcd:100:MUNGED:8 - - [07/Aug/2022:05:01:17 +]
"GET /local/pool/essential/sid/amd64/hostname_3.23_amd64.deb HTTP/1.1"
304 - "-" "Apt-Cacher-NG/3.6.4" "aptmirror17.home.woodall.me.uk"

...



It looks very much to me that acng is getting overloaded due to the
amount of data it is writing.

I've kept retrying and after about a dozen failures, all the data is now
cached and I no longer get these 502 errors.

FTAOD, this has worked flawlessly until I added acng into the mix.


Anyone got any ideas? I can change logging on all parts of this chain.


Two other acng questions:
How can I disable expiry completely? I've set it to 4 days
currently.

Can I disable caching for aptmirror17 specifically?

The documentation isn't great...

Tim.

Re: apt-cacher-ng and CNAMEs

[Celejar]

On Tue, 3 May 2022 21:24:11 +0200
Nito  wrote:

> On Tue, May 03, 2022 at 15:16:47 -0400, Celejar wrote:
> > [...], and I'm consequently somehow getting bitten by
> > this issue:
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986356
> > 
> > But that (as described by the maintainer) mess was supposedly resolved,
> > and the bug was closed. Am I missing something, or does that bug need
> > to be reopened?
> 
> Are you using stable? The bug has been closed with version 
> 3.7.1-1 of apt-cacher-ng. Stable currently has 3.6.4-1 with
> no indication of a patch being applied for this bug.
> Bullseye-backoprts offers 3.7.4-1~bpo11+1 though, so you could
> likely use this to get a fix for #986356.

I'm using Sid, apt-cacher-ng version 3.7.4-1.

-- 
Celejar

Re: apt-cacher-ng and CNAMEs

[Nito]

On Tue, May 03, 2022 at 15:16:47 -0400, Celejar wrote:
> [...], and I'm consequently somehow getting bitten by
> this issue:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986356
> 
> But that (as described by the maintainer) mess was supposedly resolved,
> and the bug was closed. Am I missing something, or does that bug need
> to be reopened?

Are you using stable? The bug has been closed with version 
3.7.1-1 of apt-cacher-ng. Stable currently has 3.6.4-1 with
no indication of a patch being applied for this bug.
Bullseye-backoprts offers 3.7.4-1~bpo11+1 though, so you could
likely use this to get a fix for #986356.

> -- 
> Celejar
> 

apt-cacher-ng and CNAMEs

[Celejar]

I'm trying to use the Tor upstream repositories:

https://support.torproject.org/apt/tor-deb-repo/

Direct access works correctly, but proxying through apt-cacher-ng
(using SSL passthrough, as per the apt-cacher-ng documentation) does
not:

Err:1 https://deb.torproject.org/torproject.org sid InRelease
  Certificate verification failed: The certificate is NOT trusted. The 
certificate issuer is unknown.  Could not handshake: Error in the certificate 
verification. [IP: xx.xx.xx.xx 3142]

I've been beating my head over this for a while, and I have arrived at
the tentative conclusion that the problem has something to do with the
fact that deb.torproject.org is a CNAME alias for
static.torproject.org., and I'm consequently somehow getting bitten by
this issue:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986356

But that (as described by the maintainer) mess was supposedly resolved,
and the bug was closed. Am I missing something, or does that bug need
to be reopened?

-- 
Celejar

getting apt-cacher-ng to pass auth through

[Ólafur Jens Sigurðsson]

Hi, I would like to use apt-cacher-ng to cache the updates from 
enterprise.proxmox.com. One thing about this repo is that they have two 
different kinds, the http one and the https one, the http one is 
non-enterprise and open to all, but the https one is closed and needs a 
subscription with a username/password.


In our current setup the proxmox node connects directly to the 
enterprise.proxmox.com server and asks for updates but we would like to 
stop that and use a cacher instead. My problem is that the 
authentication does not seem to be sent through the cacher.


What I have tried so far is to set apt-cacher-ng up with the following 
rewrite in /etc/apt-cacher-ng/acng.conf


Remap-proxmox: http://enterprise.proxmox.com ; 
https://enterprise.proxmox.com


In the proxmox machine I have told it to use our local cacher by setting 
this in /etc/apt.conf.d/02proxy


Acquire::http::Proxy "http://192.168.140.18:3142";;

where 192.168.140.18 is the IP of our apt-cacher-ng server. In 
/etc/apt/sources.list.d/pve-enterprise.list we put deb 
http://enterprise.proxmox.com/debian/pve buster pve-enterprise (the http 
is needed since apt-cacher-ng does not understand https).


With this setup then I run apt-update and it fails in the way that it 
fetches the http Release file instead of the https one, here is the 
output on the proxmox machine:


root@production-proxmox-slave01:~# apt update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://ftp.dk.debian.org/debian buster InRelease
Hit:3 http://ftp.dk.debian.org/debian buster-updates InRelease
Err:4 http://enterprise.proxmox.com/debian/pve buster InRelease
  401  Unauthorized [IP: 192.168.140.18 3142]
Reading package lists... Done
E: Failed to fetch 
http://enterprise.proxmox.com/debian/pve/dists/buster/InRelease 401  
Unauthorized [IP: 192.168.140.18 3142]
E: The repository 'http://enterprise.proxmox.com/debian/pve buster 
InRelease' is no longer signed.
N: Updating from such a repository can't be done securely, and is 
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user 
configuration details.


As you can see the cacher works fine for normal debian repos

On the apt-cacher-ng server I put VerboseLog to 2 and Debug to 7, the 
output to /var/log/apt-cacher-ng/apt-cacher.err is the following:


Tue Jul  6 10:51:52 2021|fileitem::DoDelayedUnregAndCheck, nextRunTime 
now: 9223372036854775805

Tue Jul  6 10:51:55 2021|Detected incoming connection from the TCP socket
Tue Jul  6 10:51:55 2021|Client name: 192.168.140.30
Tue Jul  6 10:51:55 2021|Detected incoming connection from the TCP socket
Tue Jul  6 10:51:55 2021|Client name: 192.168.140.30
Tue Jul  6 10:51:55 2021|Detected incoming connection from the TCP socket
Tue Jul  6 10:51:55 2021|Client name: 192.168.140.30
Tue Jul  6 10:51:55 2021|Decoded request URI: 
http://ftp.dk.debian.org/debian/dists/buster/InRelease
Tue Jul  6 10:51:55 2021|Processing new job, GET 
http://ftp.dk.debian.org/debian/dists/buster/InRelease HTTP/1.1
Tue Jul  6 10:51:55 2021|Decoded request URI: 
http://security.debian.org/dists/buster/updates/InRelease
Tue Jul  6 10:51:55 2021|Processing new job, GET 
http://security.debian.org/dists/buster/updates/InRelease HTTP/1.1
Tue Jul  6 10:51:55 2021|Decoded request URI: 
http://enterprise.proxmox.com/debian/pve/dists/buster/InRelease
Tue Jul  6 10:51:55 2021|Processing new job, GET 
http://enterprise.proxmox.com/debian/pve/dists/buster/InRelease HTTP/1.1
Tue Jul  6 10:51:55 2021|Download started, storeHeader for 
secdeb/dists/buster/updates/InRelease, current status: 1

Tue Jul  6 10:51:55 2021|Response header to be sent in the next cycle:
HTTP/1.1 304 Not Modified
Content-Length: 0
Date: Tue Jul  6 08:51:55 2021
Server: Debian Apt-Cacher NG/3.2.1
X-Original-Source: http://security.debian.org/dists/buster/updates/InRelease
Connection: Keep-Alive


Tue Jul  6 10:51:55 2021|Returning to last state, 6
Tue Jul  6 10:51:55 2021|Download started, storeHeader for 
debrep/dists/buster/InRelease, current status: 1
Tue Jul  6 10:51:55 2021|known data hit, don't write to: 
debrep/dists/buster/InRelease

Tue Jul  6 10:51:55 2021|Response header to be sent in the next cycle:
HTTP/1.1 304 Not Modified
Content-Length: 0
Date: Tue Jul  6 08:51:55 2021
Server: Debian Apt-Cacher NG/3.2.1
X-Original-Source: http://deb.debian.org/debian/dists/buster/InRelease
Connection: Keep-Alive


Tue Jul  6 10:51:55 2021|Returning to last state, 6
Tue Jul  6 10:51:55 2021|Decoded request URI: 
http://ftp.dk.debian.org/debian/dists/buster-updates/InRelease
Tue Jul  6 10:51:55 2021|Processing new job, GET 
http://ftp.dk.debian.org/debian/dists/buster-updates/InRelease HTTP/1.1
Tue Jul  6 10:51:55 2021|Download started, storeHeader for 
debrep/dists/buster-updates/InRelease, current status: 1
Tue Jul  6 10:51:55 2021|known data hit, don't write to: 
debrep/dists/buster-updates/InRelease

Tue Jul  6 10:51:55 2021|Response header to be s

Re: can not update/upgrade Debian 10 when using apt-cacher-ng

[john doe]

On 11/5/2019 4:49 PM, David Wright wrote:
> On Tue 05 Nov 2019 at 06:59:55 (+0100), john doe wrote:
>> On 10/29/2019 4:10 PM, to...@tuxteam.de wrote:
>>> On Tue, Oct 29, 2019 at 03:58:04PM +0100, john doe wrote:
>>>> On 10/29/2019 2:01 PM, to...@tuxteam.de wrote:
>>>>> On Tue, Oct 29, 2019 at 01:36:35PM +0100, john doe wrote:
>>>>>> On 10/29/2019 12:50 PM, Charles Curley wrote:
>>>>>>> On Tue, 29 Oct 2019 11:45:02 +0100
>>>>>>> john doe  wrote:
>>>>>>>
>>>>>>>> /etc/apt/sources.list:
>>>>>>>>
>>>>>>>> http://HOSTNAME-APT-CACHER-NG>:3142/debian-security buster/updates
>>>
>>> [...]
>>>
>>>> Yes, the hostname is not the one I use.
>>>
>>> Phew :-)
>>>
>>>> For now, method 2 is used when '/etc/apt/sources.list' is created by the
>>>> Debian installer, so method 1 is not an option.
>>>
>>> Not clear why, but... let's assume that.
>>>
>>>> Everything else is working but not downloading the upgrade through
>>>> apg-cacher-ng.
>>>>
>>>> Is anyone using a proxy to download the upgrade(s) and what format is to
>>>> be used in '/etc/apt/sources.list'?
>>>
>>> I have used that in the past, but I do prefer the cache specification
>>> in apt config these days.
>>>
>>> What happens when you point your browser at your cache instance?
>>>
>>> What do the cache log files say? (Find them typically in
>>> /var/log/apt-cacher-ng/apt-cacher.err and ...log).
>>>
>>
>> I have filed a bugreport regarding this (1).
>>
>> In a nutshell, the secdeb remap rule is missing the "directory spec".
>> Adding the directory spec ('/debian-security') wright before the first
>> semicolon (';') fixes the issue, so the secdeb line should look like:
>>
>> Remap-secdeb: security.debian.org /debian-security ; security.debian.org
>> deb.debian.org/debian-security
>>
>> Thanks to anyone who has chimed in.
>>
>>
>> 1)  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944114.
>
> This stuff goes a bit over my head, but I wondered whether it would
> explain something. When I converted¹ this laptop from stretch to
> buster, I copied its entire stretch/apt-cacher-ng cache of .deb files
> into the _import directory of the new buster/apt-cacher-ng and ran
> the import process from its maintenance webpage.
>
> All the packages destined for the debrep side of the cache were
> imported into their appropriate places in the directory tree, but
> nothing made it into the secdeb side. Those packages were left, and
> remain, in the _import directory. I assume now that apt-cacher-ng
> could not find out the structure of the directory tree in which to
> place them.
>
> Could that problem arise out of your bug?
>

I would imagine so, if no 'directory spec' is included in the remap rule
(secdeb line in this case) '/var/cache/apt-cacher-ng/secdeb'  will never
be created.

You can verify this, using the CLI as root, as follow:

For testing purposes, on the same host on which apt-cacher-ng is
installed try the following:

Put only those two lines in '/etc/apt/sources.list':
deb http://localhost:3142/debian-security buster/updates main
deb-src http://localhost:3142/debian-security buster/updates main


now try:

$ apt-get update

If you get the DNS error mentioned in the bugreport you need to modify
the 'secdeb' line in '/etc/apt-cacher-ng/acng.conf' to make it look like
the one I have provided or the one I use:

Remap-secdeb: security.debian.org deb.debian.org/debian-security ;
security.debian.org deb.debian.org/debian-security


I don't use the GUI, so can't help you on that front! :)


HTH.

--
John Doe

Re: can not update/upgrade Debian 10 when using apt-cacher-ng

[David Wright]

On Tue 05 Nov 2019 at 06:59:55 (+0100), john doe wrote:
> On 10/29/2019 4:10 PM, to...@tuxteam.de wrote:
> > On Tue, Oct 29, 2019 at 03:58:04PM +0100, john doe wrote:
> >> On 10/29/2019 2:01 PM, to...@tuxteam.de wrote:
> >>> On Tue, Oct 29, 2019 at 01:36:35PM +0100, john doe wrote:
> >>>> On 10/29/2019 12:50 PM, Charles Curley wrote:
> >>>>> On Tue, 29 Oct 2019 11:45:02 +0100
> >>>>> john doe  wrote:
> >>>>>
> >>>>>> /etc/apt/sources.list:
> >>>>>>
> >>>>>> http://HOSTNAME-APT-CACHER-NG>:3142/debian-security buster/updates
> >
> > [...]
> >
> >> Yes, the hostname is not the one I use.
> >
> > Phew :-)
> >
> >> For now, method 2 is used when '/etc/apt/sources.list' is created by the
> >> Debian installer, so method 1 is not an option.
> >
> > Not clear why, but... let's assume that.
> >
> >> Everything else is working but not downloading the upgrade through
> >> apg-cacher-ng.
> >>
> >> Is anyone using a proxy to download the upgrade(s) and what format is to
> >> be used in '/etc/apt/sources.list'?
> >
> > I have used that in the past, but I do prefer the cache specification
> > in apt config these days.
> >
> > What happens when you point your browser at your cache instance?
> >
> > What do the cache log files say? (Find them typically in
> > /var/log/apt-cacher-ng/apt-cacher.err and ...log).
> >
> 
> I have filed a bugreport regarding this (1).
> 
> In a nutshell, the secdeb remap rule is missing the "directory spec".
> Adding the directory spec ('/debian-security') wright before the first
> semicolon (';') fixes the issue, so the secdeb line should look like:
> 
> Remap-secdeb: security.debian.org /debian-security ; security.debian.org
> deb.debian.org/debian-security
> 
> Thanks to anyone who has chimed in.
> 
> 
> 1)  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944114.

This stuff goes a bit over my head, but I wondered whether it would
explain something. When I converted¹ this laptop from stretch to
buster, I copied its entire stretch/apt-cacher-ng cache of .deb files
into the _import directory of the new buster/apt-cacher-ng and ran
the import process from its maintenance webpage.

All the packages destined for the debrep side of the cache were
imported into their appropriate places in the directory tree, but
nothing made it into the secdeb side. Those packages were left, and
remain, in the _import directory. I assume now that apt-cacher-ng
could not find out the structure of the directory tree in which to
place them.

Could that problem arise out of your bug?

(The secdeb tree is now being populated normally as a result of the
usual buster security updates.)

¹ buster is a new installation; the stretch system remains behind
  on a twin partition; /home is a shared partition. The stretch
  cache was well populated with buster packages as all the other
  five PCs here had switched to buster already, all via this cache.

Cheers,
David.

Re: can not update/upgrade Debian 10 when using apt-cacher-ng

[john doe]

On 10/29/2019 4:10 PM, to...@tuxteam.de wrote:
> On Tue, Oct 29, 2019 at 03:58:04PM +0100, john doe wrote:
>> On 10/29/2019 2:01 PM, to...@tuxteam.de wrote:
>>> On Tue, Oct 29, 2019 at 01:36:35PM +0100, john doe wrote:
>>>> On 10/29/2019 12:50 PM, Charles Curley wrote:
>>>>> On Tue, 29 Oct 2019 11:45:02 +0100
>>>>> john doe  wrote:
>>>>>
>>>>>> /etc/apt/sources.list:
>>>>>>
>>>>>> http://HOSTNAME-APT-CACHER-NG>:3142/debian-security buster/updates
>
> [...]
>
>> Yes, the hostname is not the one I use.
>
> Phew :-)
>
>> For now, method 2 is used when '/etc/apt/sources.list' is created by the
>> Debian installer, so method 1 is not an option.
>
> Not clear why, but... let's assume that.
>
>> Everything else is working but not downloading the upgrade through
>> apg-cacher-ng.
>>
>> Is anyone using a proxy to download the upgrade(s) and what format is to
>> be used in '/etc/apt/sources.list'?
>
> I have used that in the past, but I do prefer the cache specification
> in apt config these days.
>
> What happens when you point your browser at your cache instance?
>
> What do the cache log files say? (Find them typically in
> /var/log/apt-cacher-ng/apt-cacher.err and ...log).
>

I have filed a bugreport regarding this (1).

In a nutshell, the secdeb remap rule is missing the "directory spec".
Adding the directory spec ('/debian-security') wright before the first
semicolon (';') fixes the issue, so the secdeb line should look like:

Remap-secdeb: security.debian.org /debian-security ; security.debian.org
deb.debian.org/debian-security

Thanks to anyone who has chimed in.


1)  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944114.

--
John Doe

Re: can not update/upgrade Debian 10 when using apt-cacher-ng

[tomas]

On Tue, Oct 29, 2019 at 03:58:04PM +0100, john doe wrote:
> On 10/29/2019 2:01 PM, to...@tuxteam.de wrote:
> > On Tue, Oct 29, 2019 at 01:36:35PM +0100, john doe wrote:
> >> On 10/29/2019 12:50 PM, Charles Curley wrote:
> >>> On Tue, 29 Oct 2019 11:45:02 +0100
> >>> john doe  wrote:
> >>>
> >>>> /etc/apt/sources.list:
> >>>>
> >>>> http://HOSTNAME-APT-CACHER-NG>:3142/debian-security buster/updates

[...]

> Yes, the hostname is not the one I use.

Phew :-)

> For now, method 2 is used when '/etc/apt/sources.list' is created by the
> Debian installer, so method 1 is not an option.

Not clear why, but... let's assume that.

> Everything else is working but not downloading the upgrade through
> apg-cacher-ng.
> 
> Is anyone using a proxy to download the upgrade(s) and what format is to
> be used in '/etc/apt/sources.list'?

I have used that in the past, but I do prefer the cache specification
in apt config these days.

What happens when you point your browser at your cache instance?

What do the cache log files say? (Find them typically in
/var/log/apt-cacher-ng/apt-cacher.err and ...log).

Cheers
-- t


signature.asc
Description: Digital signature

Re: can not update/upgrade Debian 10 when using apt-cacher-ng

[john doe]

On 10/29/2019 2:01 PM, to...@tuxteam.de wrote:
> On Tue, Oct 29, 2019 at 01:36:35PM +0100, john doe wrote:
>> On 10/29/2019 12:50 PM, Charles Curley wrote:
>>> On Tue, 29 Oct 2019 11:45:02 +0100
>>> john doe  wrote:
>>>
>>>> /etc/apt/sources.list:
>>>>
>>>> http://HOSTNAME-APT-CACHER-NG>:3142/debian-security buster/updates
>>>^
>>>
>>> That greater than character looks problematic; is it correct?
>>>
>>
>> It is a typo, thanks for spotting, the line I'm currently using is:
>>
>> http://HOSTNAME-APT-CACHER-NG:3142/debian-security buster/updates main
>>
>>> Also, I find that setup puts a file, apt.conf, in your /etc/apt
>>> directory, with the apt-cacher redirection in it:
>>>
>>> Acquire::http::Proxy "http://aptcacherdeb.localdomain:3142";;
>>>
>>
>> I'm installing from a preseed file, if possible, I'd like to keep the
>> file as created by d-i.
>>
>>
>>> If that file exists, you don't need the redirection in sources.list.
>>> All you need is the provided sources.list, e.g.:
>>>
>>> deb http://security.debian.org/debian-security buster/updates main contrib 
>>> non-free
>>> # deb-src http://security.debian.org/debian-security buster/updates main 
>>> contrib non-free
>>>
>>
>> Actually, that is my question why can't the above line be redirected to
>> my proxy?
>
> No. *EITHER* you set the proxy once-and-for-all in your APT conf (I have
> something like:
>
> Acquire::http::proxy "http://localhost:3142";;
>
> (replace localhost and 3142 by values making sense in your context)
> in a file named "/etc/apt/apt.conf.d/02cache", for example) *OR* you
> prefix the cache to each entry in your sources.list which you want to
> go through the cache (you might want some repos to be fetched directly,
> or via another cache, for example).
>
> Furthermore I'm assuming you have something meaningful instead of
> that funny looking "HOSTNAME-APT-CACHER-NG" (or that this actually
> resolves to a host in your setup). Otherwise it won't work...
>

Yes, the hostname is not the one I use.

According to (1), there are two methods to use a proxy apg-cacher-ng in
this case:
- "• Specify the caching machine as HTTP Proxy for your download client.
This can be usually done
- "• Replace all mirror hostnames with cachinghost/hostname in
sources.list, ..."


For now, method 2 is used when '/etc/apt/sources.list' is created by the
Debian installer, so method 1 is not an option.


Everything else is working but not downloading the upgrade through
apg-cacher-ng.

Is anyone using a proxy to download the upgrade(s) and what format is to
be used in '/etc/apt/sources.list'?

I'm clearly missing something here! :)

1)
https://www.unix-ag.uni-kl.de/~bloch/acng/html/config-servquick.html#config-client


--
John Doe

Re: can not update/upgrade Debian 10 when using apt-cacher-ng

[tomas]

On Tue, Oct 29, 2019 at 01:36:35PM +0100, john doe wrote:
> On 10/29/2019 12:50 PM, Charles Curley wrote:
> > On Tue, 29 Oct 2019 11:45:02 +0100
> > john doe  wrote:
> >
> >> /etc/apt/sources.list:
> >>
> >> http://HOSTNAME-APT-CACHER-NG>:3142/debian-security buster/updates
> >^
> >
> > That greater than character looks problematic; is it correct?
> >
> 
> It is a typo, thanks for spotting, the line I'm currently using is:
> 
> http://HOSTNAME-APT-CACHER-NG:3142/debian-security buster/updates main
> 
> > Also, I find that setup puts a file, apt.conf, in your /etc/apt
> > directory, with the apt-cacher redirection in it:
> >
> > Acquire::http::Proxy "http://aptcacherdeb.localdomain:3142";;
> >
> 
> I'm installing from a preseed file, if possible, I'd like to keep the
> file as created by d-i.
> 
> 
> > If that file exists, you don't need the redirection in sources.list.
> > All you need is the provided sources.list, e.g.:
> >
> > deb http://security.debian.org/debian-security buster/updates main contrib 
> > non-free
> > # deb-src http://security.debian.org/debian-security buster/updates main 
> > contrib non-free
> >
> 
> Actually, that is my question why can't the above line be redirected to
> my proxy?

No. *EITHER* you set the proxy once-and-for-all in your APT conf (I have
something like:

Acquire::http::proxy "http://localhost:3142";;

(replace localhost and 3142 by values making sense in your context)
in a file named "/etc/apt/apt.conf.d/02cache", for example) *OR* you
prefix the cache to each entry in your sources.list which you want to
go through the cache (you might want some repos to be fetched directly,
or via another cache, for example).

Furthermore I'm assuming you have something meaningful instead of
that funny looking "HOSTNAME-APT-CACHER-NG" (or that this actually
resolves to a host in your setup). Otherwise it won't work...

Cheers
-- t


signature.asc
Description: Digital signature

Re: can not update/upgrade Debian 10 when using apt-cacher-ng

[john doe]

On 10/29/2019 12:50 PM, Charles Curley wrote:
> On Tue, 29 Oct 2019 11:45:02 +0100
> john doe  wrote:
>
>> /etc/apt/sources.list:
>>
>> http://HOSTNAME-APT-CACHER-NG>:3142/debian-security buster/updates
>^
>
> That greater than character looks problematic; is it correct?
>

It is a typo, thanks for spotting, the line I'm currently using is:

http://HOSTNAME-APT-CACHER-NG:3142/debian-security buster/updates main

> Also, I find that setup puts a file, apt.conf, in your /etc/apt
> directory, with the apt-cacher redirection in it:
>
> Acquire::http::Proxy "http://aptcacherdeb.localdomain:3142";;
>

I'm installing from a preseed file, if possible, I'd like to keep the
file as created by d-i.


> If that file exists, you don't need the redirection in sources.list.
> All you need is the provided sources.list, e.g.:
>
> deb http://security.debian.org/debian-security buster/updates main contrib 
> non-free
> # deb-src http://security.debian.org/debian-security buster/updates main 
> contrib non-free
>

Actually, that is my question why can't the above line be redirected to
my proxy?


In other words, can 'http://security.debian.org/debian-security
buster/updates main' be changed.

--
John Doe

Re: can not update/upgrade Debian 10 when using apt-cacher-ng

[Charles Curley]

On Tue, 29 Oct 2019 11:45:02 +0100
john doe  wrote:

> /etc/apt/sources.list:
> 
> http://HOSTNAME-APT-CACHER-NG>:3142/debian-security buster/updates
   ^

That greater than character looks problematic; is it correct?

Also, I find that setup puts a file, apt.conf, in your /etc/apt
directory, with the apt-cacher redirection in it:

Acquire::http::Proxy "http://aptcacherdeb.localdomain:3142";;

If that file exists, you don't need the redirection in sources.list.
All you need is the provided sources.list, e.g.:

deb http://security.debian.org/debian-security buster/updates main contrib 
non-free
# deb-src http://security.debian.org/debian-security buster/updates main 
contrib non-free



-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

can not update/upgrade Debian 10 when using apt-cacher-ng

[john doe]

Hi,

I'm playing with apt-cacher-ng, it works fine when installing debian but
I get the following errors when trying to 'apt-get update'
(apt-cacher-ng's log):

|dists/buster/updates/InRelease [HTTP error, code: 503]
|debrep/dists/buster-updates/InRelease

The below URL makes the above error:

/etc/apt/sources.list:

http://HOSTNAME-APT-CACHER-NG>:3142/debian-security buster/updates main


I didn't modify the config of apt-cacher-ng on Debian Buster (10) from
the moment I installed it.


In other words, how can I update/upgrade Debian through apt-cacher-ng.


Any help is appriciated.

--
John Doe

Re: apt-cacher-ng's expiry job failing

[Eduard Bloch]

Hallo,
* David Wright [Sat, Apr 27 2019, 09:31:50AM]:
> > /var/cache/apt-cacher-ng/_xstore/rsnap/debrep/dists/unstable/45961554550630227606591
> >
> > I removed the file and it started complaining about other similar files.
> > After deleting a couple, the logs became even more unhelpful:
> >
> > Maintenance task Expiration, apt-cacher-ng version: 2 (Cancel)

Old. And had some issues in that area. Try
https://packages.debian.org/stretch-backports/apt-cacher-ng

Best regards,
Eduard.

Re: apt-cacher-ng's expiry job failing

[David Wright]

On Sat 27 Apr 2019 at 07:47:44 (-0300), Eduardo M KALINOWSKI wrote:
> On 26/04/2019 13:05, David Wright wrote:
> > Today's successful run, which removed probably most of the wheezy
> > packages in my cache¹, had the following error in the log:
> >
> > Error at 
> > security.debian.org/debian-security/dists/stretch/updates/19704841552237202370979443
> >
> > but it didn't stop the run. This file exists, but is actually at
> > /var/cache/apt-cacher-ng/_xstore/rsnap/security.debian.org/…
> > so take a look there perhaps.
> 
> That made me look for a file with that name in the whole hierarchy, and
> I found it at
> 
> /var/cache/apt-cacher-ng/_xstore/rsnap/debrep/dists/unstable/45961554550630227606591
> 
> I removed the file and it started complaining about other similar files.
> After deleting a couple, the logs became even more unhelpful:
> 
> Maintenance task Expiration, apt-cacher-ng version: 2 (Cancel)
> Locating potentially expired files in the cache...
> Scanning, found 1 file...
> Scanning, found 2 files...
> Scanning, found 4 files...
> Scanning, found 8 files...
> Scanning, found 16 files...
> Scanning, found 32 files...
> Scanning, found 64 files...
> Scanning, found 128 files...
> Scanning, found 256 files...
> Scanning, found 512 files...
> Scanning, found 1024 files...
> Scanning, found 2048 files...
> Found 2427 files.
> Checking implicitly referenced files...
> Restoring virtual file
> debrep/dists/testing/contrib/Contents-i386.diff/Index (equal to )
> Restoring virtual file
> debrep/dists/testing/contrib/i18n/Translation-en.diff/Index (equal to )
> Restoring virtual file
> debrep/dists/unstable/contrib/i18n/Translation-en.diff/Index (equal to )
> Bringing index files up to date...
> Found errors during processing, aborting as requested.
> 
> -- 
> Stult's Report:
>   Our problems are mostly behind us.  What we have to do now is
>   fight the solutions.

No solutions here, I'm afraid.

Today's run, which could have been running neck and neck with updating
and upgrading the point release¹, was again successful, but only needed
to tag some files without removing any.

The log contained one error again, this time for the file
debrep/dists/stretch/19774491550329202244056132 which is in
/var/cache/apt-cacher-ng/_xstore/rsnap/debrep/…
The file is alone in that directory, and it's unsigned. Its timestamp
is about the time that the update ran, but its internal timestamp is
mid-February.

There's no message arising from the file 19704841552237202370979443
which is still present.

In both cases the error was reported at the changeover from the
"Restoring virtual file…" phase to "Checking …" and
"Checking/Updating …" phases. So it might be the case that my
error occurs in a different phase from yours, and that yours is
treated as more serious.

But the other possibility is that the problem arises from caching
unstable. I ran into problems when I cached jessie on a wheezy
system, and had to use both backports and backports-sloppy at
various times to accomplish expiration of an overgrown cache.

Sorry to be the blind leading the blind.

Cheers,
David.

Re: apt-cacher-ng's expiry job failing

[Eduardo M KALINOWSKI]

On 26/04/2019 13:05, David Wright wrote:
> Today's successful run, which removed probably most of the wheezy
> packages in my cache¹, had the following error in the log:
>
> Error at 
> security.debian.org/debian-security/dists/stretch/updates/19704841552237202370979443
>
> but it didn't stop the run. This file exists, but is actually at
> /var/cache/apt-cacher-ng/_xstore/rsnap/security.debian.org/…
> so take a look there perhaps.

That made me look for a file with that name in the whole hierarchy, and
I found it at

/var/cache/apt-cacher-ng/_xstore/rsnap/debrep/dists/unstable/45961554550630227606591

I removed the file and it started complaining about other similar files.
After deleting a couple, the logs became even more unhelpful:

Maintenance task Expiration, apt-cacher-ng version: 2 (Cancel)
Locating potentially expired files in the cache...
Scanning, found 1 file...
Scanning, found 2 files...
Scanning, found 4 files...
Scanning, found 8 files...
Scanning, found 16 files...
Scanning, found 32 files...
Scanning, found 64 files...
Scanning, found 128 files...
Scanning, found 256 files...
Scanning, found 512 files...
Scanning, found 1024 files...
Scanning, found 2048 files...
Found 2427 files.
Checking implicitly referenced files...
Restoring virtual file
debrep/dists/testing/contrib/Contents-i386.diff/Index (equal to )
Restoring virtual file
debrep/dists/testing/contrib/i18n/Translation-en.diff/Index (equal to )
Restoring virtual file
debrep/dists/unstable/contrib/i18n/Translation-en.diff/Index (equal to )
Bringing index files up to date...
Found errors during processing, aborting as requested.



-- 
Stult's Report:
Our problems are mostly behind us.  What we have to do now is
fight the solutions.

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: apt-cacher-ng's expiry job failing

[David Wright]

On Thu 25 Apr 2019 at 13:08:07 (+), Eduardo M KALINOWSKI wrote:
> The daily apt-cacher-ng expiry job is failing in my machine. It refers
> me to a log file, whose contents are:
> 
> ---
> Maintenance task Expiration, apt-cacher-ng version: 2
> 
> Locating potentially expired files in the cache...
> Scanning, found 1 file...
> Scanning, found 2 files...
> Scanning, found 4 files...
> Scanning, found 8 files...
> Scanning, found 16 files...
> Scanning, found 32 files...
> Scanning, found 64 files...
> Scanning, found 128 files...
> Scanning, found 256 files...
> Scanning, found 512 files...
> Scanning, found 1024 files...
> Found 1617 files.
> Checking implicitly referenced files...
> Restoring virtual file
> debrep/dists/testing/contrib/Contents-i386.diff/Index (equal to )
> 
> Restoring virtual file
> debrep/dists/testing/contrib/i18n/Translation-en.diff/Index (equal to
> )
> 
> Restoring virtual file
> debrep/dists/unstable/contrib/i18n/Translation-en.diff/Index (equal to
> )
> 
> Bringing index files up to date...
> 
> Restoring virtual file
> debrep/dists/unstable/contrib/i18n/Translation-en.diff/Index (equal to
> )
> 
> Error at debrep/dists/unstable/45961554550630227606591
> 
> Found errors during processing, aborting as requested.
> ---
> 
> I can also run the expiry from its web interface, and get the same results.
> 
> Unfortunately, it does not make clear *what* is the error that was
> found. The only clue is 'Error at
> debrep/dists/unstable/45961554550630227606591', but there is no such
> file under
>  /var/cache/apt-cacher-ng/debrep/dists/unstable .
> 
> Anyone has any clue on how to fix this problem?

This probably won't be of great help.

Today's successful run, which removed probably most of the wheezy
packages in my cache¹, had the following error in the log:

Error at 
security.debian.org/debian-security/dists/stretch/updates/19704841552237202370979443

but it didn't stop the run. This file exists, but is actually at
/var/cache/apt-cacher-ng/_xstore/rsnap/security.debian.org/…
so take a look there perhaps.

The contents of the file look sane. Running a diff against the next
version showed that a fair number of files had been updated, and
the signature was completely different. However, that next version
and the one after that showed that the signature is always different
regardless of content, because there were no update differences in
the rest of the file.

These files go back months, and their timestamps seem to correspond
to the times when my   apt-get update   runs occur. So perhaps you
could try hiding the file and running the web interface again.

¹ I had to decrease ExStartTradeOff from 500m to 10m to give
expiration a push because jessie and stretch have been quite quiet
in the period since I removed all wheezy's apt-cacher-ng metadata.

Cheers,
David.

apt-cacher-ng's expiry job failing

[Eduardo M KALINOWSKI]

The daily apt-cacher-ng expiry job is failing in my machine. It refers  
me to a log file, whose contents are:


---
Maintenance task Expiration, apt-cacher-ng version: 2

Locating potentially expired files in the cache...
Scanning, found 1 file...
Scanning, found 2 files...
Scanning, found 4 files...
Scanning, found 8 files...
Scanning, found 16 files...
Scanning, found 32 files...
Scanning, found 64 files...
Scanning, found 128 files...
Scanning, found 256 files...
Scanning, found 512 files...
Scanning, found 1024 files...
Found 1617 files.
Checking implicitly referenced files...
Restoring virtual file  
debrep/dists/testing/contrib/Contents-i386.diff/Index (equal to )


Restoring virtual file  
debrep/dists/testing/contrib/i18n/Translation-en.diff/Index (equal to )


Restoring virtual file  
debrep/dists/unstable/contrib/i18n/Translation-en.diff/Index (equal to )


Bringing index files up to date...

Restoring virtual file  
debrep/dists/unstable/contrib/i18n/Translation-en.diff/Index (equal to )


Error at debrep/dists/unstable/45961554550630227606591

Found errors during processing, aborting as requested.
---

I can also run the expiry from its web interface, and get the same results.

Unfortunately, it does not make clear *what* is the error that was  
found. The only clue is 'Error at  
debrep/dists/unstable/45961554550630227606591', but there is no such  
file under

 /var/cache/apt-cacher-ng/debrep/dists/unstable .

Anyone has any clue on how to fix this problem?
--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: apt-cacher errors

[Greg Wooledge]

On Mon, Mar 25, 2019 at 02:24:22PM +, Adam Weremczuk wrote:
> Any practical difference between \*wheezy\* and '*wheezy*' in this case?

Both forms of quoting yield identical results.  As does "*wheezy*".

Re: apt-cacher errors

[Adam Weremczuk]

Hi Greg,

Thank you for taking the time to point out all the shortcomings.


On 25/03/19 13:21, Greg Wooledge wrote:

On Mon, Mar 25, 2019 at 12:11:21PM +, Adam Weremczuk wrote:

I've found 30 entries referencing wheezy and removed them all:

sudo find /var/cache/apt-cacher/ -type f -name *wheezy* | xargs rm

sudo find /var/cache/apt-cacher -type f -name '*wheezy*' -delete

There are three mistakes in your command:

1) The glob must be quoted, or the shell will expand it based on the files
in the current working directory, wherever that happens to be.
I would normally use \*wheezy\* but I new that wouldn't make any 
difference as I saw the list earlier.

Any practical difference between \*wheezy\* and '*wheezy*' in this case?

2) xargs without -0 is unsafe to use for filenames, because they may contain
whitespace or single quotes or double quotes, all of which are special
to xargs.
Again, I saw the list so didn't bother but a fair point indeed, it could 
easily fail or even turn disastrous.

3) You ran find with sudo privileges (probably not necessary), and failed
to run the rm with sudo privileges.  All of the removals are therefore
going to fail.
TBH I run it as root and added single sudo in front after pasting not to 
promote bad practices :)


You might argue that "apt-cacher never has any files with spaces!"
That may be true.  But it's still a good habit to develop.  Also, -delete
is more efficient than | xargs rm, albeit not portable to POSIX scripts.

Never used it with find, good to know.


If you want it to be portable as well as safe, then:

sudo find /var/cache/apt-cacher -type f -name '*wheezy*' -exec rm {} +

That's less efficient than -delete, but it's the best you can do if
POSIX portability is required.

Agree.

Thanks again,
Adam

Re: apt-cacher errors

[deb]

On 3/25/19 9:21 AM, Greg Wooledge wrote:

On Mon, Mar 25, 2019 at 12:11:21PM +, Adam Weremczuk wrote:

I've found 30 entries referencing wheezy and removed them all:

sudo find /var/cache/apt-cacher/ -type f -name *wheezy* | xargs rm

sudo find /var/cache/apt-cacher -type f -name '*wheezy*' -delete

There are three mistakes in your command:

1) The glob must be quoted, or the shell will expand it based on the files
in the current working directory, wherever that happens to be.

2) xargs without -0 is unsafe to use for filenames, because they may contain
whitespace or single quotes or double quotes, all of which are special
to xargs.

3) You ran find with sudo privileges (probably not necessary), and failed
to run the rm with sudo privileges.  All of the removals are therefore
going to fail.

You might argue that "apt-cacher never has any files with spaces!"
That may be true.  But it's still a good habit to develop.  Also, -delete
is more efficient than | xargs rm, albeit not portable to POSIX scripts.

If you want it to be portable as well as safe, then:

sudo find /var/cache/apt-cacher -type f -name '*wheezy*' -exec rm {} +

That's less efficient than -delete, but it's the best you can do if
POSIX portability is required.




Great thoughts Greg.

Helped me too.

Re: apt-cacher errors

[Greg Wooledge]

On Mon, Mar 25, 2019 at 12:11:21PM +, Adam Weremczuk wrote:
> I've found 30 entries referencing wheezy and removed them all:
> 
> sudo find /var/cache/apt-cacher/ -type f -name *wheezy* | xargs rm

sudo find /var/cache/apt-cacher -type f -name '*wheezy*' -delete

There are three mistakes in your command:

1) The glob must be quoted, or the shell will expand it based on the files
   in the current working directory, wherever that happens to be.

2) xargs without -0 is unsafe to use for filenames, because they may contain
   whitespace or single quotes or double quotes, all of which are special
   to xargs.

3) You ran find with sudo privileges (probably not necessary), and failed
   to run the rm with sudo privileges.  All of the removals are therefore
   going to fail.

You might argue that "apt-cacher never has any files with spaces!"
That may be true.  But it's still a good habit to develop.  Also, -delete
is more efficient than | xargs rm, albeit not portable to POSIX scripts.

If you want it to be portable as well as safe, then:

sudo find /var/cache/apt-cacher -type f -name '*wheezy*' -exec rm {} +

That's less efficient than -delete, but it's the best you can do if
POSIX portability is required.

Re: apt-cacher errors

[Adam Weremczuk]

I've found 30 entries referencing wheezy and removed them all:

sudo find /var/cache/apt-cacher/ -type f -name *wheezy* | xargs rm

which appears to have fixed the issue.

Thanks,
Adam


On 25/03/19 11:43, Roberto C. Sánchez wrote:

On Mon, Mar 25, 2019 at 07:05:11AM -0400, Roberto C. Sánchez wrote:

On Mon, Mar 25, 2019 at 08:59:40AM +, Adam Weremczuk wrote:

Hi all,

On 24th March (last Sunday) I received the following (for the first time):

Subject: Cron test -x /usr/share/apt-cacher/apt-cacher-cleanup.pl && 
/usr/share/apt-cacher/apt-cacher-cleanup.pl

Error: cannot open ../headers/debian_dists_wheezy_Release for locking: No such 
file or directory
Failed to open filehandles for debian_dists_wheezy_Release. Resolve this 
manually.
Exiting to prevent deletion of cache contents.

The above all came from systems originally running wheezy which were upgraded 
to stretch about 2 years ago.

Questions:

1. How to get rid of these errors? I would prefer to avoid spending half a day 
deciphering a chain of Perl scripts which I'm not familiar with.
2. What specifically happened last week to trigger this behavior? Was it e.g. a 
permanent removal of all wheezy repos and references?


https://lists.debian.org/debian-devel-announce/2019/03/msg6.html

You will need to change your sources.list.

http://archive.debian.org/debian/README


Perhaps I spoke too soon.  I encountered this error in my apt-cacher-ng
log after replying to your message.

Checking/Updating debrep/dists/wheezy/Release...
Attempting to download the alternative version... Checking/Updating
debrep/dists/wheezy/InRelease...
404 Not Found

After seeing that I re-read your message and noticed that the system had
been initially installed as wheezy but now runs stretch.

It has been some years since I moved to apt-cacher-ng, so I've forgotten
how it differs from apt-cacher, but in my case I had to remove the
directories /var/cache/apt-cacher-ng/debrep/dists/wheezy* and then
re-run the expiration task.

You may need to do something similar.

Regards,

-Roberto

Re: apt-cacher errors

[Roberto C . Sánchez]

On Mon, Mar 25, 2019 at 07:05:11AM -0400, Roberto C. Sánchez wrote:
> On Mon, Mar 25, 2019 at 08:59:40AM +, Adam Weremczuk wrote:
> > Hi all,
> > 
> > On 24th March (last Sunday) I received the following (for the first time):
> > 
> > Subject: Cron test -x /usr/share/apt-cacher/apt-cacher-cleanup.pl && 
> > /usr/share/apt-cacher/apt-cacher-cleanup.pl
> > 
> > Error: cannot open ../headers/debian_dists_wheezy_Release for locking: No 
> > such file or directory
> > Failed to open filehandles for debian_dists_wheezy_Release. Resolve this 
> > manually.
> > Exiting to prevent deletion of cache contents.
> > 
> > The above all came from systems originally running wheezy which were 
> > upgraded to stretch about 2 years ago.
> > 
> > Questions:
> > 
> > 1. How to get rid of these errors? I would prefer to avoid spending half a 
> > day deciphering a chain of Perl scripts which I'm not familiar with.
> > 2. What specifically happened last week to trigger this behavior? Was it 
> > e.g. a permanent removal of all wheezy repos and references?
> > 
> https://lists.debian.org/debian-devel-announce/2019/03/msg6.html
> 
> You will need to change your sources.list.
> 
> http://archive.debian.org/debian/README
> 
Perhaps I spoke too soon.  I encountered this error in my apt-cacher-ng
log after replying to your message.

Checking/Updating debrep/dists/wheezy/Release...
Attempting to download the alternative version... Checking/Updating
debrep/dists/wheezy/InRelease...
404 Not Found

After seeing that I re-read your message and noticed that the system had
been initially installed as wheezy but now runs stretch.

It has been some years since I moved to apt-cacher-ng, so I've forgotten
how it differs from apt-cacher, but in my case I had to remove the
directories /var/cache/apt-cacher-ng/debrep/dists/wheezy* and then
re-run the expiration task.

You may need to do something similar.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: apt-cacher errors

[Roberto C . Sánchez]

On Mon, Mar 25, 2019 at 08:59:40AM +, Adam Weremczuk wrote:
> Hi all,
> 
> On 24th March (last Sunday) I received the following (for the first time):
> 
> Subject: Cron test -x /usr/share/apt-cacher/apt-cacher-cleanup.pl && 
> /usr/share/apt-cacher/apt-cacher-cleanup.pl
> 
> Error: cannot open ../headers/debian_dists_wheezy_Release for locking: No 
> such file or directory
> Failed to open filehandles for debian_dists_wheezy_Release. Resolve this 
> manually.
> Exiting to prevent deletion of cache contents.
> 
> The above all came from systems originally running wheezy which were upgraded 
> to stretch about 2 years ago.
> 
> Questions:
> 
> 1. How to get rid of these errors? I would prefer to avoid spending half a 
> day deciphering a chain of Perl scripts which I'm not familiar with.
> 2. What specifically happened last week to trigger this behavior? Was it e.g. 
> a permanent removal of all wheezy repos and references?
> 
https://lists.debian.org/debian-devel-announce/2019/03/msg6.html

You will need to change your sources.list.

http://archive.debian.org/debian/README

Regards,

-Roberto

-- 
Roberto C. Sánchez

apt-cacher errors

[Adam Weremczuk]

Hi all,

On 24th March (last Sunday) I received the following (for the first time):

Subject: Cron test -x /usr/share/apt-cacher/apt-cacher-cleanup.pl && 
/usr/share/apt-cacher/apt-cacher-cleanup.pl

Error: cannot open ../headers/debian_dists_wheezy_Release for locking: No such 
file or directory
Failed to open filehandles for debian_dists_wheezy_Release. Resolve this 
manually.
Exiting to prevent deletion of cache contents.

The above all came from systems originally running wheezy which were upgraded 
to stretch about 2 years ago.

Questions:

1. How to get rid of these errors? I would prefer to avoid spending half a day 
deciphering a chain of Perl scripts which I'm not familiar with.
2. What specifically happened last week to trigger this behavior? Was it e.g. a 
permanent removal of all wheezy repos and references?

Regards,
Adam

Re: apt-cacher-ng / autoclean

[Hans]

Am Sonntag, 31. Dezember 2017, 11:54:12 CET schrieb Dominique Dumont:
Hi Dominique,

thanks for the information. The manual was not quite clear for me, what it 
wants. With your example below, I understood what to do. 

It was not clear for me, that I must use a browser, and thought, a commandline 
command (as usual) would do the trick.

Problem solved, so easy!

Thank you very much for your help (also all others, who helped, too)!

Have a nice new years eve!

Best regards

Hans
> On Sunday, 31 December 2017 11:24:30 CET Hans wrote:
> > What must I do, if this is possible at all?
> 
> apt-cacher-ng provides a web page to perform maintenance.
> 
> Open with your favorite browser the page:
> 
>   http://replace-with-your-cache-host:3142/acng-report.html
> 
> For more details, see
> 
>  https://www.unix-ag.uni-kl.de/~bloch/acng/html/index.html
> 
> HTH

Re: apt-cacher-ng / autoclean

[Dominique Dumont]

On Sunday, 31 December 2017 11:24:30 CET Hans wrote:
> What must I do, if this is possible at all?

apt-cacher-ng provides a web page to perform maintenance. 

Open with your favorite browser the page:

  http://replace-with-your-cache-host:3142/acng-report.html

For more details, see 

 https://www.unix-ag.uni-kl.de/~bloch/acng/html/index.html

HTH

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Re: apt-cacher-ng / autoclean

[basti]

Hello,

first of all there is an management page (http://yourhost:3142) and
there are also config options see
https://www.unix-ag.uni-kl.de/~bloch/acng/html/maint.html#maint

Best Regards,

On 31.12.2017 11:24, Hans wrote:
> Hi folks,
> 
> I am a little bit stuck. 
> 
> I am regularly building a livefile system (kali-linux) and using apt-cacher-
> ng, so that I do not need to download all the packages over and over again.
> 
> But the local repo is growing more and more, and as I want to get rid of all 
> old packages, I wanted to use "apt-get autoclean", as I am using it for a 
> normally installed system with downloaded packages.
> 
> But obviously, this does not work. What do I do wrong?
> 
> I thought, running apt-cacher-ng would point to the local repo, and then "apt-
> get autoclean" or "aptitude autoclean" would do tghe rest.
> 
> Obviously this is wrong. 
> 
> What must I do, if this is possible at all?
> 
> Thanks for any hints.
> 
> Best regards
> 
> Hans 
>  
> 

apt-cacher-ng / autoclean

[Hans]

Hi folks,

I am a little bit stuck. 

I am regularly building a livefile system (kali-linux) and using apt-cacher-
ng, so that I do not need to download all the packages over and over again.

But the local repo is growing more and more, and as I want to get rid of all 
old packages, I wanted to use "apt-get autoclean", as I am using it for a 
normally installed system with downloaded packages.

But obviously, this does not work. What do I do wrong?

I thought, running apt-cacher-ng would point to the local repo, and then "apt-
get autoclean" or "aptitude autoclean" would do tghe rest.

Obviously this is wrong. 

What must I do, if this is possible at all?

Thanks for any hints.

Best regards

Hans 
 

Re: apt-cacher-ng related program and package suggestion

[Dan Ritter]

On Thu, Jun 15, 2017 at 10:44:01AM -0400, Bob Weber wrote:
> 
> 
> 
> > Simple workaround for now:
> >
> > /etc/apt/sources.list:
> > 
> > deb http://site1.ip.address/debian jessie-backports main
> > #deb http://site2.ip.address/debian jessie-backports main
> > 
> >
> > Now just change the comment from one to the other, run apt-get
> > update and go.
> >
> > Second workaround, if you have lots of entries to be switched:
> > create two sources.list files, named home.list and uni.list.
> >
> > When you move from place to place, copy the appropriate one 
> > in to /etc/apt/sources.list and run apt-get update.
> >
> > -dsr-
> >
> Its even easier than that.  Don't mess with the .list files just change  the 
> file
> 
> /etc/apt/apt.conf.d/000apt-cacher-ng-proxy
> 
> according to the login.
> 
> The contents of that file is just the address/port of the apt-cacher-ng 
> server.
> 
> Acquire::http::Proxy "http://172.16.0.1:3142/";;
> 
> Just write a script to check what network you are on.  Like ping the
> apt-cacher-ng server(s) until a response is sent and set 
> /etc/apt/apt.conf.d/000apt-cacher-ng-proxy accordingly.
> 
> Try the following line with your own existing and non existing ips.
> 
> for f in 172.16.0.1 172.16.0.2 172.16.0.33; do if ping -c3 $f; then echo $f
> yes;else echo $f no;fi; done
> 

There's a formalized version of this which might be useful:

$ apt-cache show ifscheme
Package: ifscheme
Version: 1.7-3
Maintainer: Guus Sliepen 
Architecture: all
Depends: ifupdown (>= 0.6.5)
Description-en: scheme control for network interfaces ifscheme allows you
to change network configuration schemes or query the current scheme. It
integrates with the ifup(8) command and interfaces(5). For example, you
might use this program to configure a "home" scheme and a "work" scheme
for a network device on a laptop. When you move between home and work,
a simple command can reconfigure your networking.

This could be rigged to change files when the network is
changed.

-dsr-

Re: apt-cacher-ng related program and package suggestion

[Eduard Bloch]

Hallo,
* tuxderlinuxfuch...@gmail.com [Wed, Jun 14 2017, 09:57:50PM]:
>Hello,
> 
>I have a suggestion for a client program/package in combination with
>    apt-cacher-ng
> 
>Consider following situation:
> 
>User U_A has a laptop which he uses at home and at university
> 
>He has a poor internet connection in both places.
> 
>So he set up apt-cacher-ng services in both places but they are on
>different networks (he does not have permission to change the network
>settings at university to make the IP addresses of the apt-cacher-ng
>servers math)
> 
>Lets say at home the server HOST_1 is [1]http://192.168.1.100:3142
>At university: server: HOST_2: [2]http://192.168.76.56:3142
> 
>He uses Ubuntu (so this should work for Debian in a similar way).
> 
>He makes a backup "/etc/apt/sources.list.bak" of /etc/apt/sources.list
> 
>At university he sets up the cache repo as follows (after overwriting the
>/etc/apt/sources.list with a copy of the backup if it was changed to use
>the home apt-cacher-ng)
> 
>sed -i 's/de.archive.ubuntu.com/192.168.76.56:3142/g'
>/etc/apt/sources.list
> 
>The same procedure at home.
> 
>The shown way is not very comfortable.

You can automate this easily with a one-liner in /etc/network/ip-up.d/ ,
for example.

Actually, apt-cacher-ng provides a similar kind of automation but it can
only decide between "use a proxy" and "don't use a proxy" and the need
to switch by checking whether that proxy server is broken/unreachable by
timeout or a user hook script. This can be used well in a proxy cascade,
i.e. one apt-cacher-ng running on the mobile device itself in
non-storing mode, and local applications use that proxy on localhost.

There is, however, no support for multiple proxies that would be
switchable upon the mentioned conditions check. This could be added,
maybe in future. Please open a feature requeston Alioth (apt-cacher-ng
space) or in the BTS.

Regards,
Eduard.

-- 
Every great idea is worthless without someone to do the work. --Neil Williams

Re: apt-cacher-ng related program and package suggestion

[Yvan Masson]

> Another solution whichi does not depend of the server software (squid or
> apt-cacher-ng) is to use this directive on the client:
> Acquire::http::Proxy-Auto-Detect
> 
> I could not find a good example in English, but here is one in French.
> Obviously, man 5 apt.conf also explains it.

Oups, forgot the link:
https://www.blog-libre.org/2016/01/09/configuration-automatique-du-proxy-pour-apt/

The script used to detect the proxy is only two lines…

Regards,
Yvan



signature.asc
Description: OpenPGP digital signature

Re: apt-cacher-ng related program and package suggestion

[David Wright]

On Thu 15 Jun 2017 at 16:44:27 (+0200), tuxderlinuxfuch...@gmail.com wrote:
> Thanks for the tips. Like I said, I'd prefer a program that does all
> this in the background by calling one simple command

Sure. You're free to commission one from a C/C++ programmer.
We're just illustrating that the community doesn't see any
need (IMO) to "make it happen". The tools are already around
for scripting it.

I can see a reason to run apt-cacher-ng at home if you watch
broadcast TV and your ISP makes that assumption for their
customers.

But I can't see the point in your running apt-cacher-ng at a
university. Surely they run a university-wide caching system.
Or are you saying that you have a poor link to the university's
central servers—wireless perhaps? If so, the same applies: that
poor link is far more influential on interactive web browsing,
for example, than downloading debs, which occurs mainly in
the background. So a squid-style solution would be more beneficial.

What might be useful for package administration at work is to
put a line like:

apt-get -qq update && apt-get -qq -d upgrade && find /var/cache/apt/archives/ 
-name '*deb'

in root's or the system's crontab (that's my way), or
configure one of the unattended upgrade packages to
download debs periodically. The line above will send
an email whenever there are packages for you to upgrade
(after inspection; I don't trust automating that step).
No more watching stuttering downloads.

Cheers,
David.

Re: apt-cacher-ng related program and package suggestion

[tuxderlinuxfuch...@gmail.com]

Thanks for the tips. Like I said, I'd prefer a program that does all
this in the background by calling one simple command


On 15-Jun-17 4:38 PM, David Wright wrote:
> On Thu 15 Jun 2017 at 10:16:45 (-0400), Dan Ritter wrote:
>> On Wed, Jun 14, 2017 at 09:57:50PM +0200, tuxderlinuxfuch...@gmail.com wrote:
>>> The shown way is not very comfortable.
>>>
>>> 1. it is annoying having to remember IP addresses
>>> 2. sed command is error prone (consider typos, etc.)
>>> 3. copying around backup files is time consuming having to type in all
>>> the paths
>>> 4. typing in sed command or searching it in bash history for re-using is
>>> time consuming, too.
>>>
>> Simple workaround for now:
>>
>> /etc/apt/sources.list:
>> 
>> deb http://site1.ip.address/debian jessie-backports main
>> #deb http://site2.ip.address/debian jessie-backports main
>> 
>>
>> Now just change the comment from one to the other, run apt-get
>> update and go.
>>
>> Second workaround, if you have lots of entries to be switched:
>> create two sources.list files, named home.list and uni.list.
>>
>> When you move from place to place, copy the appropriate one 
>> in to /etc/apt/sources.list and run apt-get update.
> Another workaround is to use bash functions, say upgrade-work and
> upgrade-home, to wrap some rather long command lines like:
>
> apt-get -o Acquire::http::Proxy="http://192.168.1.19:3142/"; update && apt-get 
> -d -o Acquire::http::Proxy="http://192.168.1.19:3142/"; upgrade ; apt-get 
> upgrade
>
> Now you may well ask why I use such a crazy command line.
> Answer, I run apt-cacher-ng on my wheezy server, BUT
> proxying the actual upgrade step fails because wheezy can't
> handle apt-listbugs, so I do that step directly. The long
> command line saves messing with apt.conf or sources.list.
>
> Cheers,
> David.
>

Re: apt-cacher-ng related program and package suggestion

[Bob Weber]

> Simple workaround for now:
>
> /etc/apt/sources.list:
> 
> deb http://site1.ip.address/debian jessie-backports main
> #deb http://site2.ip.address/debian jessie-backports main
> 
>
> Now just change the comment from one to the other, run apt-get
> update and go.
>
> Second workaround, if you have lots of entries to be switched:
> create two sources.list files, named home.list and uni.list.
>
> When you move from place to place, copy the appropriate one 
> in to /etc/apt/sources.list and run apt-get update.
>
> -dsr-
>
Its even easier than that.  Don't mess with the .list files just change  the 
file

/etc/apt/apt.conf.d/000apt-cacher-ng-proxy

according to the login.

The contents of that file is just the address/port of the apt-cacher-ng server.

Acquire::http::Proxy "http://172.16.0.1:3142/";;

Just write a script to check what network you are on.  Like ping the
apt-cacher-ng server(s) until a response is sent and set 
/etc/apt/apt.conf.d/000apt-cacher-ng-proxy accordingly.

Try the following line with your own existing and non existing ips.

for f in 172.16.0.1 172.16.0.2 172.16.0.33; do if ping -c3 $f; then echo $f
yes;else echo $f no;fi; done

bob

Re: apt-cacher-ng related program and package suggestion

[David Wright]

On Thu 15 Jun 2017 at 10:16:45 (-0400), Dan Ritter wrote:
> On Wed, Jun 14, 2017 at 09:57:50PM +0200, tuxderlinuxfuch...@gmail.com wrote:
> > The shown way is not very comfortable.
> > 
> > 1. it is annoying having to remember IP addresses
> > 2. sed command is error prone (consider typos, etc.)
> > 3. copying around backup files is time consuming having to type in all
> > the paths
> > 4. typing in sed command or searching it in bash history for re-using is
> > time consuming, too.
> > 
> 
> Simple workaround for now:
> 
> /etc/apt/sources.list:
> 
> deb http://site1.ip.address/debian jessie-backports main
> #deb http://site2.ip.address/debian jessie-backports main
> 
> 
> Now just change the comment from one to the other, run apt-get
> update and go.
> 
> Second workaround, if you have lots of entries to be switched:
> create two sources.list files, named home.list and uni.list.
> 
> When you move from place to place, copy the appropriate one 
> in to /etc/apt/sources.list and run apt-get update.

Another workaround is to use bash functions, say upgrade-work and
upgrade-home, to wrap some rather long command lines like:

apt-get -o Acquire::http::Proxy="http://192.168.1.19:3142/"; update && apt-get 
-d -o Acquire::http::Proxy="http://192.168.1.19:3142/"; upgrade ; apt-get upgrade

Now you may well ask why I use such a crazy command line.
Answer, I run apt-cacher-ng on my wheezy server, BUT
proxying the actual upgrade step fails because wheezy can't
handle apt-listbugs, so I do that step directly. The long
command line saves messing with apt.conf or sources.list.

Cheers,
David.

Re: apt-cacher-ng related program and package suggestion

[Darac Marjal]

On Thu, Jun 15, 2017 at 10:16:45AM -0400, Dan Ritter wrote:

On Wed, Jun 14, 2017 at 09:57:50PM +0200, tuxderlinuxfuch...@gmail.com wrote:

The shown way is not very comfortable.

1. it is annoying having to remember IP addresses
2. sed command is error prone (consider typos, etc.)
3. copying around backup files is time consuming having to type in all
the paths
4. typing in sed command or searching it in bash history for re-using is
time consuming, too.



Simple workaround for now:

/etc/apt/sources.list:

deb http://site1.ip.address/debian jessie-backports main
#deb http://site2.ip.address/debian jessie-backports main


Now just change the comment from one to the other, run apt-get
update and go.

Second workaround, if you have lots of entries to be switched:
create two sources.list files, named home.list and uni.list.

When you move from place to place, copy the appropriate one
in to /etc/apt/sources.list and run apt-get update.


Of course, if site1 and site2 are not accessible from each other AND
you're willing to accept errors from apt, you can keep both enabled. apt
will complain that it can't update some repositories, but as both
provide the same packages, that's not a problem.



-dsr-



--
For more information, please reread.


signature.asc
Description: PGP signature

Re: apt-cacher-ng related program and package suggestion

[Dan Ritter]

On Wed, Jun 14, 2017 at 09:57:50PM +0200, tuxderlinuxfuch...@gmail.com wrote:
> The shown way is not very comfortable.
> 
> 1. it is annoying having to remember IP addresses
> 2. sed command is error prone (consider typos, etc.)
> 3. copying around backup files is time consuming having to type in all
> the paths
> 4. typing in sed command or searching it in bash history for re-using is
> time consuming, too.
> 

Simple workaround for now:

/etc/apt/sources.list:

deb http://site1.ip.address/debian jessie-backports main
#deb http://site2.ip.address/debian jessie-backports main


Now just change the comment from one to the other, run apt-get
update and go.

Second workaround, if you have lots of entries to be switched:
create two sources.list files, named home.list and uni.list.

When you move from place to place, copy the appropriate one 
in to /etc/apt/sources.list and run apt-get update.

-dsr-

Re: apt-cacher-ng related program and package suggestion

[Yvan Masson]

Le 15/06/2017 à 04:51, Andy Smith a écrit :
> Hello,
> 
> On Wed, Jun 14, 2017 at 09:57:50PM +0200, tuxderlinuxfuch...@gmail.com wrote:
>> apt-cacher-switch add  :>
>> apt-cacher-switch add  :>
>>
>> Then at university:
>> apt-cacher-switch enable 
>>
>> At home:
>> apt-cacher-switch enable 
>>
>> In an environment where no cacher is on the network
>> apt-cacher-switch disable
> 
> Seems like it would be easier to install squid-deb-proxy-client on
> each client machine. This listens for Avahi announcements of
> _apt_proxy._tcp to choose a proxy.
> 
> Normally your server(s) would run package squid-deb-proxy (an
> install of squid customised for caching Debian packages) which takes
> care of announcing its presence over Avahi, but you can make your
> own announcements that point at your own installs of apt-cacher-ng
> if you like.
> 
> If nothing is being announced then squid-deb-proxy-client goes
> direct to Debian mirrors.
> 
> That way this all works without having to run any commands on the
> client depending on where the client machine is located.
> 
> One downside is that if a broken proxy announces itself then your
> clients will use it, i.e. you don't have any control over whether
> the proxy is used or not.
> 
> Cheers,
> Andy
> 

Another solution whichi does not depend of the server software (squid or
apt-cacher-ng) is to use this directive on the client:
Acquire::http::Proxy-Auto-Detect

I could not find a good example in English, but here is one in French.
Obviously, man 5 apt.conf also explains it.

Regards,
Yvan



signature.asc
Description: OpenPGP digital signature

Re: apt-cacher-ng related program and package suggestion

[Andy Smith]

Hello,

On Wed, Jun 14, 2017 at 09:57:50PM +0200, tuxderlinuxfuch...@gmail.com wrote:
> apt-cacher-switch add  :>
> apt-cacher-switch add  :>
> 
> Then at university:
> apt-cacher-switch enable 
> 
> At home:
> apt-cacher-switch enable 
> 
> In an environment where no cacher is on the network
> apt-cacher-switch disable

Seems like it would be easier to install squid-deb-proxy-client on
each client machine. This listens for Avahi announcements of
_apt_proxy._tcp to choose a proxy.

Normally your server(s) would run package squid-deb-proxy (an
install of squid customised for caching Debian packages) which takes
care of announcing its presence over Avahi, but you can make your
own announcements that point at your own installs of apt-cacher-ng
if you like.

If nothing is being announced then squid-deb-proxy-client goes
direct to Debian mirrors.

That way this all works without having to run any commands on the
client depending on where the client machine is located.

One downside is that if a broken proxy announces itself then your
clients will use it, i.e. you don't have any control over whether
the proxy is used or not.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

apt-cacher-ng related program and package suggestion

[tuxderlinuxfuch...@gmail.com]

Hello,

I have a suggestion for a client program/package in combination with
apt-cacher-ng

Consider following situation:

User U_A has a laptop which he uses at home and at university

He has a poor internet connection in both places.

So he set up apt-cacher-ng services in both places but they are on
different networks (he does not have permission to change the network
settings at university to make the IP addresses of the apt-cacher-ng
servers math)

Lets say at home the server HOST_1 is http://192.168.1.100:3142
At university: server: HOST_2: http://192.168.76.56:3142

He uses Ubuntu (so this should work for Debian in a similar way).

He makes a backup "/etc/apt/sources.list.bak" of /etc/apt/sources.list

At university he sets up the cache repo as follows (after overwriting
the /etc/apt/sources.list with a copy of the backup if it was changed to
use the home apt-cacher-ng)

sed -i 's/de.archive.ubuntu.com/192.168.76.56:3142/g' /etc/apt/sources.list

The same procedure at home.

The shown way is not very comfortable.

1. it is annoying having to remember IP addresses
2. sed command is error prone (consider typos, etc.)
3. copying around backup files is time consuming having to type in all
the paths
4. typing in sed command or searching it in bash history for re-using is
time consuming, too.

What I would like is to setup all cachers one use a program (lets call
it apt-cacher-switch for now)

apt-cacher-switch add  :>
apt-cacher-switch add  :>

Then at university:
apt-cacher-switch enable 

At home:
apt-cacher-switch enable 

In an environment where no cacher is on the network
apt-cacher-switch disable

The apt-cacher switch should manage creating and copying around the
required /etc/apt/sources.list files.

As I am not very talented in C/C++ programming under Linux, I am asking
the community to make it happen.
I would be very happy if this could be implemented and the package be
added to the official Debian and Ubuntu (and other derivates') repositories.

Best regards

Chris

apt-cacher-ng ""500 Bad redirection (path)" - some debugging info

[Brian Candler]

I have been observing intermittent "500 Bad redirection (path)" errors
from apt-cacher-ng. This is something which appears to have been reported
before but not resolved: e.g.
https://lists.debian.org/debian-user/2015/03/msg00877.html

However I have been able to capture some information, including tcpdumps
of traffic in and out of apt-cacher-ng, which might help.

* Client node (10.10.10.18) is Debian Wheezy

Here's what's seen on the client:

root@node18:~# apt-get update
Hit http://security.debian.org wheezy/updates Release.gpg
Ign http://ftp.uk.debian.org wheezy Release.gpg
Hit http://security.debian.org wheezy/updates Release
Ign http://ftp.uk.debian.org wheezy-updates Release.gpg
Hit http://security.debian.org wheezy/updates/main Sources
Ign http://ftp.uk.debian.org wheezy Release
Hit http://security.debian.org wheezy/updates/contrib Sources
Ign http://ftp.uk.debian.org wheezy-updates Release
Hit http://security.debian.org wheezy/updates/non-free Sources
Hit http://security.debian.org wheezy/updates/main amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib amd64 Packages
Hit http://security.debian.org wheezy/updates/non-free amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib Translation-en
Hit http://security.debian.org wheezy/updates/main Translation-en
Hit http://security.debian.org wheezy/updates/non-free Translation-en
Err http://ftp.uk.debian.org wheezy/main Sources
  500  Bad redirection (path)
Err http://ftp.uk.debian.org wheezy/contrib Sources
  500  Bad redirection (path)
Err http://ftp.uk.debian.org wheezy/non-free Sources
  500  Bad redirection (path)
Err http://ftp.uk.debian.org wheezy/main amd64 Packages
  500  Bad redirection (path)
Err http://ftp.uk.debian.org wheezy/contrib amd64 Packages
  500  Bad redirection (path)
Err http://ftp.uk.debian.org wheezy/non-free amd64 Packages
  500  Bad redirection (path)
Ign http://ftp.uk.debian.org wheezy/contrib Translation-en_US
Ign http://ftp.uk.debian.org wheezy/contrib Translation-en
Ign http://ftp.uk.debian.org wheezy/main Translation-en_US
Ign http://ftp.uk.debian.org wheezy/main Translation-en
Ign http://ftp.uk.debian.org wheezy/non-free Translation-en_US
Ign http://ftp.uk.debian.org wheezy/non-free Translation-en
Err http://ftp.uk.debian.org wheezy-updates/main Sources
  500  Bad redirection (path)
Err http://ftp.uk.debian.org wheezy-updates/contrib Sources
  500  Bad redirection (path)
Err http://ftp.uk.debian.org wheezy-updates/non-free Sources
  500  Bad redirection (path)
Err http://ftp.uk.debian.org wheezy-updates/main amd64 Packages
  500  Bad redirection (path)
Err http://ftp.uk.debian.org wheezy-updates/contrib amd64 Packages
  500  Bad redirection (path)
Err http://ftp.uk.debian.org wheezy-updates/non-free amd64 Packages
  500  Bad redirection (path)
Ign http://ftp.uk.debian.org wheezy-updates/contrib Translation-en_US
Ign http://ftp.uk.debian.org wheezy-updates/contrib Translation-en
Ign http://ftp.uk.debian.org wheezy-updates/main Translation-en_US
Ign http://ftp.uk.debian.org wheezy-updates/main Translation-en
Ign http://ftp.uk.debian.org wheezy-updates/non-free Translation-en_US
Ign http://ftp.uk.debian.org wheezy-updates/non-free Translation-en
W: Failed to fetch 
http://ftp.uk.debian.org/debian/dists/wheezy/main/source/Sources 500  
Bad redirection (path)


W: Failed to fetch 
http://ftp.uk.debian.org/debian/dists/wheezy/contrib/source/Sources 500  
Bad redirection (path)


W: Failed to fetch 
http://ftp.uk.debian.org/debian/dists/wheezy/non-free/source/Sources 
500  Bad redirection (path)


W: Failed to fetch 
http://ftp.uk.debian.org/debian/dists/wheezy/main/binary-amd64/Packages 
500  Bad redirection (path)


W: Failed to fetch 
http://ftp.uk.debian.org/debian/dists/wheezy/contrib/binary-amd64/Packages 
500  Bad redirection (path)


W: Failed to fetch 
http://ftp.uk.debian.org/debian/dists/wheezy/non-free/binary-amd64/Packages 
500  Bad redirection (path)


W: Failed to fetch 
http://ftp.uk.debian.org/debian/dists/wheezy-updates/main/source/Sources 
500  Bad redirection (path)


W: Failed to fetch 
http://ftp.uk.debian.org/debian/dists/wheezy-updates/contrib/source/Sources 
500  Bad redirection (path)


W: Failed to fetch 
http://ftp.uk.debian.org/debian/dists/wheezy-updates/non-free/source/Sources 
500  Bad redirection (path)


W: Failed to fetch 
http://ftp.uk.debian.org/debian/dists/wheezy-updates/main/binary-amd64/Packages 
500  Bad redirection (path)


W: Failed to fetch 
http://ftp.uk.debian.org/debian/dists/wheezy-updates/contrib/binary-amd64/Packages 
500  Bad redirection (path)


W: Failed to fetch 
http://ftp.uk.debian.org/debian/dists/wheezy-updates/non-free/binary-amd64/Packages 
500  Bad redirection (path)


E: Some index files failed to download. They have been ignored, or old 
ones used instead.


* Configuration of the client node

=== /etc/apt/sources.list ===
deb http://ftp.uk.debian.org/debian wheezy main contrib non-free
deb-src http://ftp.uk.debi

Re: apt-cacher-ng not expiring any more

[David Wright]

Quoting Wolfgang Karall (lists+debian-u...@karall-edv.at):
> On 15-09-11 11:06:58, David Wright wrote:
> > The wheezy-backports-sloppy version, 0.8.3-1~bpo7+1 (i386) worked
> > well, but only until Sept 5/6; on this occasion, the disppearing file
> > is debrep/dists/jessie/InRelease:
> > 
> > Bringing index files up to date...
> > Checking/Updating debrep/dists/jessie/InRelease... 404 Not Found
> 
> Faced with the same problem, it seems removing the files that acng is
> complaining about from the local cache hierarchy stops it from trying to
> refresh it.
> 
> This even worked with the backports (non-sloppy) version AFAICT.

Yes, I can confirm that, having just downgraded to it first.

Normally if there are problems I get an email:

--✂
Subject: Anacron job 'cron.daily' on alum

/etc/cron.daily/apt-cacher-ng:
Error(s) occured while updating volatile index files for apt-cacher-ng.
Please visit http://alum:3142/acng-report.html to rerun the
expiration manually or check the error message(s) in the current log file(s).

Please check error messages in one of: 
/var/log/apt-cacher-ng/maint_1441883138.log.html
+/var/log/apt-cacher-ng/maint_1441802104.log.html 
/var/log/apt-cacher-ng/maint_1441715703.log.html
+/var/log/apt-cacher-ng/maint_1441623938.log.html 
/var/log/apt-cacher-ng/maint_1441537538.log.html
--✂

Normally I look at the log file because I'm not seated at the machine.
Having just made a repeated attempt at expiration with the browser at
http://alum:3142/acng-report.html
I noticed that each error 404 line here is followed by a checkbox for
tagging it, and there's a delete button at the bottom. Tagging and
deleting these files fixed it: 3 GB will be saved.

Thanks. Note to self—use the browser interface.

Cheers,
David.

Re: apt-cacher-ng not expiring any more

[Wolfgang Karall]

Hi David,

On 15-09-11 11:06:58, David Wright wrote:
> The wheezy-backports-sloppy version, 0.8.3-1~bpo7+1 (i386) worked
> well, but only until Sept 5/6; on this occasion, the disppearing file
> is debrep/dists/jessie/InRelease:
> 
> Bringing index files up to date...
> Checking/Updating debrep/dists/jessie/InRelease... 404 Not Found

Faced with the same problem, it seems removing the files that acng is
complaining about from the local cache hierarchy stops it from trying to
refresh it.

This even worked with the backports (non-sloppy) version AFAICT.

Cheers
Wolfgang


signature.asc
Description: Digital signature

Re: apt-cacher-ng not expiring any more

[David Wright]

Quoting Eduard Bloch (e...@gmx.de):
> * David Wright [Tue, Aug 25 2015, 11:00:41AM]:
> > Running apt-cacher-ng on wheezy (with wheezy-backports), some missing
> > files in the repository are making the expiration step fail. Here are
> > the relevant lines from the log:
> > 
> > Checking/Updating 
> > debrep/dists/jessie-backports/main/binary-i386/Packages.bz2...
> > 404 Not Found
> ...

> There is a newer BPO version where this problem should be fixed.
> 
> > [Re missing .bz2 files]
> 
> They were removed from mirrors because, well, they are not necessary and
> Jessie can work with .xz versions. However, apt-cacher-ng fails to
> accomodate to this fact and will try to get the zombie versions. As
> said, there is a workaround in a newer version.

The wheezy-backports-sloppy version, 0.8.3-1~bpo7+1 (i386) worked
well, but only until Sept 5/6; on this occasion, the disppearing file
is debrep/dists/jessie/InRelease:

Bringing index files up to date...
Checking/Updating debrep/dists/jessie/InRelease... 404 Not Found
Checking/Updating debrep/dists/jessie-backports/InRelease... (161KiB)
Checking/Updating debrep/dists/jessie-updates/InRelease... (138KiB)
Checking/Updating debrep/dists/jessie/main/binary-i386/Release... (0KiB)
Checking/Updating debrep/dists/sid/InRelease... (241KiB)
Checking/Updating debrep/dists/stable/Release... (144KiB)
Checking/Updating debrep/dists/testing/Release... (151KiB)
Checking/Updating debrep/dists/wheezy/Release... (0KiB)
Checking/Updating debrep/dists/wheezy-backports/Release... (163KiB)
Checking/Updating debrep/dists/wheezy-backports-sloppy/Release... (154KiB)
Checking/Updating debrep/dists/wheezy-updates/Release... (147KiB)
Checking/Updating debrep/dists/wheezy/main/binary-i386/Release... (0KiB)
Checking/Updating security.debian.org/dists/jessie/updates/InRelease... (0KiB)
Checking/Updating security.debian.org/dists/wheezy/updates/Release... (0KiB)
Found errors during processing, aborting as requested.

AFAICT InRelease is just a combination of Release with its Release.gpg
included at the end of the file. Once again, I'm not sure if I should
be carrying out some administrative step, or if it's just that
apt-cacher-ng doesn't have the flexibility to cope with what are
really quite minor changes to the Debian archive. After all, it's
obviously quite capable of handling both InRelease and
Release/Release.gpg but behaves like a starving man who refuses to eat
because the food is now offered in a bowl instead of on a plate.

Cheers,
David.

Re: apt-cacher-ng not expiring any more

[David Wright]

Quoting Eduard Bloch (e...@gmx.de):
> * David Wright [Tue, Aug 25 2015, 11:00:41AM]:
> > Running apt-cacher-ng on wheezy (with wheezy-backports), some missing
> > files in the repository are making the expiration step fail. Here are
> > the relevant lines from the log:
> > 
> > Checking/Updating 
> > debrep/dists/jessie-backports/main/binary-i386/Packages.bz2...
> > 404 Not Found
> ...

> There is a newer BPO version where this problem should be fixed.

Thanks. I hadn't realised this because I wasn't using
wheezy-backports-sloppy as well as wheezy-backports itself.

> [Re missing .bz2 files]

> They were removed from mirrors because, well, they are not necessary and
> Jessie can work with .xz versions.

That's fine. I realised the .xz ones were probably newer because they
were the ones that the pure wheezy version couldn't parse.

Cheers,
David.

Re: apt-cacher-ng not expiring any more

[Eduard Bloch]

Hallo,
* David Wright [Tue, Aug 25 2015, 11:00:41AM]:
> Running apt-cacher-ng on wheezy (with wheezy-backports), some missing
> files in the repository are making the expiration step fail. Here are
> the relevant lines from the log:
> 
> Checking/Updating 
> debrep/dists/jessie-backports/main/binary-i386/Packages.bz2...
> 404 Not Found
...
> As I don't understand why there are Packages.bz2, Packages.xz and
> Packages.gz files variously scattered throughout debrep, I'm not sure
> whether this problem is a failure to maintain debrep or a bug in
> apt-cacher-ng (version 0.8.0-3~bpo70+2) whose fix hasn't been backported.

There is a newer BPO version where this problem should be fixed.

> Anyone else noticed this? If you're running under jessie, does it
> fail, does it skip those .bz2 files without complaining, or does it
> just use one of its companion files (.xz or .gz as available)?

They were removed from mirrors because, well, they are not necessary and
Jessie can work with .xz versions. However, apt-cacher-ng fails to
accomodate to this fact and will try to get the zombie versions. As
said, there is a workaround in a newer version.

Regards,
Eduard.

-- 
Das Positive am Skeptiker ist, daß er alles für möglich hält.
-- Thomas Mann

apt-cacher-ng not expiring any more

[David Wright]

Running apt-cacher-ng on wheezy (with wheezy-backports), some missing
files in the repository are making the expiration step fail. Here are
the relevant lines from the log:

Checking/Updating debrep/dists/jessie-backports/main/binary-i386/Packages.bz2...
404 Not Found
Checking/Updating 
debrep/dists/jessie-updates/contrib/binary-i386/Packages.bz2...
404 Not Found
Checking/Updating 
debrep/dists/jessie-updates/non-free/binary-i386/Packages.bz2...
404 Not Found
Checking/Updating 
debrep/dists/jessie-backports/non-free/binary-i386/Packages.bz2...
404 Not Found
Found errors during processing, aborting as requested.

The problem started in the 24hrs before Sat, 22 Aug 2015 06:07:13 -0500.

As I don't understand why there are Packages.bz2, Packages.xz and
Packages.gz files variously scattered throughout debrep, I'm not sure
whether this problem is a failure to maintain debrep or a bug in
apt-cacher-ng (version 0.8.0-3~bpo70+2) whose fix hasn't been backported.

If I change my sources.list to uk instead of us, I get the same
problem, so if it's debrep's fault I suppose it must be being
replicated during mirroring.

Anyone else noticed this? If you're running under jessie, does it
fail, does it skip those .bz2 files without complaining, or does it
just use one of its companion files (.xz or .gz as available)?

Cheers,
David.

Re: apt-cacher-ng and apt-get changelog result in http 500 error

[David Wright]

Quoting Bernd Naumann (be...@kr217.de):

> I can't use `apt-get changelog` while have `apt-cacher-ng` running,
> which is really annoying.
> 
> I.e.:
> ```
> apt-get changelog screen
> Err Changelog for screen
> (http://packages.debian.org/changelogs/pool/main/s/screen/screen_4.1.0~2
> 0120320gitdb59704-7/changelog)
>   500  Bad redirection (invalid URL)
> Err Changelog for screen
> (http://ftp.de.debian.org/debian/pool/main/s/screen/screen_4.1.0~2012032
> 0gitdb59704-7.changelog)
>   404  Not Found
> E: changelog download failed
> ```

I can't reproduce this. Here's the output for an installed and an
uninstalled package on my laptop (jessie) and my apt-cacher-ng box
(wheezy).

$ apt-get changelog sed
Get:1 Changelog for sed
(http://packages.debian.org/changelogs/pool/main/s/sed/sed_4.2.2-4/changelog)
[19.1 kB]
Fetched 19.1 kB in 1s (10.1 kB/s)
$ apt-get changelog bless
Get:1 Changelog for bless
(http://packages.debian.org/changelogs/pool/main/b/bless/bless_0.6.0-4/changelog)
[2,713 B]
Fetched 2,713 B in 1s (1,920 B/s)
$

$ apt-get changelog sed
Get:1 Changelog for sed
(http://packages.debian.org/changelogs/pool/main/s/sed/sed_4.2.1-10/changelog)
[18.3 kB]
Fetched 18.3 kB in 1s (9,854 B/s)
$ apt-get changelog a2ps
Get:1 Changelog for a2ps
(http://packages.debian.org/changelogs/pool/main/a/a2ps/a2ps_4.14-1.1+deb7u1/changelog)
[26.8 kB]
Fetched 26.8 kB in 1s (15.5 kB/s)
$

So it looks like something might be misconfigured somewhere.

My /etc/apt/apt.conf contains

Acquire::http::Proxy "http://192.168.1.19:3142/";;

Sources files are

deb http://ftp.us.debian.org/debian/ jessie main contrib non-free
deb-src http://ftp.us.debian.org/debian/ jessie main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
deb http://ftp.us.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.us.debian.org/debian/ jessie-updates main contrib non-free

and

deb http://ftp.us.debian.org/debian/ wheezy main non-free contrib
deb-src http://ftp.us.debian.org/debian/ wheezy main non-free contrib
deb http://security.debian.org/ wheezy/updates main contrib non-free
deb-src http://security.debian.org/ wheezy/updates main contrib non-free
deb http://ftp.us.debian.org/debian/ wheezy-updates main contrib non-free
deb-src http://ftp.us.debian.org/debian/ wheezy-updates main contrib non-free

Or another possibilty: I'm running the apt-cacher-ng version from
wheezy-backports, otherwise I get problems expiring the post-wheezy
packages.

Cheers,
David.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150321203828.gb22...@alum.home

apt-cacher-ng and apt-get changelog result in http 500 error

[Bernd Naumann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi at all,

I can't use `apt-get changelog` while have `apt-cacher-ng` running,
which is really annoying.

I.e.:
```
apt-get changelog screen
Err Changelog for screen
(http://packages.debian.org/changelogs/pool/main/s/screen/screen_4.1.0~2
0120320gitdb59704-7/changelog)
  500  Bad redirection (invalid URL)
Err Changelog for screen
(http://ftp.de.debian.org/debian/pool/main/s/screen/screen_4.1.0~2012032
0gitdb59704-7.changelog)
  404  Not Found
E: changelog download failed
```

I have taken a look at other apt caching tools (for local networks),
but the most pleasing feature of apt-cacher-ng is, that I don't have
to do a full mirror, which will be atm not possible or configure
specify mirror-/archive-urls in a config file.
I often work mobil on my notebook and I need more then one
architecture in my cache.

So I'm look ether for a workaround or recommendation for an other
tool, which does the same as apt-cacher-ng, which I have my be overlooke
d.

Thanks for replys and hints!
Best regards,
Bernd

- -- 
Bernd Naumann 

PGP:   0xA150A04F via pool.sks-keyservers.net
XMPP:  b...@weimarnetz.de

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJVDajnAAoJEEYW3OihUKBPFe4QAI3EwNoObt7As8cEVididnfP
jDhHa5UEaTBODnVWSbJ6P6BCEBEs1qPVZszYbkPwZcYF5VnAc0kFazlDGu+LilTc
nE5lBe6dFOH/ZeJ4fD/Un6Bgqwe0VO/QtkZ3JE5BZFxPHJ1tujHI2xQtk8aHHrsL
RV/CL94WyEFvPC7FbcSeM9hB9ozfRUuo6bslV0Wlt76lDqBDJWrG2JCGCYrtuRQl
iGOhtwqI2QT0X2M4cBOY1HWBCW7Ul3smOcy8kl8zp+OhDXCLEP/XnlTKwcDCN5mX
ZwRnlOsvrx4EyDer6sASuZNi2IVsW7vZsWLeIZhpa09J+m5/J86Ye72DUT6w2Q0A
AOy2LN3skLNvF6Jj3Cx6UNSrKHUuRpyaB0b7vYihpRQ+Mz5p8ZjeaFOuiHU4KkiM
ZHILwQ9QWKJ+xckUa7TKlIDPwrx3fPOqivMR5AAy46p8q9wrC6AHN4OPhqP4kxx+
eKc62VbUppXu+6acQx88K5Nkgd2CPuJw24e3kHooYfVKrhayxHAuxGaUDrsAenoy
wXjCL04ybj7jlGD9p0zCfvoEArfNx204P/NwIiNVTB7dyze6mtFO5hE6JZDE2YuJ
XAHiEm7OIvCU/3lnJM68eYbWlWUtfKUhVPLTbLjf6fgZIGUuepaREr1UHS4bfjTj
0OG/pG76/kzYiIWX5/cJ
=m0Xf
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/550da8e8.90...@kr217.de

Re: Solved. Re: Debian Wheezy 7.4 apt-cacher can only access from localhost

[Scott Ferguson]

On 20/03/14 15:41, Rick McCombs AD5DU wrote:
> On Wed, Mar 19, 2014 at 6:03 PM, Scott Ferguson
>  wrote:
>> On 20/03/14 06:41, Rick McCombs AD5DU wrote:
>>> On Wed, Mar 19, 2014 at 2:36 AM, Scott Ferguson
>>>  wrote:
>>>> On 19/03/14 18:18, Rick McCombs AD5DU wrote:
>>>>> I installed Debian Wheezy 7.4 on my Tower and my laptop.
>>>>> I installed apt-cacher on the tower and it work when I use it from 
>>>>> localhost.
>>>>

>>>
>>> It is commented out but that is supposed to be the default.
>>
>> The default is *not* to allow access from all hosts.
>>
>> Uncomment that last quoted line, or add a line:-
>> allowed_hosts=$my_subnet   (replace that with the actual subnet)
>> OR
>> allowed_hosts=$my_laptop (replace that with the static IP address of
>> your laptop)
>> OR just uncomment it and rely on no port forwarding from your firewall
>> to restrict connections to your LAN
>>
> 
> That worked I guess I miss-read it. Thanks for you help.
> 
> 
> 
No worries.
The default, as is standard with Debian packages, is secure. For that
reason allowing allhosts is, trivially, disabled.

Kind regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/532a851b.9090...@gmail.com

Solved. Re: Debian Wheezy 7.4 apt-cacher can only access from localhost

[Rick McCombs AD5DU]

On Wed, Mar 19, 2014 at 6:03 PM, Scott Ferguson
 wrote:
> On 20/03/14 06:41, Rick McCombs AD5DU wrote:
>> On Wed, Mar 19, 2014 at 2:36 AM, Scott Ferguson
>>  wrote:
>>> On 19/03/14 18:18, Rick McCombs AD5DU wrote:
>>>> I installed Debian Wheezy 7.4 on my Tower and my laptop.
>>>> I installed apt-cacher on the tower and it work when I use it from 
>>>> localhost.
>>>
>>> Do you mean "apt-cacher" or "apt-cacher-ng"??
>>
>> apt-cacher.
>>>
>>>> I did not change the default config, which allows connections from any 
>>>> host.
>>>
>>> Are you sure? (Perhaps the default config has changed since I last used
>>> it instead of apt-cacher-ng)
>
> Your belief is incorrect. The default config has not changed (which is
> why I asked you to post it).
>
>>>
>>> Please post the output of:-
>>> $ grep "allowed_hosts" /etc/apt-cacher/apt-cacher.conf
>>
>> root@ricks-hp:~#  grep "allowed_hosts" /etc/apt-cacher/apt-cacher.conf
>> # addresses must be matched by allowed_hosts and not by denied_hosts to be
>> # permitted to use the cache.  Setting allowed_hosts to "*" means "allow all"
>> # hostname.  The corresponding IPv6 options allowed_hosts_6 and 
>> denied_hosts_6
>> # added directly to allowed_hosts and denied_hosts along with IPv4 addresses.
>> #allowed_hosts = *
>
> Thanks
>
>>
>> It is commented out but that is supposed to be the default.
>
> The default is *not* to allow access from all hosts.
>
> Uncomment that last quoted line, or add a line:-
> allowed_hosts=$my_subnet   (replace that with the actual subnet)
> OR
> allowed_hosts=$my_laptop (replace that with the static IP address of
> your laptop)
> OR just uncomment it and rely on no port forwarding from your firewall
> to restrict connections to your LAN
>

That worked I guess I miss-read it. Thanks for you help.



-- 

Amateur Radio AD5DU.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cahax4ow31iwze0htxyrredgwyx0+xrrbnhbd4+kmc4zj6f8...@mail.gmail.com

Re: Debian Wheezy 7.4 apt-cacher can only access from localhost

[Scott Ferguson]

On 20/03/14 06:41, Rick McCombs AD5DU wrote:
> On Wed, Mar 19, 2014 at 2:36 AM, Scott Ferguson
>  wrote:
>> On 19/03/14 18:18, Rick McCombs AD5DU wrote:
>>> I installed Debian Wheezy 7.4 on my Tower and my laptop.
>>> I installed apt-cacher on the tower and it work when I use it from 
>>> localhost.
>>
>> Do you mean "apt-cacher" or "apt-cacher-ng"??
> 
> apt-cacher.
>>
>>> I did not change the default config, which allows connections from any host.
>>
>> Are you sure? (Perhaps the default config has changed since I last used
>> it instead of apt-cacher-ng)

Your belief is incorrect. The default config has not changed (which is
why I asked you to post it).

>>
>> Please post the output of:-
>> $ grep "allowed_hosts" /etc/apt-cacher/apt-cacher.conf
> 
> root@ricks-hp:~#  grep "allowed_hosts" /etc/apt-cacher/apt-cacher.conf
> # addresses must be matched by allowed_hosts and not by denied_hosts to be
> # permitted to use the cache.  Setting allowed_hosts to "*" means "allow all"
> # hostname.  The corresponding IPv6 options allowed_hosts_6 and denied_hosts_6
> # added directly to allowed_hosts and denied_hosts along with IPv4 addresses.
> #allowed_hosts = *

Thanks

> 
> It is commented out but that is supposed to be the default.

The default is *not* to allow access from all hosts.

Uncomment that last quoted line, or add a line:-
allowed_hosts=$my_subnet   (replace that with the actual subnet)
OR
allowed_hosts=$my_laptop (replace that with the static IP address of
your laptop)
OR just uncomment it and rely on no port forwarding from your firewall
to restrict connections to your LAN

> 
> I don't have much time right now. I may try some variations later
> tonight or tomorrow.
> I think I read something on the web about a bug and  disabling ipv6
> was a work around, but I'm not sure.
> I may try it.
> 


It's not a bug.
I suggest you read comments in /etc/apt-cacher/apt-cacher.conf, and if
that isn't clear enough - try "man apt-cacher".


Kind regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/532a223c.8010...@gmail.com

Re: Debian Wheezy 7.4 apt-cacher can only access from localhost

[Scott Ferguson]

On 19/03/14 18:18, Rick McCombs AD5DU wrote:
> I installed Debian Wheezy 7.4 on my Tower and my laptop.
> I installed apt-cacher on the tower and it work when I use it from localhost.

Do you mean "apt-cacher" or "apt-cacher-ng"??


> I did not change the default config, which allows connections from any host.

Are you sure? (Perhaps the default config has changed since I last used
it instead of apt-cacher-ng)

Please post the output of:-
$ grep "allowed_hosts" /etc/apt-cacher/apt-cacher.conf

> I am behind a home gateway and I'm not going to forward the port from
> the outside.
> When I try to connect from my laptop I get the following.
> 
> 
> root@ricks-acer:~# apt-get update



> 
> W: Failed to fetch
> http://debian.uchicago.edu/debian/dists/wheezy-updates/contrib/binary-i386/Packages
>  *403  Access to cache prohibited*
> 
> E: Some index files failed to download. They have been ignored, or old
> ones used instead.
> root@ricks-acer:~#
> 
> 
> 
> 


Log emphasis mine.

Kind regards


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/53294910.4070...@gmail.com

Debian Wheezy 7.4 apt-cacher can only access from localhost

[Rick McCombs AD5DU]

I installed Debian Wheezy 7.4 on my Tower and my laptop.
I installed apt-cacher on the tower and it work when I use it from localhost.
I did not change the default config, which allows connections from any host.
I am behind a home gateway and I'm not going to forward the port from
the outside.
When I try to connect from my laptop I get the following.


root@ricks-acer:~# apt-get update
Ign cdrom://[Debian GNU/Linux 7.4.0 _Wheezy_ - Official i386 DVD
Binary-1 20140208-12:26] wheezy Release.gpg
Ign cdrom://[Debian GNU/Linux 7.4.0 _Wheezy_ - Official i386 DVD
Binary-1 20140208-12:26] wheezy Release
Ign cdrom://[Debian GNU/Linux 7.4.0 _Wheezy_ - Official i386 DVD
Binary-1 20140208-12:26] wheezy/contrib i386 Packages/DiffIndex
Ign cdrom://[Debian GNU/Linux 7.4.0 _Wheezy_ - Official i386 DVD
Binary-1 20140208-12:26] wheezy/main i386 Packages/DiffIndex
Ign cdrom://[Debian GNU/Linux 7.4.0 _Wheezy_ - Official i386 DVD
Binary-1 20140208-12:26] wheezy/contrib Translation-en_US
Ign cdrom://[Debian GNU/Linux 7.4.0 _Wheezy_ - Official i386 DVD
Binary-1 20140208-12:26] wheezy/main Translation-en_US
Ign http://security.debian.org wheezy/updates Release.gpg
Ign http://security.debian.org wheezy/updates Release
Ign http://security.debian.org wheezy/updates/main Sources/DiffIndex
Ign http://security.debian.org wheezy/updates/contrib Sources/DiffIndex
Ign http://security.debian.org wheezy/updates/main i386 Packages/DiffIndex
Ign http://security.debian.org wheezy/updates/contrib i386 Packages/DiffIndex
Err http://security.debian.org wheezy/updates/non-free Sources
  403  Access to cache prohibited
Err http://security.debian.org wheezy/updates/non-free i386 Packages
  403  Access to cache prohibited
Ign http://security.debian.org wheezy/updates/contrib Translation-en_US
Ign http://security.debian.org wheezy/updates/contrib Translation-en
Ign http://security.debian.org wheezy/updates/main Translation-en_US
Ign http://security.debian.org wheezy/updates/main Translation-en
Ign http://security.debian.org wheezy/updates/non-free Translation-en_US
Ign http://security.debian.org wheezy/updates/non-free Translation-en
Err http://security.debian.org wheezy/updates/main Sources
  403  Access to cache prohibited
Err http://security.debian.org wheezy/updates/contrib Sources
  403  Access to cache prohibited
Err http://security.debian.org wheezy/updates/main i386 Packages
  403  Access to cache prohibited
Err http://security.debian.org wheezy/updates/contrib i386 Packages
  403  Access to cache prohibited
Ign http://debian.uchicago.edu wheezy Release.gpg
Ign http://debian.uchicago.edu wheezy-updates Release.gpg
Ign http://debian.uchicago.edu wheezy Release
Ign http://debian.uchicago.edu wheezy-updates Release
Ign http://debian.uchicago.edu wheezy/main Sources/DiffIndex
Ign http://debian.uchicago.edu wheezy/main i386 Packages/DiffIndex
Ign http://debian.uchicago.edu wheezy-updates/main Sources/DiffIndex
Ign http://debian.uchicago.edu wheezy-updates/contrib Sources/DiffIndex
Ign http://debian.uchicago.edu wheezy-updates/main i386 Packages/DiffIndex
Ign http://debian.uchicago.edu wheezy-updates/contrib i386 Packages/DiffIndex
Err http://debian.uchicago.edu wheezy/non-free Sources
  403  Access to cache prohibited
Err http://debian.uchicago.edu wheezy/contrib Sources
  403  Access to cache prohibited
Err http://debian.uchicago.edu wheezy/non-free i386 Packages
  403  Access to cache prohibited
Err http://debian.uchicago.edu wheezy/contrib i386 Packages
  403  Access to cache prohibited
Ign http://debian.uchicago.edu wheezy/contrib Translation-en_US
Ign http://debian.uchicago.edu wheezy/contrib Translation-en
Ign http://debian.uchicago.edu wheezy/main Translation-en_US
Ign http://debian.uchicago.edu wheezy/main Translation-en
Ign http://debian.uchicago.edu wheezy/non-free Translation-en_US
Ign http://debian.uchicago.edu wheezy/non-free Translation-en
Err http://debian.uchicago.edu wheezy-updates/non-free Sources
  403  Access to cache prohibited
Err http://debian.uchicago.edu wheezy-updates/non-free i386 Packages
  403  Access to cache prohibited
Ign http://debian.uchicago.edu wheezy-updates/contrib Translation-en_US
Ign http://debian.uchicago.edu wheezy-updates/contrib Translation-en
Ign http://debian.uchicago.edu wheezy-updates/main Translation-en_US
Ign http://debian.uchicago.edu wheezy-updates/main Translation-en
Ign http://debian.uchicago.edu wheezy-updates/non-free Translation-en_US
Ign http://debian.uchicago.edu wheezy-updates/non-free Translation-en
Err http://debian.uchicago.edu wheezy/main Sources
  403  Access to cache prohibited
Err http://debian.uchicago.edu wheezy/main i386 Packages
  403  Access to cache prohibited
Err http://debian.uchicago.edu wheezy-updates/main Sources
  403  Access to cache prohibited
Err http://debian.uchicago.edu wheezy-updates/contrib Sources
  403  Access to cache prohibited
Err http://debian.uchicago.edu wheezy-updates/main i386 Packages
  403  Access to cache prohibited
Err http://debian.uchicag

Re: Cannot import packages from debian iso to apt-cacher-ng

[Anubhav Yadav]

Can anyone please rectify me. I have got some weird doubts.

I have set up a PXE boot server. It has a forder /srv/tftp and it has
all the required files for PXE install.

I have also installed apt-cacher-ng on that PXE server. And that PXE
server is also acting as a local DHCP server.

So now, what should I do?

1) I should first do this on the PXE server

echo "Acquire::http { Proxy "http://localhost:3142" };" >
/etc/apt/apt.conf.d/90proxy
 and then I should install one client using my bootable usb. But then
how will apt-cacher import all packages from that client?

2) Or instead of step 1 above, should I first mount all the three iso
on the PXE server, create a symlink to the /pool folder to
/var/cache/apt-cacher-ng/_import
and then import packages?

But the above method fails! Don't know why!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/ca+jf9agttxi22cqnq43qwxzhw8xjsrwa+dzzfdz7ioh+qz8...@mail.gmail.com

Re: Cannot import packages from debian iso to apt-cacher-ng

[Anubhav Yadav]

> Then I recommend taking the easy way out.  Just install one machine
> using apt-cacher-ng as a proxy.  Then all of the packages will be
> ready for the next machine.  Install the rest using the proxy and they
> will use the already downloaded files.  It is simple.  It works.

Was it so easy. How did I miss it. So that means I need to set up the
PXE server, install apt-cacher-ng using that server, then install a
client again using that server and apt-cacher-ng will then be ready
for the next machines!! :)

-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/ca+jf9agx2m2m+auaqyrzhsjqqrp97ydrigneivhay0ojt8u...@mail.gmail.com

Re: Cannot import packages from debian iso to apt-cacher-ng

[Bob Proulx]

Anubhav Yadav wrote:
> I installed a 32 bit Debian Wheezy on a PC (One PC in a lab of 24 computers).
> I made it a dhcp PXE server with netboot images of Debian 7 32 bits.
> It worked perfectly and all the 20 computers booted from network with
> the debian installer.

Good for you.

> The only problem was that all the packages had to be retrieved from
> the internet and bandwidth was a problem. So only one computer could
> be properly installed.

Twenty machines will be a lot of duplicated bandwidth.  Good to use a
caching proxy.

> So I tried to look for solutions on how to completely boot the 4.3 GB
> iso from the network, bypassing the internet mirrors completely. I
> asked a question on the debian user lists and was greeted with many
> solutions, among them was the apt-cacher-ng.

I agree.  apt-cacher-ng would be a good solution.  That way you only
download the data once and it is shared among all of the machines.

> So now I wanted to install 64 bit machines on the same lab, and the 32
> bit server being the PXE server.
> 
> So I installed the apt-cacher-ng package. All was set up.
> 
> I mounted my iso file to a location, and created a symlink of the
> /pool folder to /var/cache/apt-cacher-ng/_import folder.

I haven't ever imported into apt-cacher-ng.  I have only used it in
its default proxy mode.  Why don't you try it in the default proxy mode?

> Next I went to localhost:3142/acng-report.html and ran import and it
> gave me the following error:

Must you import from the CD?  You installed one machine okay from the
network.  For that same cost of download you could simply install one
machine using the apt-cacher-ng proxy.  Then all of the files will be
cached.  Then simply install upon the others.  Since they will all be
the same they all will be able to use the shared downloaded files.

> I am no champion of linux, nor of networking. I am just a student,
> trying to learn linux as much as he can, by asking his college to
> shift from windows to linux, and in the process learning the
> fundamentals of networking and linux.

Then I recommend taking the easy way out.  Just install one machine
using apt-cacher-ng as a proxy.  Then all of the packages will be
ready for the next machine.  Install the rest using the proxy and they
will use the already downloaded files.  It is simple.  It works.

Bob


signature.asc
Description: Digital signature

Cannot import packages from debian iso to apt-cacher-ng

[Anubhav Yadav]

I installed a 32 bit Debian Wheezy on a PC (One PC in a lab of 24 computers).
I made it a dhcp PXE server with netboot images of Debian 7 32 bits.
It worked perfectly and all the 20 computers booted from network with
the debian installer.

The only problem was that all the packages had to be retrieved from
the internet and bandwidth was a problem. So only one computer could
be properly installed.

So I tried to look for solutions on how to completely boot the 4.3 GB
iso from the network, bypassing the internet mirrors completely. I
asked a question on the debian user lists and was greeted with many
solutions, among them was the apt-cacher-ng.

So now I wanted to install 64 bit machines on the same lab, and the 32
bit server being the PXE server.

So I installed the apt-cacher-ng package. All was set up.

I mounted my iso file to a location, and created a symlink of the
/pool folder to /var/cache/apt-cacher-ng/_import folder.

Next I went to localhost:3142/acng-report.html and ran import and it
gave me the following error:

Maintenance task (File Import), apt-cacher-ng version: 0.7.11 (Cancel)
Importing from /var/cache/apt-cacher-ng/_import directory.
Scanning local files...
Scanning, found 1 file...
Scanning, found 2 files...
Scanning, found 4 files...
Scanning, found 8 files...
Scanning, found 16 files...
Scanning, found 32 files...
Scanning, found 64 files...
Scanning, found 128 files...
Scanning, found 256 files...
Scanning, found 512 files...
Scanning, found 1024 files...
Scanning, found 2048 files...
No index files detected. Unable to continue, cannot map files to
internal locations.

So I went ahead and tried to grasp the HOWTO for importing from iso,
and it mentioned that you need to run apt-get update before importing
the packages.

Now since I wanted to cache all the 64 bits packages from the iso, I
tweaked my sources.list to point to iso (The hyperlink is a method
given by me on how to use iso's as apt-get repository).

Now when I ran apt-get update it gave me an error that no i386
packages found (made sense since I was running it on 32 bits server,
and looking for amd64 packages).

So as a test, I installed apt-cacher-ng on my laptop running 64 bits
debian, and it gave me the same index error.

I even tried manually copying *deb packages from
/var/cache/apt/archives to /var/cache/apt-cacher-ng/_import folder,
but again same error!

I also tried importing packages from official repositories and again it failed.

I am no champion of linux, nor of networking. I am just a student,
trying to learn linux as much as he can, by asking his college to
shift from windows to linux, and in the process learning the
fundamentals of networking and linux.

Any ideas?



-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/ca+jf9aejfvtigqzhddt6oyekr6ejklztv8p-5v68win993t...@mail.gmail.com

apt-cacher-ng "500 Invalid header" after download some files

[basti]

Hello,

I run the latest Version of apt-cacher-ng on my raspberry.
All the clients in the network run fine expect the raspberry.

I try to configure proxy via /etc/apt/apt.d/02proxy and also in the
source.list
without luck.
I have also try to "regenerate" by remove all files, try a restart of
apt-cacher-ng.



When I run the command a again libsasl2-modules and perhaps the next 2
or 3 packages are "download"
but then it exit also with the same 500 error.


root at raspberrypi
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/apt-cacher-ng-users>:~#
dpkg -l apt-cache*
Desired=Unknown/Install/Remove/Purge/Hold
|/
/Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|// Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
/||// Name   Version  Architecture Description
/+++-==---=========
ii  apt-cacher-ng  0.7.13-1 armhfcaching proxy server for
software
root at raspberrypi
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/apt-cacher-ng-users>:~#

root at raspberrypi
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/apt-cacher-ng-users>:~#
apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  x11-xserver-utils
The following packages will be upgraded:
  base-files curl dbus dbus-x11 isc-dhcp-client isc-dhcp-common krb5-locales
  libcurl3 libcurl3-gnutls libdbus-1-3 libgl1-mesa-dri libgl1-mesa-glx
  libglapi-mesa libgnutls26 libgssapi-krb5-2 libk5crypto3 libkrb5-3
  libkrb5support0 liblapack3 libpcsclite1 libpixman-1-0 libraspberrypi-bin
  libraspberrypi-dev libraspberrypi-doc libraspberrypi0 libreadline5
  libsasl2-2 libsasl2-modules libx11-6 libx11-data libx11-xcb1 libxcb-glx0
  libxcb-render0 libxcb-shape0 libxcb-shm0 libxcb1 libxcursor1 libxext6
  libxfixes3 libxi6 libxinerama1 libxp6 libxrandr2 libxrender1 libxres1
libxt6
  libxtst6 libxv1 libxxf86dga1 libxxf86vm1 munin munin-common munin-doc
  munin-node munin-plugins-core munin-plugins-extra nfs-common
  nfs-kernel-server nginx-common nginx-full omxplayer php5-cgi php5-common
  python-rpi.gpio python3-rpi.gpio raspberrypi-bootloader raspi-config
  raspi-copies-and-fills scratch tasksel tasksel-data tzdata x11-common
  xserver-xorg xserver-xorg-input-all
75 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 21.2 MB/121 MB of archives.
After this operation, 554 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libkrb5support0 armhf 1.10.1+dfsg-5+deb7u1 [46.2 kB]
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libsasl2-modules armhf 2.1.25.dfsg1-6+deb7u1
500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libsasl2-2 armhf 2.1.25.dfsg1-6+deb7u1
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
curl armhf 7.26.0-1+wheezy3
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libcurl3 armhf 7.26.0-1+wheezy3
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libcurl3-gnutls armhf 7.26.0-1+wheezy3
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libdbus-1-3 armhf 1.6.8-1+deb7u1
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libgl1-mesa-dri armhf 8.0.5-4+deb7u2
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libgl1-mesa-glx armhf 8.0.5-4+deb7u2
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libglapi-mesa armhf 8.0.5-4+deb7u2
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libx11-data all 2:1.5.0-1+deb7u1+wheezy
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libxcb1 armhf 1.8.1-2+deb7u1
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libx11-6 armhf 2:1.5.0-1+deb7u1+wheezy
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libx11-xcb1 armhf 2:1.5.0-1+deb7u1+wheezy
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libxcb-glx0 armhf 1.8.1-2+deb7u1
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libxext6 armhf 2:1.3.1-2+deb7u1
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libxfixes3 armhf 1:5.0-4+deb7u1
  500  Invalid header
Err http://127.0.0.1/mirrordirector.raspbian.org/raspbian/ wheezy/main
libxxf86vm1 armhf 1:1.1.2-1+deb7u1
  500  Invalid header
Err http://127.0.0.1/mirrordirec

mozilla.debian.net, apt-cacher, and Squeeze

[Scott Ferguson]

Dear tubers,
please do my homework for me. It's beer o'clock on a warm
Friday afternoon - I considered doing it myself but I'm too lazy.


Boxen running Squeeze with Iceweasel and Icedove from mozilla.debian.net
and a few other backports on networks with and apt-cacher server/s.

Apt-cacher runs in daemon mode with standard settings. Boxen are
directed at the apt-cacher server by /etc/apt/apt.conf.d/50proxy
Where directive is:-
Acquire::http::Proxy "http://[apt-cacher-box]:3142";;

When running apt-get update:-

;All repositories in sources.list generate bzip error warning[*1]
Eg.:-
Get:8 http://security.debian.org/ squeeze/updates/non-free
Translation-en [226 B]
76% [8 Translation-en bzip2 0 B] [Waiting for headers] [Waiting for
headers] [Waitbzip2: (stdin) is not a bzip2 file.

;Mozilla.debian.net repositories *fail* with[*2]:-
Failed to fetch
http://mozilla.debian.net/dists/squeeze-backports/iceweasel-release/binary-i386/Packages.bz2
 Sub-process /bin/bzip2 returned an error code (2)



If apt-cacher is bypassed these errors don't occur.
Changing repositories doesn't change the errors.
No bug reports exist for this in apt-cacher.



Is anyone else having these errors?


Any constructive suggestions for solutions?



[*1] It's actually a gzip file. This error doesn't appear is apt-cacher
is not used. I suspect this may be a 404 handler type error, that bzip
is being looked for and not found, then gzip (or the uncompressed file)
is being used.

[*2] Again - this is actually a gzip file. (The error code indicates a
corrupt archive.)


Cheers

-- 
Iceweasel/Firefox extensions for finding answers to Debian questions:-
https://addons.mozilla.org/en-US/firefox/collections/Scott_Ferguson/debian/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f190ddb.6080...@gmail.com

Re: apt-cacher-ng: Cache storage error while opening data file

[T o n g]

On Wed, 14 Jul 2010 00:04:05 +, T o n g wrote:

> I got the following error when doing "aptitude update":
> 
> Err http://cdn.debian.net testing/main Packages
>   503  Cache storage error while opening data file
> Err http://security.geo.debian.org testing/updates/main Packages
>   404  OK
> 
> What's wrong? How should I fix it?

My own mistake. Fixed it by following, 

How to install and configure Apt-Cacher NG
http://acidborg.wordpress.com/2010/06/24/how-to-install-and-configure-apt-
cacher-ng-on-ubuntu-server-10-04/

-- 
Tong (remove underscore(s) to reply)
  http://xpt.sourceforge.net/techdocs/
  http://xpt.sourceforge.net/tools/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/i1j9ir$gc...@dough.gmane.org

apt-cacher-ng: Cache storage error while opening data file

[T o n g]

Hi,

I got the following error when doing "aptitude update":

Err http://cdn.debian.net testing/main Packages
  503  Cache storage error while opening data file
Err http://security.geo.debian.org testing/updates/main 
Packages
  404  OK

What's wrong? How should I fix it?

Here is details:

I installed apt-cacher-ng on my caching machine, and setup my client side 
file:

$ cat /etc/apt/apt.conf.d/02proxy
Acquire::http { Proxy "http://maroon:3142";; };  

Then run

 aptitude update

from the client. 

BTW, 

 telnet maroon 3142

was able to connect to maroon. 

please help. 

Thanks

-- 
Tong (remove underscore(s) to reply)
  http://xpt.sourceforge.net/techdocs/
  http://xpt.sourceforge.net/tools/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/i1iutk$ge...@dough.gmane.org

Recovered!! (Re: Anyone Care to Critique my Apt Preferences? (was Re: apt-cacher as package rollback buffer))

[Freeman]

On Mon, Feb 22, 2010 at 11:01:44PM +0900, Osamu Aoki wrote:
> 
> Or, just use "sudo dpkg -i old-package.deb" (maybe in chroot).
> 
> Please read "Chapter 2. Debian package management"
> http://www.debian.org/doc/manuals/debian-reference/ch02.en.html
> http://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_rescue_with_the_dpkg_command
> 

(Belatedly) that is good info about dpkg working well in emergencies because
it is low level and can be used from rescue disk to a target system.  I will
probably use that lesson someday.  8O

But I've got the apt-cacher system going now so I know what I have archived,
downloaded once to storage, without bloating my /var partition.  Disk space
can come in handy. :)

-- 
Kind Regards,
Freeman

http://www.debian.org/MailingLists/#codeofconduct


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100302032434.ga13...@europa.office

Re: Anyone Care to Critique my Apt Preferences? (was Re: apt-cacher as package rollback buffer)

[Freeman]

On Sat, Feb 27, 2010 at 09:22:34PM -0500, Celejar wrote:
> On Sat, 27 Feb 2010 09:05:58 -0800
> Freeman  wrote:
> 
> > On Mon, Feb 22, 2010 at 11:01:44PM +0900, Osamu Aoki wrote:
> 
> ...
> 
> > > Osamu
> > 
> > OMG!
> > 
> > Osamu as in "Debian Reference Copyright 2007-2009 Osamu Aoki"?
> > 
> > That was an undertaking.
> > 
> > There is a great deal of clarity in the way the reference is written. 
> > Although it provides extensive technical information, it is very accessible
> > to the beginner becasue of the selection of background information and the
> > carefull way it moves from general to specific.
> > 
> > Thank you so much for that marvelous piece of work.
> 
> He deserves a thank you not merely for the work itself, but also for
> being one of the more helpful members of this list, who often points
> people to the section of the D-R that answers their questions ..
> 

And so he should. It is a great read. Debian wouldn't be the same without
it.

A fun way to learn something is simply to look up answers in the Reference
to questions on a Debian forum, cite the section to the OP and add a thought
or two.

-- 
Kind Regards,
Freeman

http://www.debian.org/MailingLists/#codeofconduct


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100228104359.gb4...@europa.office

Re: Anyone Care to Critique my Apt Preferences? (was Re: apt-cacher as package rollback buffer)

[Celejar]

On Sat, 27 Feb 2010 09:05:58 -0800
Freeman  wrote:

> On Mon, Feb 22, 2010 at 11:01:44PM +0900, Osamu Aoki wrote:

...

> > Osamu
> 
> OMG!
> 
> Osamu as in "Debian Reference Copyright 2007-2009 Osamu Aoki"?
> 
> That was an undertaking.
> 
> There is a great deal of clarity in the way the reference is written. 
> Although it provides extensive technical information, it is very accessible
> to the beginner becasue of the selection of background information and the
> carefull way it moves from general to specific.
> 
> Thank you so much for that marvelous piece of work.

He deserves a thank you not merely for the work itself, but also for
being one of the more helpful members of this list, who often points
people to the section of the D-R that answers their questions ..

Celejar
-- 
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100227212234.362344db.cele...@gmail.com

Re: Recovered!! (was Re: Anyone Care to Critique my Apt Preferences? (was Re: apt-cacher as package rollback buffer))

[Tony Nelson]

On 10-02-27 12:04:08, Freeman wrote:
 ...
> Following the big xserver-org/mesa seg-fault/crash I was at grub
> playing space invaders.
> 
> 1.) I could reach the diversion to maintenance mode where it
> recommended running e2fsck on mounted partitions, which I eventually 
> did, reluctantly.

I would usually either boot from a "rescue" CD (or an installer and 
choose Rescue mode), or add the kernel boot option "forcefsck" along 
with the "ro" option (on both Debian and Red Hat systems).

> 2.) On restart I got up and running with errors flying everywhere,
> missing files and directories and frequent process failures.
 ...

-- 

TonyN.:'   
  '  


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1267294657.51...@localhost.localdomain

Re: Anyone Care to Critique my Apt Preferences? (was Re: apt-cacher as package rollback buffer)

[Freeman]

On Mon, Feb 22, 2010 at 11:01:44PM +0900, Osamu Aoki wrote:
> Hi,
> 
> On Sat, Feb 20, 2010 at 11:41:26AM -0800, Freeman wrote:
> 
> > In which case, I pin the rolled back version to 1001. The preferences file
> > can live on in moderation for the sake of learning.
> 
> Or, just use "sudo dpkg -i old-package.deb" (maybe in chroot).
> 
> Please read "Chapter 2. Debian package management"
> http://www.debian.org/doc/manuals/debian-reference/ch02.en.html
> http://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_rescue_with_the_dpkg_command
> 
> Osamu

OMG!

Osamu as in "Debian Reference Copyright 2007-2009 Osamu Aoki"?

That was an undertaking.

There is a great deal of clarity in the way the reference is written. 
Although it provides extensive technical information, it is very accessible
to the beginner becasue of the selection of background information and the
carefull way it moves from general to specific.

Thank you so much for that marvelous piece of work.

-- 
Kind Regards,
Freeman

http://www.debian.org/MailingLists/#codeofconduct


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100227170558.gc24...@europa.office

Recovered!! (was Re: Anyone Care to Critique my Apt Preferences? (was Re: apt-cacher as package rollback buffer))

[Freeman]

On Mon, Feb 22, 2010 at 11:01:44PM +0900, Osamu Aoki wrote:
> Hi,
> 
> On Sat, Feb 20, 2010 at 11:41:26AM -0800, Freeman wrote:
> > > > My ego may be the more delicately balanced but my system is the more
> > > > precious. :)
> > > 
> > > This squeeze testing cycle has been rough because of major transitions.
> > > My recent upgrade in one of the multiboot setup from stable to unstable
> > > caused unbootable system.
> > > 
> > 
> > Yep. I've never lost a file-system in 7 years of Debian until the
> > xserver-xorg/mesa upgrade.
> 
> Wait... you did not loose file system.  I am writig from ex-unbootable
> system :-)  This is typical unstable situation.  Data are there.  Just a
> broken boot system.
> 
> You just need to boot system with another partition or from live CD and
> chroot into unbootable system after fixing obvious problem like broken
> /etc/resolv.conf.  Then update system with good deb via aptitude in chroot.
> 
> I have had several broken grub/lilo previously, too.  These are easyones
> to fix.
> 

Sorry! Delayed by illness.

Maybe I used the term unbootable too loosely.

Following the big xserver-org/mesa seg-fault/crash I was at grub playing
space invaders.

1.) I could reach the diversion to maintenance mode where it recommended
running e2fsck on mounted partitions, which I eventually did, reluctantly.

2.) On restart I got up and running with errors flying everywhere, missing
files and directories and frequent process failures.

3.) I shutdown (hard) and ran e2fsck from gparted live cd on all partitions,
unmounted--about 15 minutes of fixing inodes, files and directories.

4.) On subsequent boot I could only reach a prompt that asked for a run
level, to which it would reply that there are no processes left in that run
level.



5.) After about 20 minutes it dawned on me that there was no /etc directory!

=8-O

6.) After restoring from a fairly close backup it is running quite well with
some minor glitches that will require maybe reinstalls at worst.

It seems as if the major problem throughout was the degredation, then loss,
of the /etc directory.

Thanks!

-- 
Kind Regards,
Freeman

http://www.debian.org/MailingLists/#codeofconduct


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100227170408.gb24...@europa.office

Re: Anyone Care to Critique my Apt Preferences? (was Re: apt-cacher as package rollback buffer)

[Osamu Aoki]

Hi,

On Sat, Feb 20, 2010 at 11:41:26AM -0800, Freeman wrote:
> > > My ego may be the more delicately balanced but my system is the more
> > > precious. :)
> > 
> > This squeeze testing cycle has been rough because of major transitions.
> > My recent upgrade in one of the multiboot setup from stable to unstable
> > caused unbootable system.
> > 
> 
> Yep. I've never lost a file-system in 7 years of Debian until the
> xserver-xorg/mesa upgrade.

Wait... you did not loose file system.  I am writig from ex-unbootable
system :-)  This is typical unstable situation.  Data are there.  Just a
broken boot system.

You just need to boot system with another partition or from live CD and
chroot into unbootable system after fixing obvious problem like broken
/etc/resolv.conf.  Then update system with good deb via aptitude in chroot.

I have had several broken grub/lilo previously, too.  These are easyones
to fix.

> In which case, I pin the rolled back version to 1001. The preferences file
> can live on in moderation for the sake of learning.

Or, just use "sudo dpkg -i old-package.deb" (maybe in chroot).

Please read "Chapter 2. Debian package management"
http://www.debian.org/doc/manuals/debian-reference/ch02.en.html
http://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_rescue_with_the_dpkg_command

Osamu


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100222140143.gb5...@osamu.debian.net

Re: Anyone Care to Critique my Apt Preferences? (was Re: apt-cacher as package rollback buffer)

[Freeman]

On Sat, Feb 20, 2010 at 06:41:35PM +0900, Osamu Aoki wrote:
> Hi,
> 
> On Fri, Feb 19, 2010 at 11:15:24PM -0800, Freeman wrote:
> > On Mon, Feb 15, 2010 at 05:10:26PM -0800, evenso wrote:
> > > On Mon, Feb 15, 2010 at 02:33:05PM -0600, Boyd Stephen Smith Jr. wrote:
> > > > On Monday 15 February 2010 13:30:19 Freeman wrote:
> > > 
> > > > 
> > > > > However, could a rollback represent an incursion on the priority 
> > > > > system?
> ...
> > The above preferences are for testing/unstable/experimental with a
> > contingency for and emergency rollback a package to an obsolete package
> > archived in my apt-cacher files. (My recent experience with the buggy
> > xserver-xorg/mesa upgrade prompted this plan.)
> 
> In short, I do not like people asking this kind of question to casually
> install mixed archive for their sake.  Especially things like experimental.
> 
> > I'd rather find out that the above Preferences are destructive here than
> > during an install!
> 

Thanks everyone, BTW. That thread is in my notes archive.

-- 
Kind Regards,
Freeman


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100222070019.ga7...@europa.office

Re: Anyone Care to Critique my Apt Preferences? (was Re: apt-cacher as package rollback buffer)

[Freeman]

On Sat, Feb 20, 2010 at 06:41:35PM +0900, Osamu Aoki wrote:
> Hi,
> 
> On Fri, Feb 19, 2010 at 11:15:24PM -0800, Freeman wrote:

> > I'd rather find out that the above Preferences are destructive here than
> > during an install!
> 
> Your setting will install latest experimental of a package which you
> insalled from experimental.  I see no reason to have stable or volatile
> when you are basically tracking testing or unstable.

Experimental: I failed to mention that I have the target release set at
testing.  As I read the man, the 500 setting will respect the target
release.

Stable: True, and the setting is redundant. If there is no replacement version,
stable packages will be left alone either way.

Volatile: I was thinking of freshcalm but that setting wouldn't help anyway.

> 
> FYI:
> The upcoming apt_preferences(5) manpage (e.g.: apt_0.7.26~exp2_i386.deb) 
> states:
> 
>Preferences are a strong power in the hands of a system administrator
>but they can become also their biggest nightmare if used without care!
>APT will not questioning the preferences so wrong settings will
>therefore lead to uninstallable packages or wrong decisions while
>upgrading packages. Even more problems will arise if multiply
>distribution releases are mixed without a good understanding of the
>following paragraphs. You have been warned.
> 
> (Hmmm... s/multiply/multiple/ .. time to make another bug report.)
>  

I've read that a few times. 8)


> > My ego may be the more delicately balanced but my system is the more
> > precious. :)
> 
> This squeeze testing cycle has been rough because of major transitions.
> My recent upgrade in one of the multiboot setup from stable to unstable
> caused unbootable system.
> 

Yep. I've never lost a file-system in 7 years of Debian until the
xserver-xorg/mesa upgrade.

> If your ego ticks you, testing only (or with testing security if
> available) is good idea.  If something broke, add unstable while keeping
> testing as default (higher preference) to get fixed packages.  Right
> now, stable and testing have too much gap usually to be useful.  I would
> rather rely on my local package archive under /var/cache/apt/packages/*
> for recent but working packages.  
> 

So really I don't need a preferences file except for my emergency plan to
rollback to a cached version of a package.  (apt-cacher keeps its cache on a
usb drive for my 3 machines.  I am archiving versions by not cleaning it
until the next release.)

In that scenario, I would have gone ahead with an unwise package upgrade and
would be retreating to save my arse, er ("down ego, down boy") the system.

In which case, I pin the rolled back version to 1001. The preferences file
can live on in moderation for the sake of learning.

-- 
Kind Regards,
Freeman


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100220194126.ga7...@europa.office

Re: Anyone Care to Critique my Apt Preferences? (was Re: apt-cacher as package rollback buffer)

[Lisi]

On Saturday 20 February 2010 11:24:01 Andrei Popescu wrote:
> On Sat,20.Feb.10, 18:41:35, Osamu Aoki wrote:
> > FYI:
> > The upcoming apt_preferences(5) manpage (e.g.: apt_0.7.26~exp2_i386.deb)
> > states:
> >
> >Preferences are a strong power in the hands of a system
> > administrator but they can become also their biggest nightmare if used
> > without care! APT will not questioning the preferences so wrong settings
> > will therefore lead to uninstallable packages or wrong decisions while
> > upgrading packages. Even more problems will arise if multiply
> > distribution releases are mixed without a good understanding of the
> > following paragraphs. You have been warned.
> >
> > (Hmmm... s/multiply/multiple/ .. time to make another bug report.)
>
> And either:
>
> s/will not questioning/will not question/ or
> s/will not questioning/will not be questioning/
>
> I hope a native speaker will point to the better one (second?).

The first is not only the better one, but in this context the only correct 
one.  

Lisi


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201002201223.06097.lisi.re...@gmail.com

Re: Anyone Care to Critique my Apt Preferences? (was Re: apt-cacher as package rollback buffer)

[Andrei Popescu]

On Sat,20.Feb.10, 18:41:35, Osamu Aoki wrote:
 
> FYI:
> The upcoming apt_preferences(5) manpage (e.g.: apt_0.7.26~exp2_i386.deb) 
> states:
> 
>Preferences are a strong power in the hands of a system administrator
>but they can become also their biggest nightmare if used without care!
>APT will not questioning the preferences so wrong settings will
>therefore lead to uninstallable packages or wrong decisions while
>upgrading packages. Even more problems will arise if multiply
>distribution releases are mixed without a good understanding of the
>following paragraphs. You have been warned.
> 
> (Hmmm... s/multiply/multiple/ .. time to make another bug report.)

And either:

s/will not questioning/will not question/ or
s/will not questioning/will not be questioning/

I hope a native speaker will point to the better one (second?).

Regards,
Andrei
-- 
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic


signature.asc
Description: Digital signature

Re: Anyone Care to Critique my Apt Preferences? (was Re: apt-cacher as package rollback buffer)

[Boyd Stephen Smith Jr.]

In <20100220094135.gc12...@osamu.debian.net>, Osamu Aoki wrote:
>Right
>now, stable and testing have too much gap usually to be useful.

That's not true.  I mix stable/backports/testing/unstable/experimental.  
Roughly 78% of my systems is packages from stable with the remainder mostly 
from testing.

Packages installed: 1688
Version from stable/security/volatile: 1318
Version from backports: 34
Version from testing/security: 239
Version from unstable: 94
Version from experimental: 0
Local packages: 3
nvidia-kernel-2.6.32-trunk-amd6 - NVIDIA binary kernel module for Linux 
2.6.
pq  - Progress Quest is a "fire and forget" 
comp
w64codecs   - win64 binary codecs

Aptitude requires more use of the interactive resolver than in a pure system, 
but other than that (which I am very comfortable with), I actually am 
encountering fewer bugs than when I used stable+backports.

This is also specific to my package selection.  Users of different bits of 
software may find that much more of testing/unstable needs to be pulled in.  

Osamu is absolutely correct that this is an advanced setup.  It requires an 
attentive and knowledgeable system administrator, and has only minimal support 
form the DDs themselves.  (They provide you plenty of rope with which you can 
hang yourself.)

>(experimental's preference is set to 1 with reason.)

Backports is set to 1 as well. :P
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/\_/


signature.asc
Description: This is a digitally signed message part.