MMM for MySQL Wiki

Old releases

Pascal Hofmann — Tue, 11 May 2010 10:03:48 +0000

MMM 2.2.0 * * .deb MMM 2.1.1 * * .deb MMM 2.1.0 * * .deb MMM 2.0.10 * * .deb MMM 2.0.9 * * .deb MMM 2.0.8 * * .deb MMM 2.0.7 * * .deb MMM 2.0.6 * * .deb MMM 2.0.5 * *

Downloads

Pascal Hofmann — Tue, 11 May 2010 10:02:29 +0000

MMM 2 * Changelog * Download statistics * Old Releases MMM 2.2.1 Be sure to read the Upgrade informations before upgrading from MMM <2.1.0! * * Debian/Ubuntu Fedora/Red Hat Users of Fedora 11+ and Red Hat Enterprise Linux 5+ (via EPEL) can install MySQL-MMM with yum:

Changelog for MMM 2.x

Pascal Hofmann — Tue, 11 May 2010 09:59:39 +0000

MMM 2.2.1 * Fixed usage of wrong state name in set_active, forced_move_role and set_offline which could lead to strange errors when hosts had replication backlog. MMM 2.2.0 * Added manual mode (), wait mode, config values 'mode' and 'wait_for_other_master' * Don't die at startup when no network connection is available - wait for it to appear instead () * Changed startup behaviour. mmm_mond will only go into passive mode if it detects the active_master_role on more than one host. * Added …

FAQ

Pascal Hofmann — Thu, 15 Apr 2010 13:52:22 +0000

I have one master and many slaves and want to promote one slave to become a second master. Does this work? Yes. Set up master-master replication (don't forget log_slave_updates, etc.), then change mmm config and finally restart agents/monitor. FATAL Listener: Can't create socket! When I try to start the agent these messages are repeatedly logged:

Installation Guide - set bin_path to /usr/lib/mysql-mmm/ in mmm_mon.conf

fleish — Tue, 06 Apr 2010 23:28:07 +0000

Note: this guide is a draft, feel free to make changes if you see anything that can be improved, expanded on or corrected This installation guide describes a installation of MMM 2 (without the MMM tools) based on Debian Lenny (5.0) A basic installation contains at least 2 database servers and 1 monitoring server. In this guide, I used 5 servers with Debian Lenny (5.0)

Upgrade

Pascal Hofmann — Thu, 25 Feb 2010 12:10:56 +0000

Upgrading from 2.0.x to 2.1.0 MMM 2.1.0 is backwards compatible with MMM 2.0.x, so a monitoring host running version 2.1.0 can talk to agents running 2.0.x and the other way around. Upgrading the monitoring host * Stop mmmd_mon (if you have multiple clusters running, be sure to stop all instances of mmmd_mon): /etc/init.d/mysql-mmm-monitor stop