It seems that error was related to apt-cacher-ng, we are in the middle of rolling out ipv6 and the machine apt-cacher-ng is running is was trying to use ipv6 when contacting security.debian.org. Disabling ipv6 on that machine fixed this issue.
On Tue, Apr 12, 2011 at 12:52 PM, Kash <melbo...@gmail.com> wrote: > I see bunch of "500 Peer communication, code 101", here's a screenshot > > http://imgpaste.com/i/ufjna.jpg > > > On Tue, Apr 12, 2011 at 9:45 AM, Christian PERRIER <bubu...@debian.org> wrote: >> Quoting Kash (melbo...@gmail.com): >> >>> What could be the problem and how can I fix this error? >> >> As is, nobody can tell. >> >> The logs in terminal 4, or the /var/log/syslog file (or files in >> /var/log/installer on the instaleld system) will give you more >> information. >> >> >> > -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktimb76-p5+tlbxmxkdfv1cvo7xc...@mail.gmail.com
