On Tue, Mar 03, 2009 at 07:34:00AM -0500, Omari Norman wrote: > Greetings! > > On Tue, Mar 03, 2009 at 09:10:29AM +0000, Mark Hindley wrote: > > Is it always the same files, or always the same server? > > It seems to always be these four files. > > > Could you run apt-get update with -o Debug::Acquire::http=True > > Sure, I will attach that if the BTS allows it as I have lots of sources. > > > and also enable debugging in the config file and send the contents of > > /var/log/apt-cacher/error.log. > > I will attach what I have from an older rotated log that did not have > debugging enabled. I enabled debugging and restarted apt-cacher, but now > it will not start at all. All I get on my console when running > /etc/init.d/apt-cacher start is > > Starting Apt-Cacher: apt-cacherdebug [17224]: Using IPv6 > debug [17224]: Listening on :::3142 > debug [17224]: fork listener > debug [17224]: Clean up before exiting. > .
That is normal. It is just the parent process exiting after it has forked the daemon. > ps doesn't show any running apt-cacher instances and netstat doesn't > show anything listening on port 3142, and the error.log is empty. > apt-get update spews out a bunch of "Connection refused" messages. > aptitude reinstall apt-cacher doesn't help. (This is the first time I > tried to restart apt-cacher after noticing the problem that caused me to > report this bug.) netstat -l|grep 3142 or top -u www-data ought to show you the apt-cacher process. Mark -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
