Home /  MMonit /  Release 4-2-0

Released on March 24, 2024

New installation | Upgrading

  1. New
  2. Fixed
  3. Enhanced

Changes Version 4.2.0

  1. Automatic detection of duplicate Monit ID. If multiple Monit Hosts are using the same Monit ID, which could happen if e.g. images with the same configuration and ID are copied, statistics and status will change constantly and nonsensical. If duplication is detected, a warning is posted in the Dashboard. See the FAQ on how-to solve Monit ID duplication.
  2. Intermittent disruptions in SSL connections.
  • Status page:
  1. Sort any table column in ascending or descending order. Host names are additional sorted in ascending order within the result.
  2. Improved Host search performance
  • Status details page:
  1. Added search filter for Service name and LED value
  2. Sort any table column in ascending or descending order. Service names are additional sorted in ascending order within the result.
  3. On mobile, the default sort column was not visible. The default sort column is now service name, in ascending order.
  • Admin:
  1. Added a new general Settings page for the application.
  2. If password audit is enabled and some accounts are using unsafe password, display a warning icon in admin/users
  3. Improve the admin/hosts page on mobile
  • Upgrade:
  1. MySQL or PostgreSQL upgrade could fail due to foreign key naming scheme

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.0 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.0 version.

  • Download the new 4.2.0 release for your OS.
  • Install M/Monit 4.2.0 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.0/upgrade/upgrade -p /usr/local/mmonit-4.1.1
  • Start M/Monit 4.2.0:
  • Finally, please clear your browser cache before accessing M/Monit 4.2.0