Hello all,
A thread storage problem was found in the just released 2.1 version
which could lead M/Monit to grow out of available virtual memory.
Upgrading to 2.1.1 is strongly recommended. We are sorry for the
inconvenience.
The new 2.1.1 release can be downloaded from http://mmonit.com/download/
Release information:
====================
IMPROVEMENTS:
* In admin/hosts, if an outbound IP-address was
specified for Monit, display this address in
the hosts table.
* Allow non-fully qualified domain for jabber users.
BUG FIXES:
* Fixed a thread storage problem that caused M/Monit
virtual memory usage to grow during event processing.
This in turn could lead M/Monit to grow out of available
virtual memory and to a full stop. Many thanks to Asim
for the bug report.
UPGRADING:
There are no database changes in this release
1) Using a proxy in front of M/Monit and having problems reaching
Monit from M/Monit?
-------------------------------------------------------------------------------------
In difference to the previous M/Monit 2.0.3 version, the host IP-
address is continuously updated to reflect real values. M/Monit takes
the IP-address of the connection from Monit and use that as the
address of the Host.
For example, if you have setup an Apache Proxy in front of M/Monit and
setup M/Monit to listen on the loop-back interface (127.0.0.1), M/
Monit will see the IP-address of Monit as 127.0.0.1.
Using a proxy in front of M/Monit is fine, but since the IP-address is
now updated each time Monit reports in, changing the Monit IP-address
in "Monit Host specification" will not stick.
Here is the solution to make M/Monit able to reach Monit again. Go to
admin/hosts and edit the Host in question. Click on the "Firewall/NAT/
Proxy" link and specify the outbound IP-address and port for Monit,
that would be the IP-address Monit is really running on. Click the
"Test connection to Monit" link to see if it works and that M/Monit
can now reach Monit. This screenshot indicate how it may look on your
system:
This solution will also fix any problems you might have had with the M/
Monit iPhone app not being able to connect.
Contact:
========
If you have questions, comments or any other feedback about this
release, please contact us at mmonit(a)tildeslash.com
Best regards from the M/Monit team.
Hello, everyone!
We have been busy improving M/Monit and today we have a new release
for you. This is a free upgrade for all M/Monit users.
The new release can be downloaded from http://mmonit.com/download/
Release information:
====================
NEW FEATURES:
* M/Monit will now send an alert if a Monit agent does not
report in on time.
* Various caching strategies have been added internally. This
should help M/Monit scale to hundreds of hosts and beyond.
* Replaced the Host drop down menu with a host search field in
the events page.
* Host groups can now be used, in addition to hosts, when
specifying an alert rule.
* Service groups can now be used, in addition to services, when
specifying an alert rule. A service group is defined in your
monitrc control file
* M/Monit can now send Jabber/GTalk alert messages in addition
to Mail messages.
* The M/Monit server now support SSL. Please consult the manual
to learn how to configure M/Monit to use SSL.
* The web user interface has got a modest face lift.
* Updated and improved manual
BUG FIXES:
* Evaluate all rules when processing events for sending alerts.
Previous versions only evaluated and acted on the first
matching rule. Thanks to Andrew Stott for report.
* Services and service groups are now pre-fetched from Monit
when Monit starts up and report to M/Monit. In earlier
versions of M/Monit, an event had to occur on a service before
the service was made available when specifying alert rules.
Note: this feature requires Monit-5.1, Monit-5.0.3 will also
work, but service names won't be synced.
* Added timezone in date header for mails sent by M/Monit.
Thanks to Thorsten Kampe for requesting this feature.
* Fixed a possible crash in Dashboard when an event from Monit
was received with a system time ahead of M/Monit's system
time. Thanks to Aleksander Kamenik for report.
* Improved the AJAX host search field to allow for a more
interactive search
* Improved message queue handling
* FreeBSD releases of M/Monit are now built using FreeBSD
version 6.0 and 7.0 instead of version 6.4 and 7.2. This
allows M/Monit to support a wider range of 6.x and 7.x FreeBSD
OS versions.
UPGRADING:
If you are upgrading from M/Monit 2.0.3 please perform the
following to upgrade the database:
If you use SQLite:
./upgrade/upgrade-2.0.3-2.1.sqlite
If you use MySQL:
cat ./upgrade/upgrade-2.0.3-2.1.mysql | \
mysql -u mmonit -p -D mmonit
If you use Postgresql:
cat ./upgrade/upgrade-2.0.3-2.1.postgresql | \
psql -U mmonit mmonit
Browser cache:
Please clear your Browser cache before login in to M/Monit 2.1.
Most pages have been changed in the web user interface and cached
pages from the previous version may create problems.
Contact:
========
We hope that you will enjoy this new release and find it useful.
If you have questions, comments or any other feedback about this
release, please contact us at mmonit(a)tildeslash.com
With the best regards from the M/Monit team.
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.
The monit 5.0.1 is available:
Download from: http://www.mmonit.com/monit/dist/
MD5 checksum:
4a33f7f0b8d40264fb50370e6544f974
SHA256 checksum:
e0f7e208b99cd4cfe2fdaea097d1b8ce6bdabdd4e6638876a3cd5f84d94a3b03
Change log: http://www.mmonit.com/monit/dist/CHANGES.txt
BUGFIXES:
* When PID, PPID, timestamp or size change test was defined
and the test failed and then succeeded again, monit started
to log success each monitoring cycle.
Hello everyone!
I'm happy to announce that M/Monit 2.0 has been released today and is
now available. M/Monit 2.0 can be downloaded from:
http://mmonit.com/download/
We are now officially out of the beta phase and this is the final 2.0
release.
Judging from previous beta releases, it seems that we have a 2 month
turnaround time for new releases. We'll try to continue with this
frequency, at least this first year as we have plans for many new and
useful features, both in M/Monit and Monit. We'll keep you posted.
A big, big thanks to all of you who have helped us test M/Monit during
the beta phase and for giving us useful suggestions, feedback and
ideas. This is highly appreciated!
Release information:
====================
The changes in this release compared to the previous beta 7 are minor
tweaks behind the scene and alignment of M/Monit events with Monit.
There are a few database changes, and if you want to upgrade from M/
Monit beta 7, you can run an upgrade script for the database as
explained in the change log: http://mmonit.com/dist/CHANGES
We also provide a migrate script in the upgrade directory if you want
to move over from SQLite to MySQL or PostgreSQL. This is recommended
if you run Monit on more than 10 hosts, as SQLite can have scalability
issues with more hosts.
Monit:
======
With more than 50 new features and bug fixes, we are also happy to
announce that Monit 5.0 is out of beta today and available from http://mmonit.com/monit/download/
M/Monit 2.0 requires this version of Monit.
We hope Monit 5.0 will be picked up by package distributors shortly,
so it will be available directly in distributions as well.
Contact:
========
If you have questions or comments about this release, please contact
us at mmonit(a)tildeslash.com
Documentation:
==============
Answers to frequently asked questions regarding M/Monit and Monit can
be found at http://mmonit.com/wiki/ And documentation for the M/Monit
program can be found at http://mmonit.com/documentation/
License and Purchase:
=====================
Monit will always be free and licensed under the GPL. For M/Monit we
need to take a small fee to allow us to continue working on Monit and
M/Monit. We hope you understand.
When you download M/Monit, it comes with a trial license which will
expire after 30 days. If you like M/Monit and find it useful, which we
believe you will, you can support our work further by purchasing a
license from:
http://mmonit.com/shop/
If you want to customize and modify M/Monit and build new binaries,
you can also purchase a Standard or Enterprise license which will give
you access to the M/Monit source code and SDK. The email with the
license key includes an URL from where you can download the source
code distribution of M/Monit. The Servlet Container M/Monit is built
on is not released in source form, but it is included as a shared
library for all supported platforms. The database library used by M/
Monit is available in the source distribution and also as an open
source GPL distribution here, http://www.tildeslash.com/libzdb/
Mailing list
============
We have converted this mailing list to a low traffic announce list. We
hope you will continue to subscribe to the list and follow us in our
on-going efforts to make M/Monit even better. As mentioned, we are
also directly available at mmonit(a)tildeslash.com.
With the very best regards from the M/Monit team