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
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
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
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
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
o 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
operat
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
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 pa
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.
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
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
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
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 (19
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
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
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
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
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:
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 s
/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
ep_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
:MUNGED:8 - - [07/Aug/2022:05:01:17 +0000]
> "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
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
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
- "
ut 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 current
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 tho
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
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
t;>>>> 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:
>>>>>
ohn 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:
> >>>>>&
:
>>>>> 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
>
&
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
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.lis
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-AP
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 g
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 fi
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
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 be
; > 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.
>
> Tha
t; 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/
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 expir
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
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*".
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
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
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
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
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
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.
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 d
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?
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
ht
ularly 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"
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
; > 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/000
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
> 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
rating 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 runni
ong 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.
> An
s 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
e-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 lin
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
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
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 enabl
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 environme
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
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 i
Boa tarde caros amigos;
Montei em minha rede um servidor apt-cacher, quando faço algum apt-get
update ou instalo algum programa ele começa a baixar os pacotes
normalmente, porem se ocorrer algum erro em um dos pacotes o aptcacher para
de funcionar, porem se eu apago o pacote que deu erro ele
Mas qual a mensagem de erro ?
Em 3 de novembro de 2015 13:38, thyago Assis <thyago...@gmail.com> escreveu:
> Boa tarde caros amigos;
>
> Montei em minha rede um servidor apt-cacher, quando faço algum apt-get
> update ou instalo algum programa ele começa a baixar os pacotes
&g
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:
>
om 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) o
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
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
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
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
-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
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
Bonjour,
Savez-vous si on peut utiliser les dépots wheezy-backports avec
apt-cacher-ng. si oui, comment fait-on ? J'ai beau chercher sur le net,
je ne trouve rien de probant.
J'ai des machines en réseau sous wheezy qui utilisent un serveur muni
d'apt-cacher. J'aimerai pouvoir installer
Bonsoir,
Le 02/10/2014 19:38, Nicolas a écrit :
Bonjour,
Savez-vous si on peut utiliser les dépots wheezy-backports avec
apt-cacher-ng. si oui, comment fait-on ? J'ai beau chercher sur le net,
je ne trouve rien de probant.
J'ai des machines en réseau sous wheezy qui utilisent un serveur muni
, 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.
snipped
It is commented out but that is supposed to be the default.
The default is *not* to allow access from all hosts
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
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
On 20/03/14 06:41, Rick McCombs AD5DU wrote:
On Wed, Mar 19, 2014 at 2:36 AM, Scott Ferguson
scott.ferguson.debian.u...@gmail.com 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
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
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
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
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
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
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
Hola gente:
Por ahí es una tontería lo que pregunto, pero ahí va...
Por qué cuando ejecuto nmap localhost no me aparece el puerto 3142 que
utiliza apt-cacher ?
Aclaro que apt-cacher se está ejecutando y lo utilizo desde otros
equipos para hacer las actualizaciones.
Tampoco aparece este
On 09/05/13 21:07, Walter O. Dari wrote:
Hola gente:
Por ahí es una tontería lo que pregunto, pero ahí va...
Por qué cuando ejecuto nmap localhost no me aparece el puerto 3142 que
utiliza apt-cacher ?
Aclaro que apt-cacher se está ejecutando y lo utilizo desde otros
equipos para hacer las
El día 9 de mayo de 2013 21:07, Walter O. Dari
wod...@swcomputacion.com escribió:
Hola gente:
Por ahí es una tontería lo que pregunto, pero ahí va...
Por qué cuando ejecuto nmap localhost no me aparece el puerto 3142 que
utiliza apt-cacher ?
Hablo de memoria, pero creo que nmap solo
apt-cacher ?
Hablo de memoria, pero creo que nmap solo chequea los puertos
estándar, si quieres que chequee otros puertos debes indicarlo con el
-p
Eso no lo sabía, pensé que escaneaba todos los puertos posibles por defecto.
Bueno, ahora sí, con tu sugerencia apareció...
root@debi5:~# nmap
Hola...
El 09/05/13 16:46, jors escribió:
On 09/05/13 21:07, Walter O. Dari wrote:
Hola gente:
Por ahí es una tontería lo que pregunto, pero ahí va...
Por qué cuando ejecuto nmap localhost no me aparece el puerto 3142 que
utiliza apt-cacher ?
Aclaro que apt-cacher se está ejecutando y lo
servidor
sin problemas.
Hum... me refiero a si en el resto de equipos, al poner esta lÃÂnea en
el sources.list funciona o te salta apt-cacher con el mismo error:
deb http://192.168.0.4:3142/mariadb52 squeeze main
En el único equipo que me da error especificando la IP es en el corre el
apt-cacher
El Mon, 08 Apr 2013 13:59:30 -0300, Walter O. Dari escribió:
El 05/04/13 11:06, Camaleón escribió:
(...)
En el único equipo que me da error especificando la IP es en el corre
el apt-cacher.
Hum... entonces no tenemos un patrón de fallo.
Pues se me ocurre que revises los registros de
Hola...
El 08/04/13 14:13, Camaleón escribió:
El Mon, 08 Apr 2013 13:59:30 -0300, Walter O. Dari escribió:
El 05/04/13 11:06, Camaleón escribió:
(...)
En el único equipo que me da error especificando la IP es en el corre
el apt-cacher.
Hum... entonces no tenemos un patrón de
El Mon, 08 Apr 2013 15:01:34 -0300, Walter O. Dari escribió:
El 08/04/13 14:13, Camaleón escribió:
(...)
¿Y el registro de apt-cacher te da alguna pista más?
Apareció el problema !
Como en el registro de apt-cacher no me aparecía la palabra error,
salvo un paquete que la contenía, me
resto de equipos, al poner esta lÃnea en
el sources.list funciona o te salta apt-cacher con el mismo error:
deb http://192.168.0.4:3142/mariadb52 squeeze main
En el único equipo que me da error especificando la IP es en el corre el
apt-cacher.
Hum... entonces no tenemos un patrón de fallo
el apt-cacher.
Bueno, lo extraño es cuando hago un aptitude update:
- en la PC con wheezy no hay problemas
- en el servidor con squeeze i386, tampoco
Ahora solamente en el servidor con squeeze amd64 me da el siguiente error:
Ign http://192.168.0.4 squeezy/main amd64 Packages
Err http
1 - 100 of 237 matches
Mail list logo
