[Piuparts-devel] timeout testing debian-design

Jonas Smedegaard dr at jones.dk
Wed Jan 11 12:45:05 UTC 2017


Quoting Andreas Beckmann (2017-01-11 13:04:58)
> I'm just rerunning the command from the logfile manually and these should be the relevant "hanging" processes:
> 
> root     30773  0.0  0.0  79924  4436 pts/39   S+   12:42   0:00 sudo nice env PYTHONPATH=/srv/piuparts/lib/python2.7/dist-packages timeout -s INT -k 5m 110m /srv/piuparts/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --no-eatmydata --scriptsdir /etc/piuparts/scripts --allow-database --warn-on-leftovers-after-purge --proxy http://localhost:3128 --mirror http://ftp.de.debian.org/debian main --tmpdir /tmp/piupartss --arch amd64 -b /srv/piuparts/slave/basetgz/sid_amd64.tar.gz -d sid --no-upgrade-test --apt design-desktop=3.0.4
> root     30783  0.0  0.0  11944   856 pts/39   SN   12:42   0:00 timeout -s INT -k 5m 110m /srv/piuparts/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --no-eatmydata --scriptsdir /etc/piuparts/scripts --allow-database --warn-on-leftovers-after-purge --proxy http://localhost:3128 --mirror http://ftp.de.debian.org/debian main --tmpdir /tmp/piupartss --arch amd64 -b /srv/piuparts/slave/basetgz/sid_amd64.tar.gz -d sid --no-upgrade-test --apt design-desktop=3.0.4
> root     30803  1.1  0.1 120264 63824 pts/39   TN   12:42   0:11 /usr/bin/python /srv/piuparts/sbin/piuparts --skip-logrotatefiles-test --warn-on-others --no-eatmydata --scriptsdir /etc/piuparts/scripts --allow-database --warn-on-leftovers-after-purge --proxy http://localhost:3128 --mirror http://ftp.de.debian.org/debian main --tmpdir /tmp/piupartss --arch amd64 -b /srv/piuparts/slave/basetgz/sid_amd64.tar.gz -d sid --no-upgrade-test --apt design-desktop=3.0.4
> root     29515  0.0  0.1  84340 46992 pts/39   TN   12:45   0:00 apt-get -y install design-desktop=3.0.4
> root     30238  0.0  0.0  84340 14128 pts/39   TN   12:45   0:00 apt-get -y install design-desktop=3.0.4
> root     30240  0.0  0.0   4288   752 pts/39   TN   12:45   0:00 sh -c test -x /usr/lib/needrestart/apt-pinvoke && /usr/lib/needrestart/apt-pinvoke || true
> root     30241  0.0  0.0  55276 14444 pts/39   TN   12:45   0:00 /usr/bin/perl -w /usr/share/debconf/frontend /usr/sbin/needrestart
> root     30331  0.0  0.0  50124 17516 pts/39   TN   12:45   0:00 /usr/bin/perl /usr/sbin/needrestart
> root      2838  0.0  0.0      0     0 pts/39   ZN   12:45   0:00 [90-none] <defunct>
> root      2846  0.0  0.0   4288   740 pts/39   TN   12:45   0:00 sh -c resize 2>/dev/null
> root      2847  0.0  0.0   4188   704 pts/39   TN   12:45   0:00 resize
> piupart+  3759  0.0  0.0  14636   928 pts/7    S+   13:00   0:00 grep pts/39

Thanks.

But if that info was meant for me, then could you please help make sense 
of it?

On a live system I would hit "t" in htop for a tree view - hoping that 
way to identify the parent of the mysterious "[90-none] <defunct>".

Could it perhaps be needrestart hanging?  Apparently it is very rare to 
depend on that package...


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20170111/a8f577c0/attachment.sig>


More information about the Piuparts-devel mailing list