MySQL Enterprise Monitor 3.4 Release Notes  /  Changes in MySQL Enterprise Monitor 3.4.2 (2017-07-05)

Changes in MySQL Enterprise Monitor 3.4.2 (2017-07-05)

Agent-specific Issues in 3.4.2

  • Important Change: As MySQL Enterprise Monitor is enhanced over time, it is not always possible to maintain backward compatibility between new MySQL Enterprise Service Managers and older MySQL Enterprise Monitor Agents. Running mismatched versions can result in unpredictable behavior.

    The Wrong Version Agent Tracker advisor is updated in this release and renamed Unsupported Agent Version Advisor. This advisor checks all agents connecting to the MySQL Enterprise Service Manager and raises events for unsupported agents.

    It is strongly recommended that you upgrade your agents after upgrading your MySQL Enterprise Service Manager. MySQL Enterprise Service Manager and MySQL Enterprise Monitor Agent should be the same version.

  • If the following reports were run from a MySQL Enterprise Service Manager 3.4.1, which used older MySQL Enterprise Monitor Agents, a deserialization error occurred:

    • InnoDB Buffer Pool Usage

    • Processes

    • Lock Waits

    • Database File I/O

    • Table Statistics

    Important

    To run those reports, the MySQL Enterprise Monitor Agent version must match the MySQL Enterprise Service Manager version. That is, if you are running MySQL Enterprise Service Manager 3.4.2, you must also run MySQL Enterprise Monitor Agent 3.4.2.

    (Bug #26307003)

  • The MySQL User Account advisor in MySQL Enterprise Service Manager 3.4.1 could not evaluate data from MySQL Enterprise Monitor Agents of version 3.4.0 or earlier.

  • If MySQL Enterprise Monitor Agents were upgraded before the MySQL Enterprise Service Manager, under certain circumstances they disconnected and threw serialization errors.

    It is strongly recommended that you upgrade your agents after upgrading your MySQL Enterprise Service Manager. MySQL Enterprise Service Manager and MySQL Enterprise Monitor Agent should be the same version.

Functionality Added or Changed

  • The following advisors were removed and their functionality added to the MySQL User Account:

    • Non-root User Has GRANT Privileges On All Databases

    • Non-root User Has Server Admin Privileges

    • Account Has Strong MySQL Privileges

    For more information, see MySQL User Account. (Bug #26130781)

  • The OpenSSL libraries used by the MySQL Enterprise Monitor installers and MySQL Enterprise Monitor Aggregator have been upgraded to 1.0.2l.

  • As of this release, if you are using a MySQL Server repository other than the installation bundled with the MySQL Enterprise Service Manager installation, the installer checks the MySQL Server for the following, minimum requirements:

    • MySQL Server version: versions older then MySQL 5.7.9 are not supported.

    • SSL: SSL must be enabled on the MySQL Server.

    • innodb_file_format: innodb_file_format must be barracuda.

    • innodb_file_per_table: innodb_file_per_table must be enabled.

    If any of those checks fail, the installer displays an error and cannot proceed until the configuration is corrected.

    The upgrade process performs the same checks.

    To check your repository is correctly configured, the MySQL Enterprise Service Manager's configuration utility is extended with the parameter --mysql-check-requirements.

    For more information, see Service Manager Configuration Utilities.

Bugs Fixed

  • It was not possible to install the MySQL Enterprise Service Manager on Solaris due to a missing file, libstlport.so.1. (Bug #26336679)

  • The MySQL Enterprise Service Manager upgrade installer did not check the version of the MySQL server used as the repository. If the repository version was less than 5.7.9, the upgrade completed, but MySQL Enterprise Service Manager did not behave as expected.

    As of this release, the MySQL Enterprise Service Manager upgrade package requires MySQL server 5.7.9, or later, and will not install if the version is lower than 5.7.9. (Bug #25953683)

  • Validation messages were not displayed on the Settings page after a successful change was made.