MySQL Enterprise Monitor 3.3 Release Notes  /  Changes in MySQL Enterprise Monitor 3.3.3 (2017-03-13)

Changes in MySQL Enterprise Monitor 3.3.3 (2017-03-13)

Important

As of this release, MySQL Enterprise Monitor documentation is now included in the MySQL Enterprise Service Manager, MySQL Enterprise Monitor Agent, and MySQL Enterprise Monitor Proxy and Aggregator packages available from My Oracle Support or Oracle Software Delivery Cloud.

Security Notes

  • MySQL Enterprise Service Manager has been updated to use Apache Struts 2.3.32, which has been publicly reported as not vulnerable to CVE-2017-5638. (Bug #25698531)

Functionality Added or Changed

  • As of this release, MySQL Enterprise Monitor Agent no longer creates the mysql.inventory table on MySQL Server 5.6, or higher. The value of server_uuid is used to uniquely identify the server.

    For MySQL Server 5.5, the functionality is unchanged and the agent creates the mysql.inventory table. (Bug #24699549)

  • It is now possible to change the number of rows displayed in the Backups section on the History tab of the Enterprise Backup dashboard.

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

  • The Tomcat server, bundled with the MySQL Enterprise Service Manager, has been upgraded to 8.5.9.

Bugs Fixed

  • MySQL Enterprise Service Manager failed to start if the operating system's locale was set to FR_FR. (Bug #25615156)

  • MySQL Enterprise Monitor Agent installer stopped unexpectedly on Solaris platforms. This occurred for both unattended and text installation modes during the agent user credential step. (Bug #25427615)

  • No message was displayed on the Roles and Users pages if an attempt was made to save an incorrectly defined user or role. Such as a role without a name, or mismatched passwords. The role was not saved, but no reason was given for the failure to save. (Bug #25268334)

  • Input fields were available on the Roles and Users pages before a role or user was selected. (Bug #25268248)

  • No error was generated if the General and Limited user passwords violated a server-side password validation rule. This error occurred if the MySQL server used the password validation plug-in.

    As of this release, if a monitoring connection request fails because the General or Limited user's passwords do not meet the requirements on the server, an error is displayed with the server error message and the username which caused the error. (Bug #25153652)

  • Query detail graphs were not displayed on the Graphs tab of the query details dialog on the Query Analyzer page if the locale was set to Japanese. (Bug #24830763)

  • The Group Settings tab on the Edit Instance dialog was too small to properly display its contents. (Bug #24481474)

  • If agent.sh was run as root, incorrect permissions were applied to some log and keystore files, making them inaccessible to the agent, which runs as mysql.

    As of this release, it is not possible to run agent.sh from the command line as root, but only as mysql. (Bug #24338452)

  • The agent failed to start on Solaris platforms due to incorrectly defined permissions. (Bug #24327644)

  • MySQL Enterprise Monitor Agent upgrades overwrote custom, log4j configuration files with a new, default configuration file. As of this release, the custom log4j configuration files are preserved, and the new, default configuration is written to the same directory with the filename log4j.properties.default. (Bug #18501221)

  • MySQL Enterprise Service Manager upgrade, installed as root, reported errors on OS X. Services did not start after the upgrade completed, but could be started manually.