Bug#365819: apt-get update chokes on Bad header line

2006-05-09 Thread Ralf Schlatterbeck
On Thu, May 04, 2006 at 01:46:10PM +0200, Goswin von Brederlow wrote:
 Could you use tcpdump or ethereal or similar to log the actual network
 traffic of apt-get? But please, only that of apt-get.

On Mon, May 08, 2006 at 11:13:30AM +0200, Michael Vogt wrote:
 The output of:
 # apt-get  -o Debug::Acquire::http=true update 2 apt_http.log
 
 would be usefull here (please attach it to this bugreport).

I've attached a tcpdump log, 10.0.0.5 is the server 10.0.0.17 the debian
etch client. The first answer from the server (200 OK to Release.gpg)
looks garbled (my ethereal's dissector could not parse it).  This lead
me to restart apache on the server and I haven't seen the problem since.
If it occurs again I'll try with the Debug options to apt-get. For now I
think you can close this report, doesn't seem to be a problem in apt-get
afaict.

Sorry for the report, looks like wget could parse the broken header-line
ok and I hadn't seen that behaviour of apache ever before.

Ralf
-- 
Ralf Schlatterbeck
email: [EMAIL PROTECTED] FAX: +43/2243/26465/23



dump.try1
Description: Binary data


Bug#365819: apt-get update chokes on Bad header line

2006-05-08 Thread Michael Vogt
On Thu, May 04, 2006 at 08:48:29AM +0200, Ralf Schlatterbeck wrote:
 On Wed, May 03, 2006 at 12:52:37AM -0700, Steve Langasek wrote:
  On Wed, May 03, 2006 at 09:20:39AM +0200, Ralf Schlatterbeck wrote:
  
   apt-get update produces Bad header line messages on some files. Note 
   that
   this error is not reproduceable always (and happens for different files
   although Release.gpg is often among them), sometimes the update runs
   successfully,
  
  This error certainly isn't reproducible in the general case.
 
 I can now confirm that only apt-get in etch is affected. My apt-get in
 sarge works perfectly. Anything I can do (e.g. build the apt package
 with debugging turned on) to help you diagnose this problem?

The output of:
# apt-get  -o Debug::Acquire::http=true update 2 apt_http.log

would be usefull here (please attach it to this bugreport).

Thanks,
 Michael

-- 
Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#365819: apt-get update chokes on Bad header line

2006-05-04 Thread Ralf Schlatterbeck
On Wed, May 03, 2006 at 12:52:37AM -0700, Steve Langasek wrote:
 On Wed, May 03, 2006 at 09:20:39AM +0200, Ralf Schlatterbeck wrote:
 
  apt-get update produces Bad header line messages on some files. Note that
  this error is not reproduceable always (and happens for different files
  although Release.gpg is often among them), sometimes the update runs
  successfully,
 
 This error certainly isn't reproducible in the general case.

I can now confirm that only apt-get in etch is affected. My apt-get in
sarge works perfectly. Anything I can do (e.g. build the apt package
with debugging turned on) to help you diagnose this problem?

Ralf
-- 
Ralf Schlatterbeck
email: [EMAIL PROTECTED] FAX: +43/2243/26465/23



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#365819: apt-get update chokes on Bad header line

2006-05-04 Thread Steve Langasek
On Thu, May 04, 2006 at 08:48:29AM +0200, Ralf Schlatterbeck wrote:
 On Wed, May 03, 2006 at 12:52:37AM -0700, Steve Langasek wrote:
  On Wed, May 03, 2006 at 09:20:39AM +0200, Ralf Schlatterbeck wrote:

   apt-get update produces Bad header line messages on some files. Note 
   that
   this error is not reproduceable always (and happens for different files
   although Release.gpg is often among them), sometimes the update runs
   successfully,

  This error certainly isn't reproducible in the general case.

 I can now confirm that only apt-get in etch is affected. My apt-get in
 sarge works perfectly. Anything I can do (e.g. build the apt package
 with debugging turned on) to help you diagnose this problem?

Sorry, I'm afraid not; I was only triaging the bug severity so that it
wasn't marked as a release-critical bug when the vast majority of users are
using apt-get ok, I'm not actually an apt maintainer and don't know the
internals enough to suggest how to debug this.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


signature.asc
Description: Digital signature


Bug#365819: apt-get update chokes on Bad header line

2006-05-04 Thread Goswin von Brederlow
Ralf Schlatterbeck [EMAIL PROTECTED] writes:

 On Wed, May 03, 2006 at 12:52:37AM -0700, Steve Langasek wrote:
 On Wed, May 03, 2006 at 09:20:39AM +0200, Ralf Schlatterbeck wrote:
 
  apt-get update produces Bad header line messages on some files. Note that
  this error is not reproduceable always (and happens for different files
  although Release.gpg is often among them), sometimes the update runs
  successfully,
 
 This error certainly isn't reproducible in the general case.

 I can now confirm that only apt-get in etch is affected. My apt-get in
 sarge works perfectly. Anything I can do (e.g. build the apt package
 with debugging turned on) to help you diagnose this problem?

 Ralf

Could you use tcpdump or ethereal or similar to log the actual network
traffic of apt-get? But please, only that of apt-get.

MfG
Goswin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#365819: apt-get update chokes on Bad header line

2006-05-03 Thread Ralf Schlatterbeck
Package: apt
Version: 0.6.43.3
Severity: critical

apt-get update produces Bad header line messages on some files. Note that
this error is not reproduceable always (and happens for different files
although Release.gpg is often among them), sometimes the update runs
successfully, I've also tried 
apt-get -o Acquire::http::Pipeline-Depth=0 update
suggested in an earlier bug-report for apt but this did not work.
I'm running apache 1.3.33-6sarge1 on a debian server for my local debian
mirror.

Output of apt-get:
gnu:~# apt-get -o Acquire::http::Pipeline-Depth=0 update
Errhttp://bee etch Release.gpg
  Bad header line [IP: 10.0.0.5 80]
Ign http://bee etch Release
Errhttp://bee etch/main Packages
  Bad header line [IP: 10.0.0.5 80]
Hit http://bee etch/non-free Packages
Hit http://bee etch/contrib Packages
Hit http://bee etch/main Sources
Hit http://bee etch/non-free Sources
Hit http://bee etch/contrib Sources
Get: 1 http://security.debian.org etch/updates Release.gpg [189B]
Get: 2 http://debian.inode.at etch Release.gpg [189B]
Hit http://debian.inode.at etch Release
Hit http://security.debian.org etch/updates Release
Hit http://security.debian.org etch/updates/main Packages
Hit http://debian.inode.at etch/main Packages
Hit http://security.debian.org etch/updates/contrib Packages
Hit http://debian.inode.at etch/non-free Packages
Hit http://security.debian.org etch/updates/non-free Packages
Hit http://debian.inode.at etch/contrib Packages
Hit http://security.debian.org etch/updates/main Sources
Hit http://security.debian.org etch/updates/contrib Sources
Hit http://security.debian.org etch/updates/non-free Sources
Fetched 190B in 0s (394B/s)
Failed to fetch http://bee/debian/dists/etch/Release.gpg  Bad header line [IP: 
10.0.0.5 80]
Failed to fetch http://bee/debian/dists/etch/main/binary-i386/Packages.gz  Bad 
header line [IP: 10.0.0.5 80]
Reading package lists... Done
E: Some index files failed to download, they have been ignored, or old ones 
used instead.

