WARNING: openmediavault 4.1.8-1 breaks system!

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

    Code
    apt update
    apt upgrade
    Y to all


    Rebooted - monit not start.
    Manually started monit:

    Code
    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


    Code
    2018-06-10T14:10:01+0200 omv-virt systemd[1]: multi-user.target: Found ordering cycle on multi-user.target/start
    2018-06-10T14:10:01+0200 omv-virt systemd[1]: multi-user.target: Found dependency on monit.service/start
    2018-06-10T14:10:01+0200 omv-virt systemd[1]: multi-user.target: Found dependency on multi-user.target/start
    2018-06-10T14:10:01+0200 omv-virt systemd[1]: multi-user.target: Breaking ordering cycle by deleting job monit.service/start
    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
  • 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 6.0.5-2 Shaitan | 64 bit | 5.13 proxmox kernel | omvextrasorg 6.0.4 | kvm plugin 6.0
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

    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.


  • 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.

  • How do we apply the fix before the update/patch is released? Is it just removing the two lines in /etc/systemd/system/monit.service.d/openmediavault.conf ? If so would commenting them out be sufficient?

  • Remove the file then systemctl daemon-reload

    omv 6.0.5-2 Shaitan | 64 bit | 5.13 proxmox kernel | omvextrasorg 6.0.4 | kvm plugin 6.0
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • 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 ...

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!