On 17/06/20 at 12:09 +0200, Julien Cristau wrote: > On Wed, Jun 17, 2020 at 07:00:43 +0100, Adam D. Barratt wrote: > > > On Wed, 2020-06-17 at 00:14 +0200, Lucas Nussbaum wrote: > > > Apparently the condition where this happens is quite rare > > > occurences on 08/2019, 12/2019, 06/2020), so notifying me after the > > > files were cleaned up from /tmp makes it hard to identify which > > > packages cause this issue. If I could get notified when a warning > > > limit is reached, it would be much easier to debug. > > > > I'm not sure what the usual policy on that is, but I didn't clean up > > /tmp after disabling the importer last night:
I could not reproduce this exact issue, but ran into something similar. It boils down to: To get the watch file, UDD extracts the source package (once per source package per version; then the watch file is stored in DB). /tmp on ullmann only has 5.3GB available, which is too small to extract some source packages in Debian (such as nvidia-cuda-toolkit). I've just added a more generic exception handling, so now UDD should clean up /tmp from those extracted packages in all cases (which wasn't the case before, even if I don't understand exactly why it wasn't). However, until the disk space available for /tmp is increased, this importer would continue to fill up / on a regular basis, which will likely break other stuff. So, please increase the disk space available in /tmp (or provide a dedicated temporary space, for example under /srv/udd.debian.org/). In the meantime, I've disabled the importer in rudd.conf. Thanks Lucas