[Aptitude-devel] Bug#575062: aptitude: file descriptor leak of debtags related files

[Manuel A. Fernandez Montecelo]

Control: tags -1 - confirmed + moreinfo unreproducible


Hi all,

(pabs copied because of the duplicate #611235, abe because of BTS
confirming it as late as 2013)


2010-03-23 08:09 Raphaël Hertzog:
>Package: aptitude
>Version: 0.6.1.5-3
>Severity: important
>
>During upgrade today I got this while upgrading the lvm2 package:
>
>Paramétrage de lvm2 (2.02.62-1) ...
>Installation de la nouvelle version du fichier de configuration /etc/lvm/lvm.conf ...
>Setting up LVM Volume GroupsFile descriptor 43 (/var/lib/debtags/vocabulary.idx) leaked on vgscan invocation. Parent PID 17721: /bin/sh
>File descriptor 44 (/var/lib/debtags/vocabulary) leaked on vgscan invocation. Parent PID 17721: /bin/sh
>File descriptor 45 (/var/lib/debtags/package-tags.idx) leaked on vgscan invocation. Parent PID 17721: /bin/sh
>  Reading all physical volumes.  This may take a while...
>  Found volume group "VG-CRYPT" using metadata type lvm2
>File descriptor 43 (/var/lib/debtags/vocabulary.idx) leaked on vgchange invocation. Parent PID 17721: /bin/sh
>File descriptor 44 (/var/lib/debtags/vocabulary) leaked on vgchange invocation. Parent PID 17721: /bin/sh
>File descriptor 45 (/var/lib/debtags/package-tags.idx) leaked on vgchange invocation. Parent PID 17721: /bin/sh
>  2 logical volume(s) in volume group "VG-CRYPT" now active
>.
>
>I think that aptitude was the process who opened those files. If it's not feel
>free to reassign where appropriate. You should ensure those files are
>closed when you fork to run dpkg.


2013-01-08 20:34 Axel Beckert:
>tags 497129 + confirmed
>tags 623609 + moreinfo
>found 373846 0.6.4-1
>found 373846 0.6.4-1.2
>tags 555399 + unreproducible
>tags 665794 + moreinfo
># Daniel H. marked it as found
>tags 575062 + confirmed
># Daniel H. marked it as found
>tags 575062 + confirmed
>tags 665794 + moreinfo
># based on report date and aptitude version in Squeeze at that time (i.e. didn't try to reproduce it)
>found 676365 0.6.3-3.2+squeeze1
>thanks


I am quite sure (but not 100%) that I tried to reproduce this a few
weeks ago and that I couldn't.  I also remember seeing these error
messages in the distant past when upgrading myself, but not lately, and
cannot recall if they were related to aptitude/debtags anyway.

The original reports now merged happened in 2010-2011, but no new
reports / seconds since then (except Axel's confirmation in 2013, that
looks more like a BTS bookkeping than a real confirmation).  One of the
messages in the bug reports points to Ubuntu bugs, but it's not related
to debtags or aptitude.

Opening the tags was changed in the last intervening years, from using
libept as intermediary to using xapian directly, so I am wondering if it
was fixed by then.


I already upgraded lvm2 in unstable a couple of days ago, and playing
with this in my main / only machine at the time is quite risky
(esp. because of downgrading)...  but this package was updated on the
last few days in November, and still not in testing ("4 of 5 days old").

If you have systems with testing (or unstable, but still didn't upgrade
the package), could you perhaps try to see if this is still happening
when you upgrade in the next few days, and report back the results in
this bug report?


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>