Corresponding Apache access.log on the server:
10.0.0.12 - - [03/May/2006:09:07:09 +0200] GET /debian/dists/etch/Release.gpg 
HTTP/1.1 200 189 - Debian APT-HTTP/1.3 -
10.0.0.12 - - [03/May/2006:09:07:09 +0200] GET /debian/dists/etch/Release 
HTTP/1.1 304 - - Debian APT-HTTP/1.3 -
10.0.0.12 - - [03/May/2006:09:07:09 +0200] GET 
/debian/dists/etch/main/binary-i386/Packages.gz HTTP/1.1 304 - - Debian 
APT-HTTP/1.3 -
10.0.0.12 - - [03/May/2006:09:07:09 +0200] GET 
/debian/dists/etch/non-free/binary-i386/Packages.gz HTTP/1.1 304 - - Debian 
APT-HTTP/1.3 -
10.0.0.12 - - [03/May/2006:09:07:09 +0200] GET 
/debian/dists/etch/contrib/binary-i386/Packages.gz HTTP/1.1 304 - - Debian 
APT-HTTP/1.3 -
10.0.0.12 - - [03/May/2006:09:07:09 +0200] GET 
/debian/dists/etch/main/source/Sources.gz HTTP/1.1 304 - - Debian 
APT-HTTP/1.3 -
10.0.0.12 - - [03/May/2006:09:07:09 +0200] GET 
/debian/dists/etch/non-free/source/Sources.gz HTTP/1.1 304 - - Debian 
APT-HTTP/1.3 -


