monit errors

ggr · Sep 22nd 2014

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?

davidh2k · Sep 22nd 2014

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:

http://wiki.openmediavault.org…tle=Environment_Variables

Greetings
David

ggr · Sep 22nd 2014

getting
-bash: mkconf: command not found

Do I need to install something?

Solo0815 · Sep 22nd 2014

try omv-mkconf monit

ggr · Sep 22nd 2014

Quote from Solo0815

try omv-mkconf monit

OK. That command appeared to work, but still seeing the errors on restart.
Luckily I have a clonezilla backup from last night, so I'll restore that and try changing the variables as suggested by davidh2k.

ryecoaaron · Sep 22nd 2014

rm /etc/monit/conf.d/openmediavault-filesystem.conf.bak
service monit restart

ggr · Sep 22nd 2014

Quote from ryecoaaron

rm /etc/monit/conf.d/openmediavault-filesystem.conf.bak
service monit restart

That did it.
Thanks again to all.

Once again I'm struck by how helpful folks are on this forum. Makes using OMV a pleasure, even for Linux beginner like myself.
I'll need to stop tinkering though....

that0n3guy · Jan 14th 2015

In 1.0... I got this to work by doing:

Add

Code

OMV_MONIT_SERVICE_FILESYSTEM_SPACEUSAGE=90

to

Code

/etc/default/openmediavault

. It wasn't already in there, so I added it to the end.

run
Code
```
sudo
```
Code
```
omv-mkconf monit
```
run
Code
```
sudo service monit restart
```
double check that the 80%'s turned to 90%'s here:
Code
```
/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

Code

/etc/default/openmediavault

.

ryecoaaron · Jan 14th 2015

grep -r "\=\${" /usr/share/openmediavault/mkconf/* will show you the majority of them - some of these may be very dangerous to change!

davidh2k · Jan 14th 2015

Quote from that0n3guy

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

/etc/default/openmediavault

.

http://wiki.openmediavault.org…tle=Environment_Variables

http://wiki.openmediavault.org…Environment_Variables/all

Greetings
David

ryecoaaron · Jan 14th 2015

Did you just add that to the wiki?

davidh2k · Jan 14th 2015

Actually I added that on September 14th to the wiki.

Greetings
David

that0n3guy · Jan 15th 2015

Ahh, I skimmed over that wiki page 3 times and never saw the all variables link.

Maybe make it under its own heading so its easy to see :).

Gutz-Pilz · Jul 22nd 2015

i modified monit"OMV_MONIT_SERVICE_FILESYSTEM_SPACEUSAGE" to 90 and get errors
when i try to restart monit.
Also webgui gets error

WEBGUI

Code

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

Code

root@NAS:/etc/monit/conf.d# sudo service monit restart
Stopping daemon monitor: monit.
Starting daemon monitor: monit/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"'
 failed!

Gutz-Pilz · Jul 22nd 2015

solved it

Code

rm /etc/monit/conf.d/openmediavault-filesystem.conf.*
rm /etc/monit/conf.d/openmediavault-filesystem.conf_*
service monit restart

Participate now!