Monit 5.0.3 is available:
Download from: http://www.mmonit.com/monit/dist/
MD5 checksum:
dae7859ec10551fc941daeae60dee9d3
SHA256 checksum:
5dd2539b3c61d109fa75efaa599168eb91bd59f20eba889e4c8b1990cac587d3
Change log: http://www.mmonit.com/monit/dist/CHANGES.txt
BUGFIXES:
* Fixed #26664: crash on service timeout or unmonitor action
(introduced in 5.0.2). Thanks to Bretislav Kubesa and
Michael Shigorin for report.
* Removed the configure --without-resource option. If the user
who is running Monit doesn't have permissions to check the
processes state, the related checks are disabled dynamically.
Hello everyone!
We have just released M/Monit 2.0.3. You can download the new release
from:
http://mmonit.com/download/
Release information:
--------------------
This is a bug fix release which fixes the NumberFormatException I sent
a mail about earlier this week [1]. In addition, it contains a few
other minor fixes. Upgrade is recommended!
The changes in this release are:
* Fixed a potential NumberFormatException error when clicking on
a host row in the host status page. Many thanks to Aleksander
Kamenik for finding this bug and helping us resolve it.
* The grey delete icon in admin tables is changed to a red icon
on mouse hover to give better UI feedback. Thanks to Aleksander
Kamenik for suggestion.
* Ignore invalid cookies. Previous versions aborted the request
with a 404 error. Thanks to Ron McKown for debug help.
* In the admin page only display real active login sessions.
* Expanded host table columns platformname, platformrelease,
platformversion, platformmachine to allow for up to 255
characters. FreeBSD 7.x uses very long names and this could
prevent M/Monit from accepting status reports from servers
running this OS.
If you are upgrading from M/Monit 2.0.2, perform the following to
upgrade the database:
If you use SQLite:
./upgrade/upgrade-2.0.2-2.0.3.sqlite
If you use MySQL:
cat ./upgrade/upgrade-2.0.2-2.0.3.mysql | \
mysql -u mmonit -p -D mmonit
If you use Postgresql:
cat ./upgrade/upgrade-2.0.2-2.0.3.postgresql | \
psql -U mmonit mmonit
Future plans:
=============
We expect this 2.0.3. release to be a stable version and the next 2.1
release is scheduled for July. The 2.1 release will primarily focus on
scalability and make M/Monit able to handle many more Monit hosts. The
goal is 1000. We'll also add Jabber alerts to this version and include
host groups in alert rules for easier management of host rules.
Contact:
========
If you have questions or comments about this release, please contact
us at mmonit(a)tildeslash.com
Have a nice weekend! Best regards from the M/Monit team.
[1] http://www.tildeslash.com/pipermail/mmonit-announce/2009-May/000004.html
We have found a potential problem in M/Monit version 2.0.2 when
clicking on a host row in the host status page (http://localhost:8080/status/
). If you see an error page with this error instead of the host detail
page:
NumberFormatException: For input string null
Then, here is a simple workaround until we have a new release
available later this week. Run this SQL statement in the mmonit
database:
update host set port_out = -1 where port_out is NULL or port_out = "";
This bug manifest if you edit and save changes to a host in admin/
host. The field "Outbound Port for Monit" is normally empty and unless
a value was given it will be saved with a null value which we did not
properly test for in the status page above. Many thanks to Aleksander
Kamenik for finding this bug and helping us resolve it.
If you have seen any other problems in M/Monit version 2.0.2 please
let us know at mmonit(a)tildeslash.com so we can fix them ASAP and
include them in the 2.0.3 release.
Best regards
--
Jan-Henrik Haukeland
http://tildeslash.com/
Hi everyone,
We have just released M/Monit 2.0.2. You can download the new release
from:
http://mmonit.com/download/
Release information:
--------------------
The changes in this release are mostly bug and stability fixes. We
have also snuck in a few new features as well. Excerpt from the change
log follows.
* If you are upgrading from M/Monit 2.0 perform the
following to upgrade the database:
If you use SQLite:
./upgrade/upgrade-2.0-2.0.2.sqlite
If you use MySQL:
cat ./upgrade/upgrade-2.0-2.0.2.mysql | \
mysql -u mmonit -p -D mmonit
If you use Postgresql:
cat ./upgrade/upgrade-2.0-2.0.2.postgresql | \
psql -U mmonit mmonit
NEW FEATURES:
* You can now change the name and description of host groups.
* Quick delete added to admin page tables for hosts, users and
rules. These tables have a new delete icon in the rightmost
column and clicking on the icon deletes the table entry. This
is a shortcut so you don't have to open the entry first to
delete it. Thanks to Nicola Tiling for suggestion.
* Added Monit version information to admin/hosts table. This
allows you to quickly see which Monit version is running on
each host. Thanks to Aleksander Kamenik for suggestion.
* Increased skew rate for Monit agents from 2 to 3 cycles.
* OpenBSD support added.
* Updated all shared libraries to latest version.
BUG FIXES:
* Stability fixes.
* Internal performance improvements in the connection pool driver
for SQLite. The new changes makes SQLite scale much better and
able to handle many more hosts.
* Expanded host.platformrelease column in the database to allow
for up to 100 characters. Some OS use a long release name which
did not fit in the original 20 characters limit used in the
database. M/Monit could refuse message from these hosts and not
update the host status. Thanks to Aaron Scamehorn for report.
* Increased read timeout from 3 seconds to 30 seconds when
communicating with SMTP servers to allow for slow servers.
* Fixed possible "Number format exception" error when trying to
open host status or use host admin for monit hosts which were
imported from older M/Monit versions. Thanks to Nicola Tiling
for report.
* Fix possible OpenSolaris crash. Thanks to Christoffer Torris
Olsen for report.
Future plans:
=============
While this release focus on stability, the next release will focus on
scalability.
Before we start on all the cool new features we plan for M/Monit we
want to ensure that M/Monit can easily be used with more than Monit
150-200 hosts.
We also want to reduce the stress M/Monit can cause on the database
server. If you monitor more than 10 hosts and run Monit on a low poll
cycle it can increase the CPU load on the database server because each
status report from Monit ends up in a database request.
We plan to fix this by introducing an in-memory cache for host status
which will make M/Monit scale much better and drastically reduce the
need for database access. We are working on the 2.0.3 release now and
we hope to have it available for you within a month.
Contact:
========
If you have questions or comments about this release, please contact
us at mmonit(a)tildeslash.com
With the best regards from the M/Monit team
The monit 5.0.2 is available:
Download from: http://www.mmonit.com/monit/dist/
MD5 checksum:
416db6d616ee3a44d274522103fef9af
SHA256 checksum:
dc5b7a483383bf54e3f8a1dc29089d50e13f15e5f7512bc705a92e52cc41092f
Change log: http://www.mmonit.com/monit/dist/CHANGES.txt
BUGFIXES:
* 35 improvements based on code scan with Klockwork
(http://www.klocwork.com/) which we were evaluating.
Huge thanks to Klocwork for their great product.
* Fixed #26382: if start or stop script for some service didn't
exist, monit logged error during configuration file parsing and
refused to start. Monit now just logs warning and continues.