Latest debian update breaks VirtualBox/phpVirtualBox plugin?

  • Not sure of it though,


    the problems started appearing after yesterday (02.02.) update - I didn't notice any omv or plugin specific updates but what it looked like general ones for OS. I'm sorry now I didn't write it down :( I'm pretty sure backport 4.9.0 was among theese.


    Anyways, upon reboot OMV wouldn't connect to phpVirtualBox throwing error:

    Code
    Error #0:
    exception 'Exception' with message 'Could not connect to host (http://127.0.0.1:18083/)' in /usr/share/phpvirtualbox/endpoints/lib/vboxconnector.php:220
    Stack trace:
    #0 /usr/share/openmediavault/engined/rpc/virtualbox.inc(136): vboxconnector->connect()
    #1 [internal function]: OMV\Engined\Rpc\VirtualBox->getMachines(Array, Array)
    #2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
    #3 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('getMachines', Array, Array)
    #4 /usr/sbin/omv-engined(516): OMV\Rpc\Rpc::call('VirtualBox', 'getMachines', Array, Array, 1)
    #5 {main}

    Any attempt to disable phpVirtualBox is met with Bad Gateway error and ultimately spits this out:


    This is what syslog says:


    Code
    Feb  3 08:09:02 nas systemd[1]: Starting LSB: VirtualBox Linux kernel module...
    Feb  3 08:09:02 nas systemd[1]: Failed to reset devices.list on /system.slice: Invalid argument
    Feb  3 08:09:02 nas virtualbox[5456]: Loading VirtualBox kernel modules...No suitable module for running kernel found ... failed!
    Feb  3 08:09:02 nas virtualbox[5456]: failed!
    Feb  3 08:09:02 nas systemd[1]: virtualbox.service: control process exited, code=exited status=1
    Feb  3 08:09:02 nas systemd[1]: Failed to start LSB: VirtualBox Linux kernel module.
    Feb  3 08:09:02 nas systemd[1]: Dependency failed for VirtualBox Web Service.
    Feb  3 08:09:02 nas systemd[1]: Unit virtualbox.service entered failed state.


    I also tried removing then installing the plugin again ( the windows way :D:D:D ) with same results - I've since completely disabled it.


    Anyone knows more about this? Looks like borked/missing kernel module?

    OMV erasmus 3.0.90 | omv-extras 3.4.29 | Xeon E3 1225 | 8GB ECC RAM | 2x3 TB WD Red | 1.5 TB WD Green | 1TB HGST

    • Offizieller Beitrag

    Anyone knows more about this? Looks like borked/missing kernel module?

    New kernels typically require new code in things that compile kernel modules like virtualbox, zfs, iscsi, etc. You will just have to use the 4.8 kernel (which should still be on your system and you can set it to boot with omv-extras) until virtualbox is fixed.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • thanks for input - i'll wait for 4.9.0 compatibility


    vbox is not critical service for me

    OMV erasmus 3.0.90 | omv-extras 3.4.29 | Xeon E3 1225 | 8GB ECC RAM | 2x3 TB WD Red | 1.5 TB WD Green | 1TB HGST

  • Hi,


    for all others with the same problem following is a work around to get virtualbox running incl. phpvirtualbox


    1. login via SSH as root
    2. download the Linux headers

    Bash
    apt-get install linux-headers-$(uname -r)



    3. reconfigure virtualbox


    Bash
    dpkg-reconfigure virtualbox-dkms
    dpkg-reconfigure virtualbox


    4. edit /usr/share/phpvirtualbox/endpoints/api.php


    PHP
    //$response['data']['responseData']['phpvboxver'] = @constant('PHPVBOX_VER');
    $response['data']['responseData']['phpvboxver'] = "5.1-0";


    This worked for my OMV 3.0.8 with Kernel 4.9.0-0.bpo.3-amd64.


    Andy

  • Hi Andy


    thanks man, this fixed it for me!


    Manne


    edit: to clarrify.


    my first install was with the download iso to OMV3 with kernel .7 or .8 where i installed virtualbox via webui, then upgraded the kernel and ended with a broken virtualbox. i followed all the above steps, and it made it work again. that was my test enviroment.


    today i started with the same iso on my production server. but this time I first updated, then installed virtualbox form UI


    so this time I only needed step4 of the above guide, just to fix an anoying warning about some combatibillity issue.


    this was not clear on me, the first time I come here to find a solution, that actually I had broken the virtualbox, not "was broaken out of the box".


    entirely my fault.


    cheers manne

  • wie komme ich dort hin ins 4. edit /usr/share/phpvirtualbox/endpoints/api.php Verzeichnis
    über putty geht es nicht



    how do I get there to the 4th edit /usr/share/phpvirtualbox/endpoints/api.php directory
    it's not about putty

  • klar über putty


    putty öffnen dann ip vom server + port 22 + ssh eingeben/wählen und "open" klicken


    login mit user root und kennwort vom aufsetzen des OMV servers,


    ich persönlich nutzt vim, daher wäre beim OMv dann noch


    apt-get update && apt-get install vim


    nötig, um vim zu installieren. (folgende anlietung ist für vim, geht natürlich auch mit jedem anderen editor)


    danach dann: vim /usr/share/phpvirtualbox/endpoints/api.php



    dann mit /phpvboxver + Enter die Zeile suchen. bei mir ist es zeile 86



    mit i in den editor modus springen, die betroffene zeile mit // am Zeilenanfang auskommentieren, dann am Zeilenende ein Enter, und mit tab die Leerzeichen am anfang generieren, dann abtippen oder per copy paste (putty: rechte maustaste für einfügen) reinhaun.



    Editor modus mit ESC beenden.
    :wq +Enter für speichern, beenden



    exit um putty zu verlassen


    fertig.

  • Moin auch ich habe das Problem seit dem ich das letzte Update gestern gemacht habe, kann ich VirtualBox nicht mehr Starten. Wenn ich das OMV Interface aufrufe bekomme ich eine Meldung


    Code
    Could not connect to host (http://127.0.0.1:18083/)



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


    Diese schritte habe ich schon mehrfach ausgeführt leider kein erfolg



Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!