Virtualbox-Plugin not installable

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Virtualbox-Plugin not installable

      Hello together,

      I did an update from OMV 3.x to 4.1.9 using omv-release-upgrade. I have made sure that all installed plugins are already prepared for 4.x (in my case: autoshutdown, nut, omvextrasorg and virtualbox).

      There were no errors during the process. But the virtualbox-plugin doesn't work. It is not installed anymore, just the config files are present:

      Source Code

      1. $ sudo dpkg -l | grep openmediavault
      2. [...]
      3. rc openmediavault-virtualbox 3.0.8 all VirtualBox plugin for OpenMediaVault.

      I tried to install it manually, but I got:

      Source Code

      1. $ sudo LANG=en_US.UTF-8 apt-get install openmediavault-virtualbox
      2. Reading package lists... Done
      3. Building dependency tree
      4. Reading state information... Done
      5. Some packages could not be installed. This may mean that you have
      6. requested an impossible situation or if you are using the unstable
      7. distribution that some required packages have not yet been created
      8. or been moved out of Incoming.
      9. The following information may help to resolve the situation:
      10. The following packages have unmet dependencies:
      11. openmediavault-virtualbox : Depends: phpvirtualbox but it is not going to be installed
      12. Depends: virtualbox but it is not going to be installed
      13. Depends: virtualbox-ext-pack but it is not installable or
      14. virtualbox-ext-pack-installer but it is not going to be installed
      15. E: Unable to correct problems, you have held broken packages.
      Display All

      Trying to install the packages manually doesn't help, I got:


      Source Code

      1. $ sudo LANG=en_US.UTF-8 apt-get install virtualbox
      2. Reading package lists... Done
      3. Building dependency tree
      4. Reading state information... Done
      5. Some packages could not be installed. This may mean that you have
      6. requested an impossible situation or if you are using the unstable
      7. distribution that some required packages have not yet been created
      8. or been moved out of Incoming.
      9. The following information may help to resolve the situation:
      10. The following packages have unmet dependencies:
      11. virtualbox : Depends: python3 (< 3.5) but 3.5.3-1 is to be installed
      12. Depends: python3.4 but it is not installable
      13. Depends: libgsoap5 but it is not installable
      14. Depends: libpng12-0 (>= 1.2.13-4) but it is not installable
      15. Depends: libpython3.4 (>= 3.4.2~rc1) but it is not installable
      16. Depends: libvncserver0 (>= 0.9.9) but it is not installable
      17. Depends: libvpx1 (>= 1.0.0) but it is not installable
      18. E: Unable to correct problems, you have held broken packages.
      Display All


      It seems that my ?( OMV 4.x are using a version of Python which is to new, right?

      Any ideas to get openmediavault-virtualbox running?

      Thanks in advance,
      Freed
    • Did you disable the backports repo? You need to have it enabled for virtualbox since it is only in the stretch backports repo. There is a button omv-extras to enable backports.
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      Did you disable the backports repo? You need to have it enabled for virtualbox since it is only in the stretch backports repo. There is a button omv-extras to enable backports.
      Hey,

      maybe I'm blind. But I can't find a button for enabling backports in the UI... have a look on my screenshot.

      Thanks for a hint for the blind ones... :rolleyes:

      Regards
      Freed
      Images
      • omv_screenshot.jpg

        58.19 kB, 843×430, viewed 68 times
    • freed wrote:

      But I can't find a button for enabling backports in the UI
      You either need to clear your browser cache or you aren't running omv-extras 4.1.7 or newer.
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      You either need to clear your browser cache or you aren't running omv-extras 4.1.7 or newer.
      It is the second one: I'm running omv-extras 3.4.32 - this is the version my UI presents, look at my screenshot.

      How can I do an update if this version is not presented by the frontend?

      Maybe I found a mistake myself, look at this:

      Source Code

      1. $ cat omv-extras-org.list
      2. # This is file is generated.
      3. # OMV-Extras repos
      4. #
      5. # OMV-Extras.org
      6. deb https://dl.bintray.com/openmediavault-plugin-developers/erasmus jessie main
      Maybe it should be "arrakis" instead of "erasmus" and "stretch" instead of "jessie"? If this is the case, there might be a bug in omv-release-upgrade...

      BTW: browser cache is cleared.

      Thanks again,
      Freed
      Images
      • omv_screenshot2.jpg

        56.68 kB, 787×351, viewed 82 times

      The post was edited 2 times, last by freed ().

    • freed wrote:

      How can I do an update if this version is not presented by the frontend?
      Your omv-extras didn't get upgraded in your upgrade then. As root: wget -O - http://omv-extras.org/install | bash
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Okay! After wget -O - omv-extras.org/install | bash the installation of the virtualbox-plugin was possible! Thanks a lot.

      Now there is a new issue: if I hit VirtualBox -> Virtual Machines, I got this alert box over and over again:


      Source Code

      1. Could not connect to host (http://127.0.0.1:18083/)
      2. Error #0:
      3. Exception: Could not connect to host (http://127.0.0.1:18083/) in /usr/share/phpvirtualbox/endpoints/lib/vboxconnector.php:220
      4. Stack trace:
      5. #0 /usr/share/openmediavault/engined/rpc/virtualbox.inc(136): vboxconnector->connect()
      6. #1 [internal function]: OMV\Engined\Rpc\VirtualBox->getMachines(Array, Array)
      7. #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      8. #3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('getMachines', Array, Array)
      9. #4 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('VirtualBox', 'getMachines', Array, Array, 1)
      10. #5 {main}
      Any further ideas?
    • freed wrote:

      Any further ideas?
      The vbox module probably didn't compile. What is the output of:

      lsmod | grep vbox
      dpkg -l | grep linux-
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      The vbox module probably didn't compile. What is the output of:
      lsmod | grep vbox
      dpkg -l | grep linux-

      Source Code

      1. # lsmod | grep vbox
      2. vboxpci 24576 0
      3. vboxnetadp 28672 0
      4. vboxnetflt 28672 0
      5. vboxdrv 466944 3 vboxnetadp,vboxnetflt,vboxpci


      Source Code

      1. # dpkg -l | grep linux-
      2. ii firmware-linux-free 3.4 all Binary firmware for various drivers in the Linux kernel
      3. ii firmware-linux-nonfree 20170823-1~bpo9+1 all Binary firmware for various drivers in the Linux kernel (meta-package)
      4. ii linux-base 4.5 all Linux image base package
      5. ii linux-compiler-gcc-4.9-x86 4.9.88-1+deb9u1~bpo8+1 amd64 Compiler for Linux on x86 (meta-package)
      6. ii linux-compiler-gcc-6-x86 4.17.8-1~bpo9+1 amd64 Compiler for Linux on x86 (meta-package)
      7. ii linux-headers-4.17.0-0.bpo.1-amd64 4.17.8-1~bpo9+1 amd64 Header files for Linux 4.17.0-0.bpo.1-amd64
      8. ii linux-headers-4.17.0-0.bpo.1-common 4.17.8-1~bpo9+1 all Common header files for Linux 4.17.0-0.bpo.1
      9. ii linux-headers-4.9.0-0.bpo.6-amd64 4.9.88-1+deb9u1~bpo8+1 amd64 Header files for Linux 4.9.0-0.bpo.6-amd64
      10. ii linux-headers-4.9.0-0.bpo.6-common 4.9.88-1+deb9u1~bpo8+1 all Common header files for Linux 4.9.0-0.bpo.6
      11. ii linux-headers-amd64 4.17+95~bpo9+1 amd64 Header files for Linux amd64 configuration (meta-package)
      12. ii linux-image-4.17.0-0.bpo.1-amd64 4.17.8-1~bpo9+1 amd64 Linux 4.17 for 64-bit PCs
      13. rc linux-image-4.9.0-0.bpo.3-amd64 4.9.30-2+deb9u5~bpo8+1 amd64 Linux 4.9 for 64-bit PCs
      14. ii linux-image-4.9.0-0.bpo.4-amd64 4.9.65-3+deb9u1~bpo8+1 amd64 Linux 4.9 for 64-bit PCs
      15. ii linux-image-4.9.0-0.bpo.5-amd64 4.9.65-3+deb9u2~bpo8+1 amd64 Linux 4.9 for 64-bit PCs
      16. ii linux-image-4.9.0-0.bpo.6-amd64 4.9.88-1+deb9u1~bpo8+1 amd64 Linux 4.9 for 64-bit PCs
      17. ii linux-image-4.9.0-7-amd64 4.9.110-3+deb9u1 amd64 Linux 4.9 for 64-bit PCs
      18. ii linux-image-amd64 4.17+95~bpo9+1 amd64 Linux for 64-bit PCs (meta-package)
      19. ii linux-kbuild-4.17 4.17.8-1~bpo9+1 amd64 Kbuild infrastructure for Linux 4.17
      20. ii linux-kbuild-4.9 4.9.110-3+deb9u1 amd64 Kbuild infrastructure for Linux 4.9
      21. ii linux-libc-dev:amd64 4.9.110-3+deb9u1 amd64 Linux support headers for userspace development
      Display All
    • Well, it compiled and the module is loaded. What is the output of: ps aux | grep vb
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:

      Well, it compiled and the module is loaded. What is the output of: ps aux | grep vb

      Source Code

      1. # ps aux | grep vb
      2. vbox 718 0.0 0.1 538888 19548 ? Ssl 21:42 0:00 /usr/lib/virtualbox/vboxwebsrv --host 127.0.0.1 --port 18083
      3. vbox 922 0.0 0.0 164312 13232 ? S 21:42 0:00 /usr/lib/virtualbox/VBoxXPCOMIPCD
      4. vbox 1003 0.1 0.1 599348 21208 ? Sl 21:42 0:00 /usr/lib/virtualbox/VBoxSVC --auto-shutdown
      5. root 2434 0.0 0.0 12788 956 pts/0 S+ 21:42 0:00 grep vb

      Maybe this is interesting, too:

      Source Code

      1. # netstat -tulpen | grep vb
      2. tcp 0 0 127.0.0.1:18083 0.0.0.0:* LISTEN 997 22067 718/vboxwebsrv

      Greetings
      Freed

      The post was edited 1 time, last by freed ().

    • Well, the issue "alert box" is gone away. :/ I did a reboot and relogged into the webinterface. Thanks a lot!!

      But there is another (last?) one: phpVirtualBox gives:

      Source Code

      1. Error 404
      2. Sorry, the page you requested was not found.

      Is there an idea for this, too?

      Thanks a million,
      Freed
    • freed wrote:

      Is there an idea for this, too?
      What is the output of: dpkg -l | grep phpvirtualbox
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Source Code

      1. # dpkg -l | grep phpvirtualbox
      2. ii phpvirtualbox 5.2-0-1 all Web interface for VirtualBox.
      It looks fine, doesn't it?

      I also did apt-get install --reinstall phpvirtualbox, I tried dpkg-reconfigure openmediavault-virtualbox, dpkg-reconfigure phpvirtualbox and service nginx restart, but it has no effect.

      Some amateur considerations: should not be found in /etc/nginx/sites-available/ a reference to /usr/share/phpvirtualbox/? At the moment this directory looks just like this:

      Source Code

      1. # ls -al /etc/nginx/sites-available/
      2. insgesamt 16
      3. drwxr-xr-x 2 root root 4096 Aug 12 10:27 .
      4. drwxr-xr-x 9 root root 4096 Aug 11 11:29 ..
      5. -rw-r--r-- 1 root root 2416 Jul 12 2017 default
      6. -rw-r--r-- 1 root root 1307 Aug 11 11:30 openmediavault-webgui

      Unfortunately, I'm not very good with nginx, but in an apache2 configuration I would expect that ... or will it be bent somewhere else? If something is missing here, the question would be, what exactly you have to generate there?!? ?(

      The post was edited 3 times, last by freed ().

    • freed wrote:

      should not be found in /etc/nginx/sites-available/ a reference to /usr/share/phpvirtualbox/?
      Nope. phpvirtualbox uses the omv web interface's nginx server and adds a config file here - /etc/nginx/openmediavault-webgui.d/openmediavault-virtualbox.conf

      Does the following help:
      omv-mkconf nginx
      omv-mkconf php-fpm
      systemctl restart nginx
      systemctl restart php7.0-fpm

      If not, I would purge the plugin, virtualbox packages, virtualbox users and groups, delete /etc/default/openmediavault-virtualbox and /etc/default/virtualbox, then reinstall.
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Yeah, it works!!! :) :) :) :thumbsup:


      In fact, the file /etc/nginx/openmediavault-webgui.d/openmediavault-virtualbox.conf was missing - your omv-mkconf did it.


      Just to be smarter next time: what probably went wrong with the upgrade?


      In any case, thank you very much for your intensive, sustained and patient help!
      Freed
    • freed wrote:

      what probably went wrong with the upgrade?
      I'm not really sure. It must have been in a weird state where it didn't think the nginx/php-fpm setup had changed.
      omv 4.1.15 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!