-- Package-specific info:

-- apt-config dump --

APT ;
APT::Architecture i386;
APT::Build-Essential ;
APT::Build-Essential:: build-essential;
APT::Authentication ;
APT::Authentication::TrustCDROM true;
Dir /;
Dir::State var/lib/apt/;
Dir::State::lists lists/;
Dir::State::cdroms cdroms.list;
Dir::State::userstatus status.user;
Dir::State::status /var/lib/dpkg/status;
Dir::Cache var/cache/apt/;
Dir::Cache::archives archives/;
Dir::Cache::srcpkgcache srcpkgcache.bin;
Dir::Cache::pkgcache pkgcache.bin;
Dir::Etc etc/apt/;
Dir::Etc::sourcelist sources.list;
Dir::Etc::sourceparts sources.list.d;
Dir::Etc::vendorlist vendors.list;
Dir::Etc::vendorparts vendors.list.d;
Dir::Etc::main apt.conf;
Dir::Etc::parts apt.conf.d;
Dir::Etc::preferences preferences;
Dir::Bin ;
Dir::Bin::methods /usr/lib/apt/methods;
Dir::Bin::dpkg /usr/bin/dpkg;
DPkg ;
DPkg::Pre-Install-Pkgs ;
DPkg::Pre-Install-Pkgs:: /usr/sbin/dpkg-preconfigure --apt || true;
Acquire ;
AcquireProxy false;

-- (no /etc/apt/preferences present) --


-- /etc/apt/sources.list --

# deb http://bee/debian/ etch main
deb http://bee/debian/ etch main non-free contrib
deb-src http://bee/debian/ etch main non-free contrib
#deb http://bee/debian-dist/security/ etch/updates main non-free contrib
deb http://debian.inode.at/debian/ etch main non-free contrib

deb http://security.debian.org/ etch/updates main contrib non-free
deb-src http://security.debian.org/ etch/updates main contrib non-free

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)

Versions of packages apt depends on:
ii  libc6   2.3.6-7  GNU C Library: Shared libraries
ii  libgcc1 1:4.1.0-1+b1 GCC support library
ii  libstdc++6  4.1.0-1+b1   The GNU Standard C++ Library v3

Versions of packages apt recommends:
pn  

Bug#365819: apt-get update chokes on Bad header line

2006-05-03 Thread Steve Langasek
severity 365819 normal
tags 365819 moreinfo unreproducible
thanks

On Wed, May 03, 2006 at 09:20:39AM +0200, Ralf Schlatterbeck wrote:

 apt-get update produces Bad header line messages on some files. Note that
 this error is not reproduceable always (and happens for different files
 although Release.gpg is often among them), sometimes the update runs
 successfully,

This error certainly isn't reproducible in the general case.  How much free
space do you have on /var?  That's the only time I've ever seen this
particular error.

Downgrading this report, since it's certainly not true that apt is generally
unusable...

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#365819: apt-get update chokes on Bad header line

2006-05-03 Thread Ralf Schlatterbeck
On Wed, May 03, 2006 at 12:52:37AM -0700, Steve Langasek wrote:
 tags 365819 moreinfo unreproducible
 
 This error certainly isn't reproducible in the general case.  How much free
 space do you have on /var?  That's the only time I've ever seen this
 particular error.
On the server:
[EMAIL PROTECTED]:(260)% df /var
Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/sda1151225248 139694388   3848984  98% /

On the to-be-installed etch system:
gnu:~# df
Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/sda1189682520516288 179530852   1% /
tmpfs   513976 0513976   0% /dev/shm
tmpfs   51397672513904   1% /dev

So I guess space is not the problem.

 Downgrading this report, since it's certainly not true that apt is generally
 unusable...
OK.
For me it's a showstopper -- although I maybe should try with ftp on the
server. Note that this hit me also during install of another box
(soekris embedded hardware with serial console), after apt configuration
the magic in the installer marked all apt sources as unavailable, so I
was unable to complete the installation normally because neither lilo
nor grub would be installed...

-- 
Ralf Schlatterbeck
email: [EMAIL PROTECTED] FAX: +43/2243/26465/23



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]