On Fri, Oct 21, 2016 at 08:35:55PM +0200, Eduard Bloch wrote: > Hallo, > * Peter Colberg [Fri, Oct 21 2016, 11:01:44AM]: > > Package: apt-cacher-ng > > Version: 1-1 > > Severity: normal > > > > Dear Maintainer, > > > > After updating to the above version, the cron job fails with > > From which version? That's the real question.
The regression was introduced upgrading from 0.9.3.2-1 to 1-1. > > /etc/cron.daily/apt-cacher-ng: > > Error: cannot fetch > > http://foo.example.org:3142/acng-report.html?doExpire=Start+Expiration&abortOnErrors=aOe, > > There is no such hostname anywhere in the source. If you redacted the > output then you should mention this (and describe the real output), > otherwise we are hunting ghosts. Sorry for not being clear; yes, the hostname has been redacted and belongs to the machine which runs apt-cacher-ng and the cron job. > As stop-gap solution, you could set HOSTNAME variable as needed in the > mentioned cron script. Thanks, I will try that for the next run. > > My acng.conf differs from the default by one line, > > > > BindAddress: localhost > > In the previous times there was a creepy workaround that fished the > hostname from BindAddress strings as a last ressort. Maybe I should > recteate this method in acngtool. What would speak against querying http://localhost:3142/ by default? Regards, Peter
