mmonit-announce

mmonit-announce@tildeslash.com

83 discussions

[Announce] M/Monit 2.3
by Jan-Henrik Haukeland 23 Sep '10

23 Sep '10

Hi, everyone! We have just released M/Monit 2.3. You can download the new release from: http://mmonit.com/download/ This new version of M/Monit sports a subtle improved user interface. New uptime reports for your hosts and services, which we hope you will like. The ability to execute a program as an alert action, in addition to email and jabber. Automatic registration of Monit credentials; when Monit registers now, it is really plug-and-play without the need to manually edit Monit hosts credentials in M/Monit. (Automatic registration of credentials can be turned off in your monitrc file, though we recommend using SSL instead with Monit and M/Monit if security is a concern). The M/Monit manual is updated to reflect the new changes; http://mmonit.com/monit/documentation/ This release requires the new Monit 5.2 version which we also released today. To simplify things we now also provide prebuilt binaries of Monit. So you can either build Monit from source or download a binary for your system. The binaries have OpenSSL 1.0.0a static linked and support SSL without OpenSSL having to be installed on your system. Download Monit 5.2 from http://mmonit.com/monit/download/ Release information: ==================== Improvements * New Report pages for hosts and services uptime and downtime. * Added execution of user defined programs/scripts as an alert option when receiving events from Monit * Improved user interface * Host details: * New charts: swap memory, CPU and memory * Service data displayed in a new pop-out panel * Sorted port response time chart * Optional automatic registration of Monit credentials * Internal cache improvements * TCP/IP and SSL improvements. Should improve communication over low-bandwidth and saturated networks. * Reduced memory usage. M/Monit never used a lot of memory before, but now it use even less. Bug fixes * Make M/Monit less strict when handling SMTP multi-line responses. Thanks to Barynin Konstantin for letting us know. * Fix crash during mmonit start on FreeBSD-8.x * Workaround libpthread bug in OS X which caused one CPU core to max out and M/Monit to become unresponsive if run in background mode. M/Monit now works fine in daemon mode on OS X. * Fixed infrequent connection close. In some situations M/Monit could drop connections in mid-communication if the client was "slow" to respond. * Fixed login problems for user account during which's create/edit some input data format check failed and the form was re-submitted after correction of the input. Upgrading from M/Monit 2.1.x or 2.2.x: ====================================== If you are upgrading from M/Monit 2.1.x or 2.2.x please perform the following to upgrade the database: ./upgrade/upgrade-2.1.x-2.3.sh -t [sqlite|mysql|postresql] or ./upgrade/upgrade-2.2.x-2.3.sh -t [sqlite|mysql|postresql] Browser Cache: Please clear your Browser cache before login to M/Monit 2.3. Some pages have been changed and cached pages from the previous version may create problems. Known issues: ============= None Contact: ======== If you have questions, comments or any other feedback about this release, please contact us at info(a)mmonit.com Best regards from the M/Monit team

1 0

[Announce] M/Monit 2.2.1
by Jan-Henrik Haukeland 16 Mar '10

16 Mar '10

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(a)tildeslash.com Best regards, the Monit team

1 0

[Announce] M/Monit 2.2
by Jan-Henrik Haukeland 17 Feb '10

17 Feb '10

Hello, everyone! We have just released M/Monit 2.2. You can download the new release from: http://mmonit.com/download/ Release information: ==================== Improvements * Added support for Monit 5.1 (required to support multiple service groups per service which was added in Monit 5.1). * Allow non-fully qualified domain name in mail addresses * Added automatic synchronization of services and service group names with Monit. Services that are no longer configured in any Monit agent configuration file are not displayed in the rules admin drop-down menu. Likewise, if new services are added to a Monit agent they will be displayed and made available when setting up alert rules in M/Monit. The Events page will still display removed services in the drill-down filter if there are events referring to old removed services. * When specifying a rule, the service menu is context sensitive, that is, the menu lists only services that belongs to the selected host. If a host group is selected, only services that are common for all hosts in the group. * M/Monit database schema version added and checked on startup. Bug fixes * Fixed alert mail duplication which could occur in some situations. Thanks to George Agnelli for bug report. * Fixed sporadic long waits when doing an action on a service in the status detailed page. When M/Monit performs a start, stop restart etc action it waits up to 30 seconds for a reply from Monit before it times out. In some situations, especially if Monit is running in a virtual machine, Monit could reply before M/Monit started its wait, which would result in M/Monit waiting the full 30 seconds before timeout. * Fixed a crash that could occur if a host was added to a non-existent host group. Thanks to Jarod Reid for report. * Fixed initial sorting of host names in the host admin table. * If several sessions were open for the same user and password changed, the new password was not applied until all the sessions had terminated. This is now fixed and password changes takes effect immediately. * Monit 5.1 now makes sure that it sends a timely status message to M/Monit, even if Monit is busy in long testing cycles, to prevent false alerts generated by M/Monit about non-responsive Monit agents. Upgrading from M/Monit 2.1.1: ============================= If you are upgrading from M/Monit 2.1.1 please perform the following to upgrade the database: If you use SQLite: ./upgrade/upgrade-2.1.x-2.2.sqlite If you use MySQL: cp mmonit-2.1.1/conf/* mmonit-2.2/conf/ cat ./upgrade/upgrade-2.1.x-2.2.mysql | mysql -u mmonit -p -D mmonit If you use Postgresql: cp mmonit-2.1.1/conf/* mmonit-2.2/conf/ cat ./upgrade/upgrade-2.1.x-2.2.postgresql | psql -U mmonit mmonit Browser Cache: Please clear your Browser cache before login to M/Monit 2.2. Some pages have been changed and cached pages from the previous version may create problems. 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(a)tildeslash.com Future plans: ============= * We have now started on our plan to add historical data, statistical analysis, trend charts and other charts to M/Monit. * We are working on adding new, more thematic screencasts to the M/Monit website which we hope will be useful. With the best regards from the M/Monit team.

1 0

M/Monit for iPhone updated
by Jan-Henrik Haukeland 02 Feb '10

02 Feb '10

Hello all, Just a quick note to let you know that the M/Monit iPhone app has been updated and can be downloaded from the app-store. The main changes in this version is that the iPhone app now works with a self-signed SSL certificate. Caveats, we have seen some error messages in the app when adding credentials such as session has expired etc. The trick is to restart the iPhone app and enter credentials again until it works, as it does work. Remember to enter the URL to M/Monit with a trailing slash, such as http://x.x.x.x:8080/ where x.x.x.x is an IP-address or hostname where mmonit runs and 8080 is the port number the mmonit server listen on. Best regards from the M/Monit team.

1 0

[Announce] M/Monit 2.1.1
by Jan-Henrik Haukeland 01 Nov '09

01 Nov '09

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.

1 0

[Announce] M/Monit 2.1
by Jan-Henrik Haukeland 24 Oct '09

24 Oct '09

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.

1 0

[Announce] Monit 5.0.3
by Martin Pala 29 May '09

29 May '09

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.

1 0

[Announce] M/Monit 2.0.3
by Jan-Henrik Haukeland 21 May '09

21 May '09

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

1 0

FYI: NumberFormatException bug and a temporary workaround
by Jan-Henrik Haukeland 19 May '09

19 May '09

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/

1 0

[Announce] M/Monit 2.0.2
by Jan-Henrik Haukeland 15 May '09

15 May '09

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

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mmonit-announce