I updated to OMV 4.1.8 and nothing broke here.
Nothing broken for me either.
No problems here.
I also see no issue right now. But did any of you reboot after the update and can confirm monit is running?
Checked in a VM. After a restart monit is not running.
This is in the boot logfile
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/startAs temporary solution, you can start monit from CLI
systemctl start monit
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
I've double checked that on my production hardware and creating a new Vagrant box. On both systems i do not see any problems.
root@omv4box:/home/vagrant# systemctl status monit
● monit.service - LSB: service and resource monitoring daemon
Loaded: loaded (/etc/init.d/monit; generated; vendor preset: enabled)
Drop-In: /etc/systemd/system/monit.service.d
└─openmediavault.conf
Active: active (running) since Mon 2018-06-11 06:36:05 UTC; 1min 40s ago
Docs: man:systemd-sysv-generator(8)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/monit.service
└─30738 /usr/bin/monit -c /etc/monit/monitrc
Jun 11 06:36:05 omv4box systemd[1]: Stopped LSB: service and resource monitoring
Jun 11 06:36:05 omv4box systemd[1]: Starting LSB: service and resource monitorin
Jun 11 06:36:05 omv4box monit[30735]: Starting Monit 5.20.0 daemon with http int
Jun 11 06:36:05 omv4box monit[30735]: Monit start delay set to 5s
Jun 11 06:36:05 omv4box monit[30731]: Starting daemon monitor: monit.
Jun 11 06:36:05 omv4box systemd[1]: Started LSB: service and resource monitoring
Jun 11 06:36:10 omv4box monit[30738]: 'omv4box' Monit 5.20.0 startedI'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 https://github.com/openmediava…3a595fe9a802b550d1fe8e3e8.
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
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 ...
It is just a warning. Are you facing any problems?
Is it advisable to update knowing that monit fails?
Is it advisable to update knowing that monit fails?
Another update has been released that fixes the problem. Or at least it supposedly does. I haven't rebooted to test it.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
