OMV 4 on Debian 9 problem install

    • OMV 4.x
    • related generic clean WSL debian 9 install on a clean new windows 10 pro ssd install OMV 4 fails

      oh, arr , for a minute i thought YES it's alive, sadly not yet and im at a bit lost now....
      "apt-get --yes --auto-remove --show-upgraded --allow-downgrades --allow-change-held-packages --no-install-recommends --option Dpkg::Options::="--force-confdef" --option DPkg::Options::="--force-confold" --allow-unauthenticated install openmediavault"

      the adventure was to use a generic clean WSL debian 9 install on a clean new windows 10 pro ssd install and for a moment it seems to almost work...

      i needed to first give "root" a legacy password for nostalgia "toor" ,install and test a few apps every base video storage OS needs today , ffmpeg, mediainfo, vlc, mc, worker for the must have xfce4 desktop env and windows installed VcXsrv ,rebol, and a few likes for automation later, native qbittorrent-nox, Radarr nightly,Sonarr nightly and jackett installs,and/or duckieTV OBVIOUSLY :)
      and that all went fine as in they seemed to work on a quick go however the MS shenanigans are very apparent in the always
      Failed to connect to bus: No such file or directory



      ssh.service couldn't restart.
      Updating configuration ...
      Processing triggers for libc-bin (2.24-11+deb9u3) ...
      Processing triggers for systemd (232-25+deb9u3) ...
      Processing triggers for resolvconf (1.79) ...
      Processing triggers for rsyslog (8.24.0-1) ...
      invoke-rc.d: could not determine current runlevel
      Processing triggers for dbus (1.10.26-0+deb9u1) ...
      Processing triggers for openmediavault (4.1.8.2-1) ...
      Restarting engine daemon ...
      New Monit id: 85f0c2ac6b82fca174cf51d4295fbd02
      Stored in '/var/lib/monit/id'
      'omv-engined' trying to restart
      'omv-engined' start: '/bin/systemctl start openmediavault-engined'
      'omv-engined' failed to start (exit status 1) -- '/bin/systemctl start openmediavault-engined': Failed to connect to bus: No such file or directory

      Failed to connect to bus: No such file or directory
      Failed to connect to bus: No such file or directory
      openmediavault-engined.service couldn't restart.
      dpkg: error processing package openmediavault (--configure):
      subprocess installed post-installation script returned error exit status 1
      Errors were encountered while processing:
      openmediavault
      E: Sub-process /usr/bin/dpkg returned an error code (1)
      root@livingroom:/home/dave#
      root@livingroom:/home/dave# omv-initsystem
      cat: /etc/timezone: No such file or directory
      run-parts: /usr/share/openmediavault/initsystem/50timezone exited with return code 1
      root@livingroom:/home/dave#

      its a shame and seems to be almost there as github.com/Microsoft/WSL/issues/2941 gives a simple why it should work with this hack that didnt really work in this OMV 4 case...

      Post by bugnotme ().

      This post was deleted by the author themselves ().
    • oh, arr , for a minute i thought YES it's alive, sadly not yet and im at a bit of a lost now....
      "apt-get --yes --auto-remove --show-upgraded --allow-downgrades --allow-change-held-packages --no-install-recommends --option Dpkg::Options::="--force-confdef" --option DPkg::Options::="--force-confold" --allow-unauthenticated install openmediavault"

      the adventure was to use a generic clean WSL debian 9 install on a clean new windows 10 pro ssd install and for a moment it seems to almost work...

      interestingly its seems a generic clean WSL debian 9 install shows a few OMV bugs and basic unhandled errors that kill the scripts rather than recover gracefully as in for instance
      omv-firstaid
      options
      1:

      ERROR: dialog-like terminated due to an error: the dialog-like program exited with status 3 (which was passed to it as the DIALOG_ERROR environment variable). Sometimes, the reason is simply that dialog was given a height or width parameter that is too big for the terminal in use. Its output, with leading and trailing whitespace stripped, was:

      Error: Expected at least 5 tokens for --menu, have 4.
      Use --help to list options.

      2:

      Updating web control panel settings. Please wait ...
      ERROR: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; systemctl reload 'monit' 2>&1' with exit code '1': Failed to reload monit.service: Launch helper exited with unknown return code 1
      See system logs and 'systemctl status monit.service' for details.

      and will some community dev please fix the typo in a current and many prior releases to fix that annoying File "/usr/lib/python3.5/weakref.py", line 117

      Hit:10 packages.openmediavault.org/public arrakis-proposed InRelease
      Hit:11 apt.sonarr.tv master InRelease
      Hit:12 download.virtualbox.org/virtualbox/debian stretch InRelease
      Hit:13 deb.debian.org/debian stretch Release
      Hit:16 deb.nodesource.com/node_10.x stretch InRelease
      Hit:14 vorboss.dl.sourceforge.net/project/openmediavault/packages arrakis InRelease
      Hit:15 datapacket.dl.sourceforge.net/…t/openmediavault/packages arrakis-proposed InRelease
      Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fdced3a88c8>
      Traceback (most recent call last):
      File "/usr/lib/python3.5/weakref.py", line 117, in remove
      TypeError: 'NoneType' object is not callable
      Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7fdced3a88c8>
      Traceback (most recent call last):
      File "/usr/lib/python3.5/weakref.py", line 117, in remove
      TypeError: 'NoneType' object is not callable
    • WSL is not a full Debian install. OMV relies on a "real" Linux install where the kernel isn't being lied to. The weakref.py issue is well documented in the forum.
      omv 4.1.8.2 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.9
      omv-extras.org plugins source code and issue tracker - github.com/OpenMediaVault-Plugin-Developers

      Please read this before posting a question.
      Please don't PM for support... Too many PMs!
    • Yeah pretty much anything network-related does not work through WSL. I learned this the hard way when trying to use UPnPC with my router. Your best bet is to either run Debian directly on your hardware or create a VM with it and configure the virtual network adapter to have its own IP address on the network. I forget what this setting is called, but you can find it quite easily online.