- Report a bug
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.
/etc/init.d/mysql-mmm-monitor stop
/etc/default/mysql-mmm-monitor and set ENABLED to 0mmmd_mon was renamed to mmm_mond. So you can delete the old binary:rm -f /usr/sbin/mmmd_mon
/etc/init.d/mysql-mmm-monitor and adjusting the variable CLUSTERmmm_mon.conf and change status_path from /var/lib/misc/mmmd_mon.status to /var/lib/misc/mmm_mond.status - afterwards copy the existing status file to its new location:cp /var/lib/misc/mmmd_mon.status /var/lib/misc/mmm_mond.status
mmm_mon.conf and change pid_path from /var/run/mmmd_mon.pid to /var/run/mmm_mond.pidbin_path from /usr/bin/mysql-mmm.html to /usr/lib/mysql-mmm.html - then delete the old binaries:rm -rf /usr/bin/mysql-mmm
/etc/default/mysql-mmm-monitor and set ENABLED to 1/etc/init.d/mysql-mmm-monitor start
/etc/init.d/mysql-mmm-agent stop
/etc/default/mysql-mmm-agent and set ENABLED to 0mmmd_agent was renamed to mmm_agentd. So you can delete the old binary:rm -f /usr/sbin/mmmd_agent
mmm_*.conf and change bin_path from /usr/bin/mysql-mmm.html to /usr/lib/mysql-mmm.html - then delete the old binaries:rm -rf /usr/bin/mysql-mmm
mmm_*.conf and change pid_path in the <host> sections from /var/run/mmmd_agent.pid to /var/run/mmm_agentd.pid/etc/default/mysql-mmm-agent and set ENABLED to 1/etc/init.d/mysql-mmm-agent start