Home /  MMonit /  Release 4-3-2

Released on Nov 1, 2024

New installation | Upgrading

  1. New
  2. Fixed
  3. Enhanced

Changes Version 4.3.2

This is a minor bug fix and improvement release.

  1. Alert Services for Microsoft Teams and Telegram: Added support for sending alerts directly to Microsoft Teams and Telegram.
  2. Repetition Support for Alert Services: Added repetition support for persistent errors (option set for individual Alert Rule action).
  3. Email SSL Configuration: Sending email from M/Monit now properly uses the SSL client configuration defined in server.xml. Previously, SMTPS, STARTTLS, and similar protocols used a default configuration, which could lead to connection errors if custom SSL/TLS settings were needed.
  4. Fixed an issue where updated Alert Services (e.g., when adding an API-key or endpoint) incorrectly appeared as disabled in the Rules -> Service list.
  5. Various minor bug fixes and improvements to enhance stability and performance.

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-4.3.2-linux-x64.tar.gz
  • Go to the unpacked mmonit-4.3.2 directory: 
 cd mmonit-4.3.2
  • Optional: Change the default account's password using: 
 ./bin/mmonit-admin password admin

 ./bin/mmonit-admin password monit
  • Run M/Monit using: 
 ./bin/mmonit
  • Point your browser to the host where M/Monit is installed (or "localhost" if running on the same machine), for example: http://localhost:8080/ and log in as user admin with password swordfish (or the password that was set using mmonit-admin).
  • 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 M/Monit in the foreground and in diagnostic mode by starting M/Monit with the -id options. In diagnostic mode, M/Monit will print errors and debug information to the console. Use CTRL+C to stop M/Monit 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.3.2 version.

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