Filesystem monitoring is a bit too aggressive

When I shut down my server, sometimes the monitoring service triggers reporting one of the file systems can't be read. This is expected, because the file system has been unmounted for shutdown, but this email should not be sent.

This leads to heartbreaking moments, because this email is only sent when the system is back on.

Monitoring restart -- Does not exist filesystem_srv_dev-disk-by-label-HDD1


The system monitoring needs your attention.


Date:        Sat, 12 Dec 2020 02:55:20
Service:     filesystem_srv_dev-disk-by-label-HDD1
Event:       Does not exist
Description: unable to read filesystem '/srv/dev-disk-by-label-HDD1' state


This triggered the monitoring system to: restart

I found a couple of environment variables but I don't know if they fit the case and how they should be configured:

OMV_MONIT_CHECK_INTERVAL

OMV_MONIT_DELAY_SECONDS

Thank you. I know how to apply environmental variables, but I was wondering how to address this case.

I checked my own docs and apparently I am already using OMV_MONIT_DELAY_SECONDS set to 20 seconds, because I was getting many errors during startup.