Hi all, I have a problem all of a sudden with monit and would appreciate some advice. I am using an old version of OMV (1.19)
I had a power outage recently and the UPS scheduled shutdown sequence was erratic. The logs don't make much sense and I suspect it was related to monit issues.
On rebooting, the logs say collectd was refused a connection to the NUT plugin and OMV is unable to connect to monit. Even if I SSH in and try to manually access the monit daemon via CLI, I get the same "not authorized" error as the PHP script does when I try to change something through the web UI.
At some point a few weeks ago, I did try to manually make a change to /etc/monit/monitrc to get the separate monit web interface working, but OMV overwrote the file so I gave up trying to mess with it.
I can access the daemon via CLI for some reason if I uncomment the line "set admin:monit" under the httpd settings in the monit config file but then that change is automatically reverted immediately so it's not much of a solution.
What can I do to fix whatever is wrong here? I'm not understanding *why* monit is refusing connections from root, and, since OMV seems to be controlling the config file, I don't understand why OMV is also not able to access monit. Is there perhaps some sort of OMV command I can use to reset monit to the last functional state? I tried searching the web for an answer but monit troubleshooting resources seem to be very slim in availability.