WARNING: openmediavault 4.1.8-1 breaks system!

    • OMV 4.x
    • Upgrade 3.x -> 4.x

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

    • WARNING: openmediavault 4.1.8-1 breaks system!

      Installed 4.1.3-1 from CD. Initial reboot fine.
      Logged in:

      Source Code

      1. apt update
      2. apt upgrade
      3. Y to all

      Rebooted - monit not start.
      Manually started monit:

      Source Code

      1. systemctl start monit

      Made a load of changes via web gui, including LUKS encrypted volume.
      After a reboot, LUKS failed to unlock volume, monit failed to start.
      OMV well broken, reinstalled everything except openmediavault 4.1.8-1, so far OK.
    • This problem was reproducible. Reinstalled 5 times to test.
      All goes wrong after openmediavault 4.1.8 update.

      The box had been running 3.x, upgraded to 4 all the way to 4.1.7 (or maybe 4.1.8), and rebooted OK.
      However, didn't have console plugged in and didn't attempt any changes through Web GUI, so didn't notice if monit was still running.
      Yesterday was a fresh install to get LUKS encryption on for good old GDPR.

      Getting a few other strange issues attempting to setup UPS - says name characters not in a-z, 0-9. They are!
      Maybe boot SSD is on it's way out?
      Will have to check next weekend, spent 10 hours at customer site yesterday. Heading off out in the sunshine today...
    • @votdev

      Checked in a VM. After a restart monit is not running.

      This is in the boot logfile

      Source Code

      1. 2018-06-10T14:10:01+0200 omv-virt systemd[1]: multi-user.target: Found ordering cycle on multi-user.target/start
      2. 2018-06-10T14:10:01+0200 omv-virt systemd[1]: multi-user.target: Found dependency on monit.service/start
      3. 2018-06-10T14:10:01+0200 omv-virt systemd[1]: multi-user.target: Found dependency on multi-user.target/start
      4. 2018-06-10T14:10:01+0200 omv-virt systemd[1]: multi-user.target: Breaking ordering cycle by deleting job monit.service/start
      5. 2018-06-10T14:10:01+0200 omv-virt systemd[1]: monit.service: Job monit.service/start deleted to break ordering cycle starting with multi-user.target/start
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • I haven't checked my systems but sounds like systemctl enable monit would fix the problem.

      ** edit - that doesn't work. very strange.

      ** edit 2 - removing the systemd override added in 4.1.8 fixes the problem. Not sure if the fact that monit doesn't use a systemd unit file is causing the problem @votdev
      omv 4.1.13 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!

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

    • I've double checked that on my production hardware and creating a new Vagrant box. On both systems i do not see any problems.

      Shell-Script

      1. root@omv4box:/home/vagrant# systemctl status monit
      2. ● monit.service - LSB: service and resource monitoring daemon
      3. Loaded: loaded (/etc/init.d/monit; generated; vendor preset: enabled)
      4. Drop-In: /etc/systemd/system/monit.service.d
      5. └─openmediavault.conf
      6. Active: active (running) since Mon 2018-06-11 06:36:05 UTC; 1min 40s ago
      7. Docs: man:systemd-sysv-generator(8)
      8. Tasks: 2 (limit: 4915)
      9. CGroup: /system.slice/monit.service
      10. └─30738 /usr/bin/monit -c /etc/monit/monitrc
      11. Jun 11 06:36:05 omv4box systemd[1]: Stopped LSB: service and resource monitoring
      12. Jun 11 06:36:05 omv4box systemd[1]: Starting LSB: service and resource monitorin
      13. Jun 11 06:36:05 omv4box monit[30735]: Starting Monit 5.20.0 daemon with http int
      14. Jun 11 06:36:05 omv4box monit[30735]: Monit start delay set to 5s
      15. Jun 11 06:36:05 omv4box monit[30731]: Starting daemon monitor: monit.
      16. Jun 11 06:36:05 omv4box systemd[1]: Started LSB: service and resource monitoring
      17. Jun 11 06:36:10 omv4box monit[30738]: 'omv4box' Monit 5.20.0 started
      Display All
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • I'm facing the same issue, monit not starting after reboot hence any configuration change errors out until I start monit manually which works fine. Fresh install of OMV 4 on HP Microserver Gen8, fully updated (OMV 4.1.8-1 kernel 4.16.0-0.bpo.1), monit service is enabled to start at boot.

      Let me know if you need any logs to figure out what's wrong.
    • Fixed in openmediavault 4.1.8.1, see github.com/openmediavault/open…3a595fe9a802b550d1fe8e3e8.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Just updated:

      Preparing to unpack .../openmediavault_4.1.8.1-1_all.deb ...
      Unpacking openmediavault (4.1.8.1-1) over (4.1.8-1) ...
      dpkg: warning: unable to delete old directory '/etc/systemd/system/monit.service.d': Directory not empty
      Setting up perl-modules-5.24 (5.24.1-3+deb9u4) ...
      Setting up libperl5.24:amd64 (5.24.1-3+deb9u4) ...
      Setting up perl (5.24.1-3+deb9u4) ...
      Processing triggers for libc-bin (2.24-11+deb9u3) ...
      Setting up openmediavault (4.1.8.1-1) ...
      Updating configuration database ...
      Updating configuration ...
      monit.service is not a native service, redirecting to systemd-sysv-install.
      Executing: /lib/systemd/systemd-sysv-install is-enabled monit
      Processing triggers for rsyslog (8.24.0-1) ...
      Processing triggers for openmediavault (4.1.8.1-1) ...
      Restarting engine daemon ...
      Updating locale files ...
      Updating file permissions ...
      Purging internal cache ...
      Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f5f96c898c8>
      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 0x7f5f96c898c8>
      Traceback (most recent call last):
      File "/usr/lib/python3.5/weakref.py", line 117, in remove
      TypeError: 'NoneType' object is not callable
      Done ...