Home /  MMonit /  Release 4-2-1

Released on April 23, 2024

New installation | Upgrading

  1. New
  2. Fixed
  3. Enhanced

Changes Version 4.2.1

This release primarily focuses on performance improvements and also squashes a few bugs.

  1. M/Monit should feel snappier, and collector threads should no longer stall. The M/Monit Cache has been updated with finer lock granularity, which improves parallelism and speed. Analytics reports should be a bit faster, though they remain slow when generating comprehensive charts and statistics from extensive timelines. This will be further improved.
  2. On Linux, M/Monit will use considerably less memory as it no longer attempts to raise the number of available file descriptors to the soft limit.
  3. There was a deadlock issue when the AccessLogger was configured in server.xml to automatically rotate.
  4. Plus, 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.
  • Go to the unpacked mmonit-4.2.1 directory
  • Run M/Monit using: ./bin/mmonit
  • 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
  • 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.1 version.

  • Download the new 4.2.1 release for your OS.
  • Install M/Monit 4.2.1 in the same directory as previous release. For example: 
 /usr/local/mmonit-4.1.1
 /usr/local/mmonit-4.2.1
  • 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.1/upgrade/upgrade -p /usr/local/mmonit-4.1.1
  • Start M/Monit 4.2.1: 
 /usr/local/mmonit-4.2.1/bin/mmonit
  • Finally, please clear your browser cache before accessing M/Monit 4.2.1