Public bug reported:
The systemd file that was shipped in focal contains:
...
[Service]
Type=forking
ExecStart=/usr/lib/virtualbox/vboxweb-service.sh start
PIDFile=/run/vboxweb.pid
...
But the script that it calls uses a different file for PID:
cat /usr/lib/virtualbox/vboxweb-service.sh:
...
SCRIPTNAME=vboxweb-service.sh
...
PIDFILE="/var/run/${SCRIPTNAME}"
...
Which causes the unit to fail on my system.
I think the script is wrong but since I find it easier to track I fixed
this by copying the systemd unit to /etc and changing it there.
cat /etc/systemd/system/vboxweb.service:
[Unit]
Description=VirtualBox Web Service
After=network.target
[Service]
Type=forking
ExecStart=/usr/lib/virtualbox/vboxweb-service.sh start
PIDFile=/run/vboxweb-service.sh
[Install]
WantedBy=multi-user.target
Which works fine after doing a systemctl daemon-reload.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-53.59-lowlatency 5.4.65
Uname: Linux 5.4.0-53-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 13 09:15:47 2020
SourcePackage: virtualbox
UpgradeStatus: Upgraded to focal on 2020-05-07 (189 days ago)
mtime.conffile..etc.default.virtualbox: 2020-07-18T01:32:05.356307
** Affects: virtualbox (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904123
Title:
Mismatch between vboxweb.service systemd file and startup script
causes unit to fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1904123/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
