Hi Andreas! On Thu, 2014-01-09 at 20:14:02 +0100, Andreas Beckmann wrote: > Package: dpkg > Version: 1.17.5 > Severity: serious
> during a piuparts test of education-thin-client-server with installation > of recommends enabled, I ran into these dpkg errors: > > [...] > Setting up python-lxml (3.2.0-1+b1) ... > dpkg: error processing package python-lxml (--configure): > unable to open triggers ci file `/var/lib/dpkg/info/python-lxml.triggers': > Too many open files > Setting up python-pylibacl (0.5.1-1.1+b3) ... > dpkg: error processing package python-pylibacl (--configure): > unable to open triggers ci file > `/var/lib/dpkg/info/python-pylibacl.triggers': Too many open files > Setting up python-pyxattr (0.5.1-1.1+b3) ... > dpkg: error processing package python-pyxattr (--configure): > unable to open triggers ci file > `/var/lib/dpkg/info/python-pyxattr.triggers': Too many open files > Setting up python-tdb (1.2.12-1) ... > dpkg: error processing package python-tdb (--configure): > unable to open triggers ci file `/var/lib/dpkg/info/python-tdb.triggers': > Too many open files > dpkg: dependency problems prevent configuration of python-samba: > python-samba depends on python-tdb; however: > Package python-tdb is not configured yet. > [...] So it would seem there's a file descriptor leak somewhere, I guess this started happening only with dpkg >> 1.17.1? I'm reviewing the commits since then, but it might be easier if you had access to the system running those commands and could do a «ls -l /proc/<main-dpkg-pid>/fd/». So that we could quickly see what's the file whose descriptor is being leaked. Otherwise I'll try to come up with a test case. Thanks, Guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
