monit errors

    • Resolved
    • OMV 1.0
    • monit errors

      Can anyone help?
      I was getting lots of monit messages in syslog for my disks exceeding usage limit-

      monit[3404]: 'fs_media_48b3563b-9ef9-47a3-953d-df8c90510038' space usage 82.6% matches resource limit [space usage>80.0%]

      So I (stupidly) tried to fix it by modifying /etc/monit/conf.d/openmediavault-filesystem.conf
      and changing 80% to 90% in the following line for all my disks

      "
      # Alert if filesystem is missing or disk space gets low
      check filesystem fs_media_48b3563b-9ef9-47a3-953d-df8c90510038 with path /media$
      if space usage > 80% for 5 times within 15 cycles
      then alert else if succeeded for 10 cycles then alert
      "
      I now get errors on reboot saying -

      /etc/monit/conf.d/openmediavault-filesystem.conf.bak:7: Error: service name conflict, fs_media_48b3563b-9ef9-47a3-953d-df8c90510038 already defined '/media/99cfeb1a-024b-46e8-b1bc-b6d64a91bdd7'

      I tried putting back the original openmediavault-filesystem.conf but the errors still occur

      What did I do wrong?
    • To fix your error: mkconf monit should fix it.

      To change the threshold for notification you have to add a line to /etc/default/openmediavault : OMV_MONIT_SERVICE_FILESYSTEM_SPACEUSAGE=80 Replace it with the value you want.

      See here for more Info on the environment variables:

      wiki.openmediavault.org/index.…tle=Environment_Variables

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • rm /etc/monit/conf.d/openmediavault-filesystem.conf.bak
      service monit restart
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • In 1.0... I got this to work by doing:
      • Add

        Source Code

        1. OMV_MONIT_SERVICE_FILESYSTEM_SPACEUSAGE=90
        to

        Source Code

        1. /etc/default/openmediavault
        . It wasn't already in there, so I added it to the end.
      • run

        Source Code

        1. sudo

        Source Code

        1. omv-mkconf monit

      • run

        Source Code

        1. sudo service monit restart

      • double check that the 80%'s turned to 90%'s here:

        Source Code

        1. /etc/monit/conf.d/openmediavault-filesystem.conf
        (don't change stuff here, it will get overritten.

      It would be good to have documentation on the other environment variables we can modify that aren't in

      Source Code

      1. /etc/default/openmediavault
      .
    • grep -r "\=\${" /usr/share/openmediavault/mkconf/* will show you the majority of them - some of these may be very dangerous to change!
      omv 4.1.14 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • that0n3guy wrote:

      It would be good to have documentation on the other environment variables we can modify that aren't in
      Source Code

      /etc/default/openmediavault

      .


      wiki.openmediavault.org/index.…tle=Environment_Variables

      wiki.openmediavault.org/index.…Environment_Variables/all

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • Actually I added that on September 14th to the wiki.

      Greetings
      David
      "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"

      Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.


      Upload Logfile via WebGUI/CLI
      #openmediavault on freenode IRC | German & English | GMT+1
      Absolutely no Support via PM!

      I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
    • i modified monit"OMV_MONIT_SERVICE_FILESYSTEM_SPACEUSAGE" to 90 and get errors
      when i try to restart monit.
      Also webgui gets error

      WEBGUI

      Source Code

      1. Failed to execute command 'export LANG=C; monit summary 2>&1': /etc/monit/conf.d/openmediavault-filesystem.conf:2: Error: service name conflict, rootfs already defined '/' /etc/monit/conf.d/openmediavault-filesystem.conf:6: Error: service name conflict, fs_media_5a24e136-09b9-48e1-95db-b44d5db3e28a already defined '"/media/5a24e136-09b9-48e1-95db-b44d5db3e28a"'


      SSH

      Source Code

      1. root@NAS:/etc/monit/conf.d# sudo service monit restart
      2. Stopping daemon monitor: monit.
      3. Starting daemon monitor: monit/etc/monit/conf.d/openmediavault-filesystem.conf:2: Error: service name conflict, rootfs already defined '/'
      4. /etc/monit/conf.d/openmediavault-filesystem.conf:6: Error: service name conflict, fs_media_5a24e136-09b9-48e1-95db-b44d5db3e28a already defined '"/media/5a24e136-09b9-48e1-95db-b44d5db3e28a"'
      5. failed!