Home /  MMonit /  Release 3-2-2

Released on July 18, 2014

Changes | New installation | Upgrading | Known Issues


  • Fixed: display correct system memory and swap on systems with more then 2TB of RAM.
  • Fixed: possible database connections leak, resulting in M/Monit not being able to read/write to the database.
  • Fixed: OpenSSL vulnerability CVE-2014-0224. The OpenSSL team released version 1.0.1h which fixes this bug. This version of M/Monit distribute and link with the fixed version of OpenSSL.

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-3.2.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 setup 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).

Upgrading from previous M/Monit versions (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.

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

  • Download the new 3.2.2 release for your OS.
  • Install M/Monit 3.2.2 in the same directory as the previous version. For example:
  • Stop the previous M/Monit version:
 /usr/local/mmonit/mmonit-3.2.1/bin/mmonit stop
  • Run the upgrade program and specify the path to the previous M/Monit version:
 /usr/local/mmonit/mmonit-3.2.2/upgrade/upgrade -p /usr/local/mmonit/mmonit-3.2.1
  • Start M/Monit 3.2.2:
  • Finally, clear your browser cache before accessing M/Monit

Known Issues

  • None