Monit - resource limit threshold ignored in /etc/default/openmediavault

fmonaca · Sep 21st 2015

Hello,

I added OMV_MONIT_SERVICE_FILESYSTEM_SPACEUSAGE=95 in /etc/default/openmediavault and rebuilt the configuration and restarted the service (omv-mkconf collectd, monit restart collectd), but in the logs I keep having the same entries:

Sep 21 10:39:31 OMV monit[3562]: 'fs_media_905c93c6-ed7c-40c1-a916-444cabaf62e6' space usage 91.2% matches resource limit [space usage>80.0%]

so basically the new threshold is ignored.

I'm using Openmediavault 2.1.15, and the problem was present also in 2.1.14.

Any ideas?

Thanks!

gderf · Sep 21st 2015

Your format is not correct. Change the line to read (note the quotes around 95):

OMV_MONIT_SERVICE_FILESYSTEM_SPACEUSAGE="95"

fmonaca · Sep 27th 2015

Sorry, I mistyped it here, but I used the correct format in the configuration file, and it does not work.

subzero79 · Sep 27th 2015

You need to restart engined

/etc/init.d/openmediavault-engined restart

then

omv-mkconf monit

then /etc/init.d/monit restart

fmonaca · Sep 27th 2015

Thanks subzero79, that did it.

winemaster · Oct 2nd 2019

Quote from subzero79

You need to restart engined

/etc/init.d/openmediavault-engined restart

then

omv-mkconf monit

then /etc/init.d/monit restart

Display More

When I try to do this, I get

"-bash: /etc/init.d/openmediavault-engined: No such file or directory"

Am I doing something incorrectly?

Monit - resource limit threshold ignored in /etc/default/openmediavault

Participate now!

Tags