Guest: Lubuntu 15.10 (yes, I KNOW it is out of service!), Guest Additions 5.1.10
[The following problem is NOT new since 5.1.10. I guess it has always been in the 15.10 system.]
vboxadd-service.service fails to load at systemd boot.
Any wizard around here who can shed some light on VBoxService nonzero return codes and how to debug them?
From journalctl:
Nov 26 19:04:36 LUB64MAIL vboxadd.sh[1044]: .
Nov 26 19:04:36 LUB64MAIL systemd[1]: Started vboxadd.service.
Nov 26 19:04:36 LUB64MAIL systemd[1]: Starting vboxadd-service.service...
Nov 26 19:04:36 LUB64MAIL vboxadd-service[1046]: vboxadd-service.sh: Starting VirtualBox Guest Addition service.
Nov 26 19:04:36 LUB64MAIL vboxadd-service.sh[1049]: Starting VirtualBox Guest Addition service.
Nov 26 19:04:36 LUB64MAIL vboxadd-service.sh[1053]: VirtualBox Guest Addition service started.
Nov 26 19:04:36 LUB64MAIL systemd[1]: vboxadd-service.service: Control process exited, code=exited status=1
Nov 26 19:04:36 LUB64MAIL systemd[1]: Failed to start vboxadd-service.service.
Nov 26 19:04:36 LUB64MAIL systemd[1]: vboxadd-service.service: Unit entered failed state.
Nov 26 19:04:36 LUB64MAIL systemd[1]: vboxadd-service.service: Failed with result 'exit-code'.
Manually starting the service after boot with
sudo systemctl start vboxadd-service.service
also fails:
Nov 26 19:12:50 LUB64MAIL polkitd(authority=local)[858]: Registered Authentication Agent for unix-process
54653 (system bus name :1.38 [/usr/bin/pkttyagenNov 26 19:12:50 LUB64MAIL systemd[1]: Starting vboxadd-service.service...
Nov 26 19:12:50 LUB64MAIL vboxadd-service[1923]: vboxadd-service.sh: Starting VirtualBox Guest Addition service.
Nov 26 19:12:50 LUB64MAIL vboxadd-service.sh[1926]: Starting VirtualBox Guest Addition service.
Nov 26 19:12:50 LUB64MAIL vboxadd-service.sh[1930]: VirtualBox Guest Addition service started.
Nov 26 19:12:50 LUB64MAIL systemd[1]: vboxadd-service.service: Control process exited, code=exited status=1
Nov 26 19:12:50 LUB64MAIL systemd[1]: Failed to start vboxadd-service.service.
Nov 26 19:12:50 LUB64MAIL systemd[1]: vboxadd-service.service: Unit entered failed state.
Nov 26 19:12:50 LUB64MAIL systemd[1]: vboxadd-service.service: Failed with result 'exit-code'.
Nov 26 19:12:50 LUB64MAIL polkitd(authority=local)[858]: Unregistered Authentication Agent for unix-process
54653 (system bus name :1.38, object path /orgHowever, directly calling the VBoxService executable with
sudo /usr/sbin/VBoxService --pidfile /var/run/vboxadd-service.sh
(this is actually the line taken from /opt/VBoxGuestAdditions-5.1.10/init/vboxadd-service )
seems to work:
Nov 26 19:18:46 LUB64MAIL kernel: VBoxService 5.1.10 r112026 (verbosity: 0) linux.amd64 (Nov 21 2016 17:44:44) release log
00:00:00.000758 main Log opened 2016-11-26T18:18:46.399849000Z
Nov 26 19:18:46 LUB64MAIL systemd-tmpfiles[1984]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Nov 26 19:18:46 LUB64MAIL kernel: 00:00:00.039553 main OS Product: Linux
Nov 26 19:18:46 LUB64MAIL kernel: 00:00:00.039802 main OS Release: 4.2.0-42-generic
Nov 26 19:18:46 LUB64MAIL kernel: 00:00:00.039881 main OS Version: #49-Ubuntu SMP Tue Jun 28 21:26:26 UTC 2016
Nov 26 19:18:46 LUB64MAIL kernel: 00:00:00.039922 main Executable: /opt/VBoxGuestAdditions-5.1.10/sbin/VBoxService
00:00:00.039924 main Process ID: 1981
00:00:00.039925 main Package type: LINUX_64BITS_GENERIC
Nov 26 19:18:46 LUB64MAIL systemd[1]: Starting Cleanup of Temporary Directories...
Nov 26 19:18:46 LUB64MAIL kernel: 00:00:00.056869 main 5.1.10 r112026 started. Verbose level = 0
Nov 26 19:18:46 LUB64MAIL kernel: 00:00:00.085576 main Service 'memballoon' was disabled because of missing functionality
Nov 26 19:18:46 LUB64MAIL systemd[1]: Started Cleanup of Temporary Directories.
Note: I have a second system here that is identical (as I hope/assume/expect) to the system above, except for the disk configuration. This second system does NOT show the error!
The difference is that the failing system has one VBox-encrypted disk-image attached, while the other system's disks are not VBox-encrypted. I believe that this is the only difference (from a system-setup point-of-view).