[SOLVED] Update to Monit 1.5 has issues

Started by dcol, March 05, 2018, 06:17:46 PM

Previous topic - Next topic
March 05, 2018, 06:17:46 PM Last Edit: March 07, 2018, 03:39:42 PM by dcol
After Update to 18.1.3 I was continuing testing of Monit and realized that it now has issues. No longer sends notifications and has Control errors. Tried a package reinstall and I think that made it worse. Also reboot.

I did log an issue report on Github already.
This is happening on three systems I updated this morning.

How can I revert back to Monit 1.4 to test if the update is the cause?

Reverted back to Monit 1.4 and the issues are gone. Be advised, Monit 1.5 has issues.

If you are relying on Monit, I suggest you revert to 1.4 until the bugs are fixed.
If you were on 18.1.2 then use the following in the shell
# opnsense-revert -r 18.1.2 os-monit

On one of my OPNsense boxes. Monit no longer runs at all after the 1.8.3 update, The other 2 boxes are working now that I downgraded Monit to version 1.4.
But on that one box, the monit service will not start and I get the following error in the system log
monit: /usr/local/etc/monitrc:17: syntax error 'failed'
I looked at this file and it appears identical to the running systems

I tried downgrading Monit to version 1.4 and then reinstalled Monit with plenty of reboots and I can not make this error go away.

Any suggestions outside a total reinstall?

Works fine here.. even after the upgrade. It has new features as well, which I highly appreciate (as a side note) and also work fine. Is it because of some custom stuff you configured?
OPNsense v18 | HW: Gigabyte Z370N-WIFI, i3-8100, 8GB RAM, 60GB SSD, | Controllers: 82575GB-quad, 82574, I221, I219-V | PPPoE: RDS Romania | Down: 980Mbit/s | Up: 500Mbit/s

Team Rebellion Member

Yes there was an error in one of my conditions that didn't have an issue with 1.4
Once I removed the syntax error, Monit 1.5 started working.

There really does need to be some changes with Monit 1.5. Most are simple.

The new 'Import From Notifications' feature should not import the secure connection because notifications and Monit use different methods. Or there needs to be a pop up that states that STARTTLS is not supported in Monit if the feature sees that field selected. Dev stated that any server that uses STARTTLS should also use SSL, which is totally incorrect.

Also, the Apply button no longer restarts the service. You now need to reload the configuration in order to complete any changes. This should be explained somewhere.

Also, we need better documentation for Monit. There are too many features that have no explanation whatsoever. The reason I had issues is I had to guess on the syntax. Wasn't until I complained and the dev responded did I realize what I did.

Agreed. There are some refinements that need to be made, you mentioned many of them. Overall, I'm happy it works :)
OPNsense v18 | HW: Gigabyte Z370N-WIFI, i3-8100, 8GB RAM, 60GB SSD, | Controllers: 82575GB-quad, 82574, I221, I219-V | PPPoE: RDS Romania | Down: 980Mbit/s | Up: 500Mbit/s

Team Rebellion Member