OMV5 Environment Variables

  • I have recently upgraded to omv 5, am on newest version 5.2.3-2.
    I run docker with the usual plex, sonarr, radarr, etc...
    I almost always have a couple transcodes going, and I contantly get the email notification for high load, the 1 minute and 5 minute variations, as well as the file system space warning


    loadavg (5min) of 11.8 matches resource limit [loadavg (5min) > 6.0]
    loadavg (1min) of 16.4 matches resource limit [loadavg (1min) > 12.0]
    space usage 91.6% matches resource limit [space usage > 85.0%]


    When I was on OMV4, I was able to add the following to /etc/default/openmediavault and omv-mkconf monit and reload and it worked.
    I have made the same additions in OMV 5, then run omv-salt deploy run monit, then monit reload, but it does not seem to work.
    I get the exact same messages with the exact same limits in the warnings.
    Has anyone been able to add any of the following to /etc/default/openmediavault and it worked? Am I missing a step?


    OMV_MONIT_SERVICE_FILESYSTEM_SPACEUSAGE=95
    OMV_MONIT_SERVICE_SYSTEM_CPUUSAGE_USER=75
    OMV_MONIT_SERVICE_SYSTEM_CPUUSAGE_SYSTEM=75
    OMV_MONIT_SERVICE_SYSTEM_CPUUSAGE_WAIT=75
    OMV_MONIT_SERVICE_SYSTEM_LOADAVG_1MIN_MULT=75
    OMV_MONIT_SERVICE_SYSTEM_LOADAVG_5MIN_MULT=50

    • Offizieller Beitrag

    Am I missing a step?

    Yep. Adding environment variables means you need to reload them for salt to know about the changes. The following command will do that: omv-salt stage run prepare After that, running omv-salt deploy run monit should work.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Thanks for posting this. Is there some place that lists all the OMV 5 environment variables?

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    • Offizieller Beitrag

    Is there some place that lists all the OMV 5 environment variables?

    Not that I know but I don't set many. And any list probably wouldn't include omv-extras environment variables. Here is the output of a quick grep on my dev system with a bunch of plugins installed but not all:


    grep -r 'default:OMV_' /srv/salt/omv/* | cut -d ":" -f3 | cut -d "'" -f1 | sort | uniq



    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Well, that's a start :) But where's the documentation that tells what the values for these are?


    As to my OMV 2.x box that became a 3, 4, and 5 - there has to be a ton of unused cruft in it. I would have a clue how to clean it all out. It's up to 11GB now.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    • Offizieller Beitrag

    But where's the documentation that tells what the values for these are?

    There isn't any that I know of. Here is a different grep with the default values:


    grep -r 'default:OMV_' /srv/salt/omv/* | cut -d ":" -f3 | cut -d')' -f1 | sort | uniq




    As to my OMV 2.x box that became a 3, 4, and 5 - there has to be a ton of unused cruft in it. I would have a clue how to clean it all out. It's up to 11GB now.

    I would start with du -d1 -h -x / | sort -h and keep changing the path and running it on the large directories until you find the cruft.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    Something strange with CPUFREQUTILS:


    grep -r 'default:OMV_CPU' /srv/salt/omv/* | cut -d ":" -f3 | cut -d')' -f1 | sort | uniq


    gives

    Code
    OMV_CPUFREQUTILS_MAXSPEED', '0'
    OMV_CPUFREQUTILS_MINSPEED', '0'

    /etc/default/openmediavault contains on my system





    Code
    OMV_CPUFREQUTILS_GOVERNOR="conservative"
    OMV_CPUFREQUTILS_MINSPEED="300000"
    OMV_CPUFREQUTILS_MAXSPEED="2000000"

    Seems the GOVERNOR variable is being ignored

    • Offizieller Beitrag

    Seems the GOVERNOR variable is being ignored

    Nope. Just not a perfect grep on my part.


    /srv/salt/omv/deploy/cpufrequtils/files/cpufrequtils.j2 has this line in it: GOVERNOR="{{ governor }}"

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag

    If you change /etc/default/openmediavault then you need to run


    # omv-salt stage run prepare
    # omv-salt deploy run cpufrequtils

    I did, but the governor is still "ondemand".


    If I change the governor manually to "conservative" and run the deploy command again, it stays at "conservative". That is why I thought the environmental variable is ignored.


Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!