VirtualBox error "Could not connect to host (http://127.0.0.1:18083/)"

    • OMV 1.0
    • Resolved
    • VirtualBox error "Could not connect to host (http://127.0.0.1:18083/)"

      Hello there.

      Got a strange error with virtualbox plugin. Each time I access the webgui of openmediavault, I get this message : "Could not connect to host (127.0.0.1:18083/)". Pressing details give me this :

      Source Code

      1. Erreur #64:
      2. exception 'Exception' with message 'Could not connect to host (http://127.0.0.1:18083/)' in /usr/share/phpvirtualbox/lib/vboxconnector.php:210
      3. Stack trace:
      4. #0 /usr/share/openmediavault/engined/rpc/virtualbox.inc(176): vboxconnector->connect()
      5. #1 [internal function]: OMVRpcServiceVirtualBox->getMachines(Array, Array)
      6. #2 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
      7. #3 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('getMachines', Array, Array)
      8. #4 /usr/sbin/omv-engined(501): OMVRpc::exec('VirtualBox', 'getMachines', Array, Array, 1)
      9. #5 {main}


      running Kralizec, with some plugins (sickbeard, couchpotato, sabnzbd, headphones and pyload, all working fine). I installed the virtualbox plugin yesterday, installed two VM which worked fine. This morning, I went back to the gui and no more access to the phpvirtualbox interface. And that was before I upgraded to 1.0.22. Already tried to reboot the system, but problem is still there.

      any logs I can post to help find my problem ?

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

    • as a matter of fact, the process wasn't running at all (always get an error during boot time but too quick to read it). After starting manually the service "/etc/init.d/vboxweb-service start", stopping it "/etc/init.d/vboxweb-service stop" and starting it again, problem is gone.

      not sure of what happened (didn't change anything at all) but it's actually solved... ?(
    • gamin wrote:

      as a matter of fact, the process wasn't running at all (always get an error during boot time but too quick to read it). After starting manually the service "/etc/init.d/vboxweb-service start", stopping it "/etc/init.d/vboxweb-service stop" and starting it again, problem is gone.

      not sure of what happened (didn't change anything at all) but it's actually solved... ?(

      the same problem ..
      now trying to deal with it and find a reason ...
      omv 1.0.29 kralizec | 64 bit | 3.2.0-4 kernel | omvextrasorg 1.0.13 (Sorry for my bad english...)
    • Virtualbox probably isnt running because your kernel module is not compiled for your kernel. ;)

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • davidh2k wrote:

      Virtualbox probably isnt running because your kernel module is not compiled for your kernel. ;)

      Greetings
      David

      Before reinstall OMV - worked ..
      Pls, say me command prompt to reset the console package virtualbox (reinstall)
      i search this command in FAQ - no see -((
      Something similar to apt-get reinstall virtualbox.... etc.. =)
      omv 1.0.29 kralizec | 64 bit | 3.2.0-4 kernel | omvextrasorg 1.0.13 (Sorry for my bad english...)
    • /etc/init.d/vboxdrv setup

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • davidh2k wrote:

      /etc/init.d/vboxdrv setup

      Greetings
      David



      At the time of installation - Internet connection lost
      Virtualbox is visible in the WEB-panel (which is installed) .. but in the plugin - says "not installed" ..
      How can this be fixed a?

      Source Code

      1. root@openmedia:~# /etc/init.d/vboxdrv setup
      2. Stopping VirtualBox kernel modules ...failed!
      3. (Cannot unload module vboxdrv)
      4. root@openmedia:~#
      omv 1.0.29 kralizec | 64 bit | 3.2.0-4 kernel | omvextrasorg 1.0.13 (Sorry for my bad english...)
    • You're welcome.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • stalkerxxl wrote:

      I have solved the problem =)

      Source Code

      1. dpkg --configure -a
      it helped me...
      Thx, David for you patience for my noob questions =)

      This - not the solution .. I was wrong ...
      After clonezilla-backup and rebooting - the problem is back ...
      Could not connect to host (127.0.0.1:18083/)

      Solved only in this way:

      Source Code

      1. root@openmedia:~# service vboxdrv restart Stopping VirtualBox kernel modules ...done. Starting VirtualBox kernel modules ...done. root@openmedia:~# service vboxweb-service restart Stopping VirtualBox web serviceNo /usr/lib/virtualbox/vboxwebsrv found running; none killed. ...done. root@openmedia:~# service vboxweb-service start Starting VirtualBox web service ...done. root@openmedia:~#

      I think it's a priority startup services .. should lower the priority of VirtualBox web service?
      ===================add============
      а... VirtualBox web serviceNo /usr/lib/virtualbox/vboxwebsrv found running; none killed - service is no autostart....
      omv 1.0.29 kralizec | 64 bit | 3.2.0-4 kernel | omvextrasorg 1.0.13 (Sorry for my bad english...)
    • Normal solution should be to let vbox recompile the kernel module. The command for that should be in this thread.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • You're welcome.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Hallo zusammen

      Habe ebenfalls das Problem, dass ich in 9 von 10 Fällen nach dem booten folgende Fehlermeldung nach Anmedlung im WefIf erhalte: Could not connect to host (127.0.0.1:18083/)

      Die Maschine kann eigentlich nicht zu langsam sein:
      ================================================================================
      = OS/Debian information
      ================================================================================
      Distributor ID: debian
      Description: Debian GNU/Linux 7 (wheezy)
      Release: 7.7
      Codename: wheezy

      ================================================================================
      = OpenMediaVault information
      ================================================================================
      Release: 1.5
      Codename: Kralizec

      ================================================================================
      = Date
      ================================================================================
      Mo 8. Dez 22:08:46 CET 2014

      ================================================================================
      = Locale
      ================================================================================
      de_DE.UTF-8

      ================================================================================
      = System information
      ================================================================================
      Linux nas001 3.16-0.bpo.2-amd64 #1 SMP Debian 3.16.3-2~bpo70+1 (2014-09-21) x86_64 GNU/Linux

      CPU ist eine i5 2400S mit 16GB Ram

      Habe das Gefühl, dass das Problem irgendwie mit der Kombination der installierten Plugins/Dienste zu tun hat. Habe aber noch nicht gesichert den Fehler einkreisen können.

      Fakt ist, dass ich das Problem durch Eingabe von

      /etc/init.d/vboxweb-service start

      in der Konsole beheben kann.

      Folgende Plugins/Dienste habe ich installiert/gestartet:

      Autoshutdown plugin
      Virtualbox plugin
      rsync
      SMB/CIFS
      SSH

      Habe die in diesem Thread beschriebenen Problemlösungen alle durch. Nichts half dauerhaft. Der Fehler tritt immer wieder auf.

      Hab keine Idee mehr woran es liegen kann.

      Vielleicht hat ja jemand ein ähnliches Verhalten?
    • Hast du es schonmal mit neuinstallieren von VirtualBox probiert?

      Gruß
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Hallo davidh2k

      Habe ich vorhin vergessen zu erwähnen.

      Habe Virtualbox komplett wie in einem anderen Thread beschrieben entfernt User/Dateien etc. und das Plugin dann neu installiert.

      Problem trat trotzdem wieder auf.

      In einer Virtuellen Maschine habe ich das Problem teilweise auch.
    • @all

      Nachdem ich gefühlt alle Beiträge zu Virtualbox gelesen habe und nichts half -> das Problem trat über kurz oder lang immer wieder auf, habe ich mich entschlossen das NAS neu aufzusetzen.

      1. Datenplatten abgehängt.
      2. Mit openmediavault_1.0.20_amd64.iso das System neu installiert.
      3. US Repos ausgewählt (In einem 2013 Beitrag gabs mal Probleme mit den deutschen)
      4. Nach der Installation Datenplatten wieder eingehängt und eingerichtet.
      5. Als erste Plugins omvextrasorg und Virtualbox installiert.
      6. Restliche Einstellungen vorgenommen.

      Der Neuaufbau hat mich 2 Stunden gekostet bis wieder alles lief. Aber was soll ich sagen der Fehler ist jetzt seit 2 Tagen mit mehreren Neustarts nicht wieder aufgetreten.

      Woran es jetzt lag kann ich nicht sagen.

      Vielleicht hilft das Vorgehen jemandem mit dem gleichen Problem.

      ciao