Your message dated Sat, 22 Oct 2016 11:39:01 -0400
with message-id <20161022153901.hdgrtqv7opu55hfc@alcyone>
and subject line Re: Bug#841633: apt-cacher-ng: cron job fails when BindAddress
is localhost
has caused the Debian Bug report #841633,
regarding apt-cacher-ng: cron job fails when BindAddress is localhost
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
841633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841633
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apt-cacher-ng
Version: 1-1
Severity: normal
Dear Maintainer,
After updating to the above version, the cron job fails with
/etc/cron.daily/apt-cacher-ng:
Error: cannot fetch
http://foo.example.org:3142/acng-report.html?doExpire=Start+Expiration&abortOnErrors=aOe,
My acng.conf differs from the default by one line,
BindAddress: localhost
which ensures that apt-cacher-ng is accessible only from the local machine.
Regards,
Peter
--- End Message ---
--- Begin Message ---
On Fri, Oct 21, 2016 at 08:35:55PM +0200, Eduard Bloch wrote:
> As stop-gap solution, you could set HOSTNAME variable as needed in the
> mentioned cron script.
With HOSTNAME=localhost the cron job ran fine today. It is only fair
that one has to adapt the cron script when configuring a non-default
BindAddress. Sorry for the noise and many thanks for having written
this very useful software.
Regards,
Peter
--- End Message ---
