Beiträge von JamesDK

    ok.. found it. with
    monit summary
    i can as well see the drives

    monit status
    does it more detailed, but thats not necessary.


    what works is now:
    still place
    OMV_MONIT_SERVICE_FILESYSTEM_SPACEUSAGE=95
    in /etc/default/openmediavault
    and


    For OMV 4.x and higher:
    omv-mkconf monit
    monit reload


    thank you for the support, gderf. sometimes i need a little push. I appreciate that.

    me too. i'm using version 4.1.19
    08/2018 : fresh 4.x omv install on debian to get system patition work on nvram, so no upgrade from older omv


    i just tried the fix for 3.0 cause didnt found any newer.



    after checking all references in /etc/default/openmediavault
    found this in /usr/share/openmediavault/mkconf/monit.d/filesystem


    which is probably to make this config file: /etc/monit/conf.d/openmediavault-filesystem.conf
    but if i look in that.. its still the old one with 85 entries for any drive, and the date is that from installation 08/2018



    how do i proceed, to update this conf file? i will look for that..
    --
    i'm still a rookie, so i m sorry, if any of this is too obvious for a linux pro

    thank you, i will try.
    this is the whole content of the file openmediavault. did not find any error, so just retyped the last line, in case there was an error..

    executed
    omv-mkconf collectd
    and
    monit restart collectd"



    log:


    still the same.


    btw now i see.. 1008 is the process id :whistling: didnt knew that before


    is there now way to check the value, like a global var ..or something like that.

    hi, maybe someone can help.


    i have every 30sec these two entries in syslog:

    Code
    monit[1001]: 'filesystem_srv_dev-disk-by-label-parity1' space usage 86.4% matches resource limit [space usage>85.0%] 
    monit[1001]: 'filesystem_srv_dev-disk-by-label-data1' space usage 85.9% matches resource limit [space usage>85.0


    trying to modify monit i found here some help


    i did this for omv 3.0 and checked in syslog that monit did a restart,
    but still getting the same entries in log.
    only this time it changed to monit[1008].


    would be great if someone can help
    thnx