Hi everyone,
M/Monit 2.2.1 has just been released. This is a bug fix release that can be download from: http://mmonit.com/download/
Release information: ====================
Improvements
* Changed name of admin menu item "Rules" to "Alerts" to make it clearer that this page is used for setting up alert rules.
* Accept messages from future Monit versions (no need to upgrade M/Monit when Monit is extended).
Bug fixes
* Fix JSON error in rules admin page, when empty hostgroup was defined. Thanks to Balazs Boros for report.
* Fixed a problem in service cache that could drain the database connection pool of available database connections.
Upgrading from M/Monit 2.2: ===========================
There are no database changes in this release. Please run the following commands if you want to copy your configuration, database and logs to the new installation:
cp -a mmonit-2.2/conf/. mmonit-2.2.1/conf/ cp -a mmonit-2.2/logs/. mmonit-2.2.1/logs/ cp -dp mmonit-2.2/db/mmonit.db mmonit-2.2.1/db/
On (some) FreeBSD and Mac OS X systems use instead:
cp -Rpv mmonit-2.2/conf/. mmonit-2.2.1/conf/ cp -Rpv mmonit-2.2/logs/. mmonit-2.2.1/logs/ cp -pv mmonit-2.2/db/mmonit.db mmonit-2.2.1/db/
Known issues: =============
Mac OS X 10.6.x (Snow Leopard): There is a bug in the system library, libpthread, which, if M/Monit is run in daemon mode will result in that one CPU core will max out and M/Monit becomes unresponsive. The workaround is to only run M/Monit in the foreground using the -i switch to the mmonit program.
Contact: ========
If you have questions, comments or any other feedback about this release, please contact us at mmonit@tildeslash.com
Best regards, the Monit team
mmonit-announce@tildeslash.com