Your message dated Tue, 12 Jan 2016 17:08:20 +0100
with message-id <569524f4.3090...@debian.org>
and subject line RE: virtualbox-ext-pack: doesn't use invoke-rc.d - leaves
processes running after purge
has caused the Debian Bug report #802143,
regarding virtualbox-ext-pack: doesn't use invoke-rc.d - leaves processes
running after purge
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
802143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox-ext-pack
Version: 5.0.6-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package starts processes
where it shouldn't. This is very probably due to not using invoke-rc.d
as mandated by policy 9.3.3.2. This is seriously disturbing! ;-)
See https://www.debian.org/doc/debian-policy/ch-opersys.html#s9.3.3
and /usr/share/doc/sysv-rc/README.invoke-rc.d.gz as well
as /usr/share/doc/sysv-rc/README.policy-rc.d.gz
>From the attached log (scroll to the bottom...):
1m28.5s ERROR: FAIL: Processes are running inside chroot:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
VBoxXPCOM 29925 root cwd DIR 0,20 460 347411940
/tmp/piupartss/tmp9o7H4F
VBoxXPCOM 29925 root rtd DIR 0,20 460 347411940
/tmp/piupartss/tmp9o7H4F
VBoxXPCOM 29925 root mem REG 0,20 47712 347443186
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libnss_files-2.19.so
VBoxXPCOM 29925 root mem REG 0,20 43592 347443192
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libnss_nis-2.19.so
VBoxXPCOM 29925 root mem REG 0,20 89104 347443181
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libnsl-2.19.so
VBoxXPCOM 29925 root mem REG 0,20 31632 347443179
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libnss_compat-2.19.so
VBoxXPCOM 29925 root mem REG 0,20 76232 347443148
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libgpg-error.so.0.16.0
VBoxXPCOM 29925 root mem REG 0,20 84856 347443185
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libresolv-2.19.so
VBoxXPCOM 29925 root mem REG 0,20 924096 347443150
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libgcrypt.so.20.0.3
VBoxXPCOM 29925 root mem REG 0,20 14640 347444227
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libcom_err.so.2.1
VBoxXPCOM 29925 root mem REG 0,20 141752 347443108
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/liblzma.so.5.0.0
VBoxXPCOM 29925 root mem REG 0,20 31784 347443196
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/librt-2.19.so
VBoxXPCOM 29925 root mem REG 0,20 109144 347443106
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libz.so.1.2.8
VBoxXPCOM 29925 root mem REG 0,20 35176 347443180
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libcrypt-2.19.so
VBoxXPCOM 29925 root mem REG 0,20 1051056 347443195
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libm-2.19.so
VBoxXPCOM 29925 root mem REG 0,20 14664 347443175
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libdl-2.19.so
VBoxXPCOM 29925 root mem REG 0,20 1729984 347443184
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libc-2.19.so
VBoxXPCOM 29925 root mem REG 0,20 89616 347443199
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libgcc_s.so.1
VBoxXPCOM 29925 root mem REG 0,20 1537864 347428339
/tmp/piupartss/tmp9o7H4F/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21
VBoxXPCOM 29925 root mem REG 0,20 137448 347443178
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libpthread-2.19.so
VBoxXPCOM 29925 root mem REG 0,20 140928 347443189
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/ld-2.19.so
VBoxXPCOM 29925 root mem REG 0,20 26258 347428461
/tmp/piupartss/tmp9o7H4F/usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache
VBoxXPCOM 29925 root 0u CHR 1,3 0t0 347421495
/tmp/piupartss/tmp9o7H4F/dev/null
VBoxXPCOM 29925 root 1u CHR 1,3 0t0 347421495
/tmp/piupartss/tmp9o7H4F/dev/null
VBoxXPCOM 29925 root 2u CHR 1,3 0t0 347421495
/tmp/piupartss/tmp9o7H4F/dev/null
VBoxXPCOM 29925 root 3r CHR 1,9 0t0 347421500
/tmp/piupartss/tmp9o7H4F/dev/urandom
VBoxXPCOM 29925 root 4wW REG 0,20 6 347743006
/tmp/piupartss/tmp9o7H4F/tmp/.vbox-root-ipc/lock
VBoxSVC 29990 root cwd DIR 0,20 460 347411940
/tmp/piupartss/tmp9o7H4F
VBoxSVC 29990 root rtd DIR 0,20 460 347411940
/tmp/piupartss/tmp9o7H4F
VBoxSVC 29990 root mem REG 0,20 18640 347444240
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libattr.so.1.1.0
VBoxSVC 29990 root mem REG 0,20 448440 347443127
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libpcre.so.3.13.1
VBoxSVC 29990 root mem REG 0,20 23128 347443152
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libcap.so.2.24
VBoxSVC 29990 root mem REG 0,20 142744 347443144
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libselinux.so.1
VBoxSVC 29990 root mem REG 0,20 524288 347443122
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libsystemd.so.0.12.0
VBoxSVC 29990 root mem REG 0,20 47712 347443186
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libnss_files-2.19.so
VBoxSVC 29990 root mem REG 0,20 43592 347443192
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libnss_nis-2.19.so
VBoxSVC 29990 root mem REG 0,20 89104 347443181
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libnsl-2.19.so
VBoxSVC 29990 root mem REG 0,20 31632 347443179
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libnss_compat-2.19.so
VBoxSVC 29990 root mem REG 0,20 76232 347443148
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libgpg-error.so.0.16.0
VBoxSVC 29990 root mem REG 0,20 84856 347443185
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libresolv-2.19.so
VBoxSVC 29990 root mem REG 0,20 924096 347443150
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libgcrypt.so.20.0.3
VBoxSVC 29990 root mem REG 0,20 14640 347444227
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libcom_err.so.2.1
VBoxSVC 29990 root mem REG 0,20 141752 347443108
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/liblzma.so.5.0.0
VBoxSVC 29990 root mem REG 0,20 1051056 347443195
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libm-2.19.so
VBoxSVC 29990 root mem REG 0,20 31784 347443196
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/librt-2.19.so
VBoxSVC 29990 root mem REG 0,20 109144 347443106
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libz.so.1.2.8
VBoxSVC 29990 root mem REG 0,20 35176 347443180
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libcrypt-2.19.so
VBoxSVC 29990 root mem REG 0,20 1729984 347443184
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libc-2.19.so
VBoxSVC 29990 root mem REG 0,20 89616 347443199
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libgcc_s.so.1
VBoxSVC 29990 root mem REG 0,20 1537864 347428339
/tmp/piupartss/tmp9o7H4F/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.21
VBoxSVC 29990 root mem REG 0,20 14664 347443175
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libdl-2.19.so
VBoxSVC 29990 root mem REG 0,20 137448 347443178
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/libpthread-2.19.so
VBoxSVC 29990 root mem REG 0,20 140928 347443189
/tmp/piupartss/tmp9o7H4F/lib/x86_64-linux-gnu/ld-2.19.so
VBoxSVC 29990 root mem REG 0,20 26258 347428461
/tmp/piupartss/tmp9o7H4F/usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache
VBoxSVC 29990 root 0u CHR 1,3 0t0 347421495
/tmp/piupartss/tmp9o7H4F/dev/null
VBoxSVC 29990 root 1u CHR 1,3 0t0 347421495
/tmp/piupartss/tmp9o7H4F/dev/null
VBoxSVC 29990 root 2u CHR 1,3 0t0 347421495
/tmp/piupartss/tmp9o7H4F/dev/null
VBoxSVC 29990 root 3r CHR 1,9 0t0 347421500
/tmp/piupartss/tmp9o7H4F/dev/urandom
VBoxSVC 29990 root 4w REG 0,20 2572 347746555
/tmp/piupartss/tmp9o7H4F/root/.config/VirtualBox/VBoxSVC.log
VBoxSVC 29990 root 13r CHR 1,9 0t0 347421500
/tmp/piupartss/tmp9o7H4F/dev/urandom
cheers,
Andreas
virtualbox-ext-pack_5.0.6-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Control: severity -1 normal
Hi Andreas,
after discussion with upstream, I'm pretty sure this isn't a bug.
- - background info: installing or removing an extension pack uses
commands which start VBoxSVC (which drags in VBoxXPCOMIPCD). those
processes will terminate themselves after about 5 seconds (if in the
mean time there is no other vbox API activity)
- - VBoxSVC and VBoxXPCOMIPCD aren't system services, they have nothing
to do with init scripts of any flavor.
- - they're normal user processes, started on demand by any vbox api clien
t
- - like vboxmanage, which I bet is used in the virtualbox-ext-pack
install scripts
- - the processes only "happen to run as root", because the package
install is done as root (and extpack install actually needs root privs
to put files in the right place)
- - I'd say this is a semi-bogus report. yes, there is something "left
behind", but it will not be for long.
- - the install scripts could wait a bit over 5 seconds after
uninstalling the extpack... I assume that this would "fix" the problem
- - LocutusOfBorg: really a strange corner case :)
So I think we can add a sleep or something else, but I checked and in
fact in more or less 5 seconds the processes exits automatically.
I would like to close this issue, since the end user won't even notice
this problem.
cheers,
Gianfranco
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJWlSTzAAoJEPNPCXROn13ZsjgP/i7dL4WKiEL2JISsRBahkkxy
Q28+JJe5wBrxExWYdkWFy2VFagJJja1OjbR9/dmS7/tgEW8RVJiNcgtYLM3GRd7C
0xUajexhg687csoWyhgkujqNO5C6WD2eeWwUDeSUKVOj6ZK9a/6MHPA2PD3cgj32
FE/hI3s+Vfu/ZuhNsNGEm431mYw0Ipj3sR2LKZKdkT50e9azDr7AJ0bc/15lIe14
C19/XB8qyvea7nX9e5zqv3+KDnnOQM3AgucxOsdTgpZAzskBYVaT2/e39lFgHvKR
hXyl8HKcpBrncNNPJJSJZCre+aVy9/lLcpu4USNTpmoGVvjau2qgtNj+YaqaEe/a
rH7TQa0ZMmEwSekvQVGfELa+xcGZB27kLde5wOGLayKwpk0uen1S4YNwHAsVhIcG
gAUPQP+GoA/qql0iOWiTdtgVq1qYyoPMwrsU5vXUa2wVu9dOFo6e4sWtEe5XWlqw
MxzzEEJKm4lNS86XXDPldv/3lyINJSwcR0Q2LIrk7zVYg4K3TujCNPBO0LtGV1f9
1jzPzjKqoGAor5Cx0xtlpJ0g3/WrjW/0Cr0DBWg50VNl8eO+WqTznb7ENJ+BSKsM
xncDNaiu+TGW78oSUaANQeSq3MNDmplw1Poq+B4QY75IpVqMut6TE9dxEvmHBpFf
w9X9QW34V9Qv2Vkyo9BW
=tRil
-----END PGP SIGNATURE-----
--- End Message ---
