Mismatch between vboxweb.service systemd file and startup script causes unit to fail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
virtualbox (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The systemd file that was shipped in focal contains:
...
[Service]
Type=forking
ExecStart=
PIDFile=
...
But the script that it calls uses a different file for PID:
cat /usr/lib/
...
SCRIPTNAME=
...
PIDFILE=
...
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/
[Unit]
Description=
After=network.
[Service]
Type=forking
ExecStart=
PIDFile=
[Install]
WantedBy=
Which works fine after doing a systemctl daemon-reload.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: virtualbox 6.1.10-
ProcVersionSign
Uname: Linux 5.4.0-53-lowlatency x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
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.
lovely thanks!