[Bug debuginfod/27399] New: dpkg-deb/lzma error when indexing .debs

[sergiodj at sergiodj dot net]

https://sourceware.org/bugzilla/show_bug.cgi?id=27399

            Bug ID: 27399
           Summary: dpkg-deb/lzma error when indexing .debs
           Product: elfutils
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: debuginfod
          Assignee: unassigned at sourceware dot org
          Reporter: sergiodj at sergiodj dot net
                CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

I'm running debuginfod in a test VM with a bunch of .deb dbgsym files and I
noticed some errors like the one below when indexing the packages:

...
Feb 12 00:33:04 debian-unstable debuginfod[92513]: dpkg-deb (subprocess):
decompressing archive
'/srv/mirrors/debian/debug.mirrors.debian.org/debian-debug/pool/main/a/anope/anope-dbgsym_2.0.6-1+b1_amd64.deb'
(size=64353340) member 'data.tar': lzma write error: Broken pipe
Feb 12 00:33:04 debian-unstable debuginfod[92511]: dpkg-deb: error:
<decompress> subprocess returned error exit status 2
...

This happens sporadically, when I start/restart the service, and with different
files every time.  Also, the number of errors varies: sometimes it's just one
error, sometimes it's as many as 4 or 5.  I have around 1841 .deb files here
(this is just a very small subset of the whole Debian mirror), so I assume that
if I try to index several thousand files I will see a bunch more of these
errors popping up.

The debuginfod.service I'm using is pretty much the same as the one shipped by
upstream.  I've done a minor modification to the /etc/default/debuginfod file
in order to make it index Debian files:

...
DEBUGINFOD_PATHS="-t43200 -U
/srv/mirrors/debian/debug.mirrors.debian.org/debian-debug/pool/main/a/"
...

Otherwise, it's also the same as the one shipped in the tarball.  I've tested
this with Debian's latest elfutils from unstable (0.183-1), and also built
debuginfod from git HEAD (d358f6329945c96b25f777377055ee44133810fa, at the time
of this writing).

I haven't gotten the chance to do proper debugging yet, but I'm happy to
provide more info meanwhile.  TIA.

-- 
You are receiving this mail because:
You are on the CC list for the bug.