On Sat, Oct 08, 2005 at 01:12:08PM +0200, Marc Haber wrote:
See attached log of a failed aptitude update run, and the working one
after restarting apt-cacher (2400 lines).
This is not related to: data expiring (EXPIRED) - apt-cacher has
successfully handled that case this morning, and it is
Moin Marc!
Marc Haber schrieb am Samstag, den 08. Oktober 2005:
Package: apt-cacher
Severity: normal
Hi,
after being in use for some time (like on a computer idling over
night, which uses hourly cron-apt to check for new updates),
apt-cacher gets confused and starts returning error 500.
On Sun, Oct 09, 2005 at 05:33:47PM +0200, Eduard Bloch wrote:
See attached log of a failed aptitude update run, and the working one
after restarting apt-cacher (2400 lines).
I do not understand where it comes from. Following this report, the
errors are reported by the http client module,
retitle 332748 User::Agent throwing bogus Bad hostname errors after a while
reassign 332748 libwww-perl
thanks
Marc Haber schrieb am Sonntag, den 09. Oktober 2005:
On Sun, Oct 09, 2005 at 05:33:47PM +0200, Eduard Bloch wrote:
See attached log of a failed aptitude update run, and the working
Package: apt-cacher
Severity: normal
Hi,
after being in use for some time (like on a computer idling over
night, which uses hourly cron-apt to check for new updates),
apt-cacher gets confused and starts returning error 500. After
terminating and restarting apt-cacher, everything is fine.
See
5 matches
Mail list logo
