Home /  MMonit /  Release 4-0-2

Released on November 29, 2023

New installation | Upgrading

  1. New
  2. Fixed
  3. Enhanced

Changes Version 4.0.2

  1. Alert rules with program action, migrated from M/Monit version <= 3.x, triggered NumberFormatException when trying to update the rule.
  2. Dashboard: the Events in last 24-hours chart displayed stacked events incorrectly.
  3. Dashboard: the dismiss button in the Active errors and warnings didn't work.
  4. MariaDB backend: the SMTP and XMPP notification was broken, due to MariaDB's MySQL incompatibility.
  5. If a service with queued events was deleted, the following error could show up in the M/Monit log: 
 Event: processing failed (hostid=number, serviceid=-number) -- SQLException: FOREIGN KEY constraint failed
  1. M/Monit 4.0.0 could crash during service removal, with the following error message: 
 SQLException: FOREIGN KEY constraint failed when storing hostid number statistics
  1. 2024-01-22 macOS: Updated macOS installer with a new mmonit build that supports macOS 11 (Big Sur) and later.

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

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