vboxweb.service: Failed with result 'protocol' on Kernel 5.8.0-16.17-generic 5.8.0

Bug #1892214 reported by bbhtt
54
This bug affects 13 people
Affects Status Importance Assigned to Milestone
Virtualbox
New
Undecided
Unassigned
virtualbox (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

# systemctl status:

● vboxweb.service - VirtualBox Web Service
     Loaded: loaded (/lib/systemd/system/vboxweb.service; enabled; vendor preset: enabled)
     Active: failed (Result: protocol) since Wed 2020-08-19 12:36:18 UTC; 2h 59min ago
    Process: 3137 ExecStart=/usr/lib/virtualbox/vboxweb-service.sh start (code=exited, status=0/SUCCESS)

Aug 19 12:36:18 kortewegdevries systemd[1]: Starting VirtualBox Web Service...
Aug 19 12:36:18 kortewegdevries systemd[1]: vboxweb.service: Can't open PID file /run/vboxweb.pid (yet?>
Aug 19 12:36:18 kortewegdevries systemd[1]: vboxweb.service: Failed with result 'protocol'.
Aug 19 12:36:18 kortewegdevries systemd[1]: Failed to start VirtualBox Web Service.

# journalctl -b 0|egrep "virt|vbox"

**Attached [1]**

# cat /usr/lib/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.pid

[Install]
WantedBy=multi-user.target

# cat /proc/version_signature

Ubuntu 5.8.0-16.17-generic 5.8.0

# lsb_release -a

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Groovy Gorilla (development branch) (*proposed)
Release: 20.10
Codename: groovy

# dpkg -l

virtualbox 6.1.12-dfsg-9:amd64

# sudo bootctl status

systemd-boot not installed in ESP.
System:
     Firmware: n/a (n/a)
  Secure Boot: disabled
   Setup Mode: setup
 Boot into FW: supported

Current Boot Loader:
      Product: n/a
     Features: ✗ Boot counting
               ✗ Menu timeout control
               ✗ One-shot menu timeout control
               ✗ Default entry control
               ✗ One-shot entry control
               ✗ Support for XBOOTLDR partition
               ✗ Support for passing random seed to OS
               ✗ Boot loader sets ESP partition information
          ESP: n/a
         File: └─n/a

Random Seed:
 Passed to OS: no
 System Token: not set
       Exists: no

Available Boot Loaders on ESP:
          ESP: /boot/efi (/dev/disk/by-partuuid/d0198c7a-515a-4977-b9f8-b9d6a4f4c792)
         File: └─/EFI/BOOT/BOOTX64.EFI

Boot Loaders Listed in EFI Variables:
        Title: ubuntu
           ID: 0x0001
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/d0198c7a-515a-4977-b9f8-b9d6a4f4c792
         File: └─/EFI/ubuntu/shimx64.efi

Boot Loader Entries:
        $BOOT: /boot/efi (/dev/disk/by-partuuid/d0198c7a-515a-4977-b9f8-b9d6a4f4c792)

Had to install virtualbox turning secure boot off, virtualbox itself works fine but this service fails to start with secure boot on/off.

Tags: groovy
Revision history for this message
bbhtt (bbhtt) wrote :
tags: added: groovy
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virtualbox (Ubuntu):
status: New → Confirmed
Revision history for this message
Vasya Pupkin (shadowlmd) wrote :

Happens on a fresh Ubuntu 20.20 install.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.