I'm in the process of migrating from unRAID to OMV + snapRAID + mhddfs and am trying to work out some minor problems. Anyone care to help?
1) The first one is more of a validity check. I've been getting the following alerts every time when resuming from sleep (using the autoshutdown plugin). They occur almost instantly after resuming and the moniterd state returns to normal after 30 seconds. This behaviour is also talked about in this thread.
ZitatResource limit matched Service localhost
Date: Tue, 28 Apr 2015 15:27:30
Action: alert
Host: skeelo.lan
Description: cpu wait usage of 100.0% matches resource limit [cpu wait usage>95.0%]
ZitatResource limit succeeded Service localhost
Date: Tue, 28 Apr 2015 15:28:01
Action: alert
Host: skeelo.lan
Description: 'localhost' cpu wait usage check succeeded [current cpu wait usage=9.4%]
Even though in the aforementioned thread they talk about cpu load, I believe this is a measure of the cpu waiting on I/O, more specifically in this case waiting for the disks to be spun up and ready. The suggested solution (i.e. adding OMV_MONIT_SERVICE_SYSTEM_CPUUSAGE_WAIT=99 to /etc/default/openmediavault and reconfiguring monit) does not work either since setting OMV_MONIT_SERVICE_SYSTEM_CPUUSAGE_WAIT=99 will still trigger the cpu wait usage, as per the following (note the adjusted value of 99%).
ZitatResource limit matched Service localhost
Date: Tue, 28 Apr 2015 20:36:29
Action: alert
Host: skeelo.lan
Description: cpu wait usage of 100.0% matches resource limit [cpu wait usage>99.0%]
Therefore I came up with the following:
I noticed monit was called with a delay of 30 seconds upon boot, so I figured there must be a way to retrigger the delay on resume. Thus I created a script in /etc/pm/sleep.d named i.e. 99custom-monit (starting with "9" makes it run early after resume) which contains the following code:
#!/bin/sh
# reload monit to avoid cpu wait usage alert
case "$1" in
hibernate|suspend)
monit unmonitor localhost
;;
thaw|resume)
sleep 32
monit monitor localhost
;;
*) exit $NA
;;
esac
Alles anzeigen
It simply stops all monitoring on sleep and restarts all monitoring 32 seconds after resume. My testing confirms I get no more alert messages. I only hope I'm not creating some other problem down the line, that's why I wanted to ask someone more knowledgeable about the validity of this workaround.
2) Monit, kind as she is, also alerts me of the space usage above 80% of every file system. Problem is, I don't need this info from every filesystem. I know some of them are full and am fine with it. Is there a way to disable the monitoring of a few specific file systems while keeping others still monitored? I already tried editing /etc/monit/conf.d/openmediavault-filesystem.conf, commenting out the lines I did not need, running omv-mkconf monit and restarting monit but my changes don't seem persistent.
3) I don't know if this has been suggested before but when removing shared folders through the webGUI, it asks to delete the content of the folders recursively. I really think this is rather dangerous because a single moment of carelessness can cause a lot of problems. I think it would be better to handle this with a separate button or with a checkbox (default unchecked) to create the same behaviour. This requires a well-thought-out action on behalf of the user, instead of mindlessly clicking a button underneath a bunch of words in an alert box which most people tend to ignore most of the time.