problem updating virtualbox & virtualvox-extpack-install

    • Resolved
    • OMV 1.0
    • problem updating virtualbox & virtualvox-extpack-install

      Hi beautiful peoples!

      Virtualbox and virtualvox-extpack-install last update, I have this error message

      Source Code

      1. Preparing to replace virtualbox-4.3 4.3.18-96516~Debian~wheezy (using .../virtualbox-4.3_4.3.20-96996~Debian~wheezy_amd64.deb) ...
      2. dpkg: warning: subprocess old pre-removal script returned error exit status 1
      3. dpkg: trying script from the new package instead ...
      4. dpkg: error processing /var/cache/apt/archives/virtualbox-4.3_4.3.20-96996~Debian~wheezy_amd64.deb (--unpack):
      5. subprocess new pre-removal script returned error exit status 1
      6. Errors were encountered while processing:
      7. /var/cache/apt/archives/virtualbox-4.3_4.3.20-96996~Debian~wheezy_amd64.deb
      8. Creating index of upgradeable packages ...
      9. Creating index of OpenMediaVault plugins ...
      10. E: Sub-process /usr/bin/dpkg returned an error code (1)


      but when I try to apt-get -f install, I get to do the upgrade virtualbox I still have that damn message saying

      Running VMs found

      VirtualBox is currently running. Please close it and try again. Please x
      note that it can take up to ten seconds for VirtualBox (in particular x
      the VBoxSVC daemon) to finish running.


      and..

      Source Code

      1. The following packages have unmet dependencies:
      2. virtualbox-extpack-installer : Depends: virtualbox-4.3 (>= 4.3.20) but 4.3.18-96516~Debian~wheezy is installed
      3. E: Unmet dependencies. Try using -f.


      tanks
      NeurOSick
      Hardware ASRock N68C-GS, AMD FX-4100 8GB RAM
      OMV3 Distro + OMV-Extra + Docker + OpenVPN = Unlimited possibilities!

    • I always stop my VMs to upgrade vbox. Try stopping them and then apt-get -f install.
      omv 4.1.11 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      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:

      I always stop my VMs to upgrade vbox. Try stopping them and then apt-get -f install.


      ok tanks, solved by killing all the PID 3 vboxwebsrv, VBoxXPCOMIPCD and VBoxSVC.

      I was not able to stop the daemons, so I used this technique. Is it that there was an easier way?

      merci,
      NeurOSick
      Hardware ASRock N68C-GS, AMD FX-4100 8GB RAM
      OMV3 Distro + OMV-Extra + Docker + OpenVPN = Unlimited possibilities!

    • I usually don't have to stop the daemons. Just the VMs. I guess you could just disable virtualbox using the plugin and try upgrading that way.
      omv 4.1.11 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.11
      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!