Home /  MMonit /  Release 4-2-2

Released on May 8, 2024

New installation | Upgrading

  1. New
  2. Fixed
  3. Enhanced

Changes Version 4.2.2

This release primarily focus on performance and also add a new admin program.

  1. A new mmonitadmin program has been added to perform administrative tasks related to mmonit. Currently, it only has one function, which is to set the password of any mmonit user. Only the effective user who owns the mmonit installation and binaries, or root, can use mmonitadmin. M/Monit must be stopped before using the password command.
  2. Support for Monit-side specified hostgroups has been added. This feature requires Monit version 5.34.0 or higher. Membership assigned through the Monit configuration cannot be removed from the M/Monit side. To change the membership defined on the Monit side, you need to update the Monit configuration and reload Monit. Below is an example of a Monit configuration that assigns the host to M/Monit hostgroups named Oslo and Mail servers (these hostgroups will be created automatically if they do not already exist):
set mmonit
    with hostgroups [ Oslo, "Mail servers" ]
  1. Analytics performance has been improved, and generating charts should now be noticeably faster. TL;DR: Charts used to show about 60 data points for each metric within the selected time frame. When all hosts were selected, with thousands of data points, the volume of analytics data could become very large (> 5 MB), causing load times to exceed 30 seconds. We have reduced the number of data points per metric to around 30 within the selected time frame, reducing both data volume and load time. Higher precision is still available; to obtain more detailed data, simply make a custom selection in the chart, which will always drill down to the best available precision.
  2. Plus, a few minor fixes and improvements.

Hardware Recommendations

M/Monit heavily utilizes the database for generating analytics reports, such as producing various charts from timeline statistics. When using SQLite, we recommend installing M/Monit and the database on a system with fast storage access, such as an SSD, to optimize performance. For all database types, avoid using a network file system (NFS) to store the database.

New installation

  • Download the release for your OS.
  • Unpack the tar.gz file in a directory, any directory will do, but unpacking in /opt or /usr/local are good choices. Example:
 tar -xzf mmonit-linux-x64.tar.gz
  • Go to the unpacked mmonit-4.2.2 directory
 cd mmonit-4.2.2
  • Optional: Reset default accounts password using:
 ./bin/mmonitadmin password admin

 ./bin/mmonitadmin password monit
  • Run M/Monit using:
  • Point your Browser to the host where mmonit is installed (or "localhost" if running on the same machine), for example: http://localhost:8080/ and login as user admin with password swordfish (or the password which was set using mmonitadmin)
  • If you want to set up M/Monit to use MySQL or PostgreSQL instead of the default SQLite database, follow these instructions in the wiki.
  • More documentation can be found inline in the application and in the manual (PDF).
  • Troubleshooting If M/Monit does not appear to run, investigate the error.log in the logs directory. You can also run mmonit in the foreground and in diagnostic mode, start mmonit with the -id options. In diagnostic mode, mmonit will print errors and debug informations to the console. Use CTRL+C to stop mmonit in this mode.

Upgrading from previous M/Monit releases (2.3 or later)

The upgrade program can be used to automatically copy database and configuration files from the previous installation and update the database schema. On macOS upgrading is not needed as the installer will upgrade M/Monit in /usr/local/mmonit automatically.

The whole upgrade process should take less than a minute and you do not have to stop or change Monit on other machines during this process. Monit will simply pick up and start reporting to the new M/Monit 4.2.2 version.

  • Download the new 4.2.2 release for your OS.
  • Install M/Monit 4.2.2 in the same directory as previous release. For example:
  • Stop the previous M/Monit release.
 /usr/local/mmonit-4.1.1/bin/mmonit stop

Or if you monitor M/Monit via Monit:

 monit stop mmonit
  • Run the upgrade program and specify the path to the previous M/Monit release:
 /usr/local/mmonit-4.2.2/upgrade/upgrade -p /usr/local/mmonit-4.1.1
  • Start M/Monit 4.2.2:
  • Finally, please clear your browser cache before accessing M/Monit 4.2.2