MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:andy bang Date:June 13 2017 6:49pm
Subject:MySQL Enterprise Monitor 3.2.8 has been released
View as plain text  
We are pleased to announce that MySQL Enterprise Monitor 3.2.8 is now
available for download on the My Oracle Support (MOS) web site.

This is a maintenance release that includes a few enhancements and
fixes a number of bugs.  You can find more information on the contents
of this release in the change log:

     http://dev.mysql.com/doc/relnotes/mysql-monitor/3.2/en/news-3-2-8.html
     (also included at the end of this note for convenience)

You will find binaries for the new release on My Oracle Support:

     https://support.oracle.com

Choose the "Patches & Updates" tab, and then choose the "Product or
Family (Advanced Search)" side tab in the "Patch Search" portlet.

IMPORTANT: MySQL Enterprise Monitor (MEM) 3.4 offers many significant
improvements over MEM 3.2 and MEM 3.3 and we highly recommend that you
consider upgrading. More information on MEM 3.4 is available here:

   What's New in MySQL Enterprise Monitor 3.4
   http://dev.mysql.com/doc/mysql-monitor/3.4/en/mem-comparison-3-4.html

   MySQL Enterprise Monitor
   http://www.mysql.com/products/enterprise/monitor.html

   MySQL Enterprise Monitor Frequently Asked Questions
   http://dev.mysql.com/doc/mysql-monitor/3.4/en/mem-faq.html

   MySQL Enterprise Monitor Change History
   http://dev.mysql.com/doc/relnotes/mysql-monitor/3.4/en/

Please open a bug or a ticket on My Oracle Support to report problems,
request features, or give us general feedback about how this release
meets your needs.

If you are not a MySQL Enterprise customer and want to try the Monitor
and Query Analyzer using our 30-day free customer trial, go to
http://www.mysql.com/trials, or contact Sales at
http://www.mysql.com/about/contact.

Useful URLs

* My Oracle Support - http://support.oracle.com/
* What's New in 3.2 - 
https://dev.mysql.com/doc/mysql-monitor/3.2/en/mem-comparison-3-2.html
* Change log - http://dev.mysql.com/doc/relnotes/mysql-monitor/3.2/en/
* Installation documentation - 
http://dev.mysql.com/doc/mysql-monitor/3.2/en/mem-installing.html
* Complete documentation - http://dev.mysql.com/doc/mysql-monitor/3.2/en/
* Product information - 
http://www.mysql.com/products/enterprise/monitor.html
* FAQs - http://dev.mysql.com/doc/mysql-monitor/3.2/en/mem-faq.html
* Download - http://support.oracle.com/

Thanks and Happy Monitoring!

   - The MySQL Enterprise Tools Development Team

==========

Changes in MySQL Enterprise Monitor 3.2.8

Functionality Added or Changed

* The Replication Configuration advisor now generates an event if
   slave_pending_jobs_size_max or slave_max_allowed_packet are less
   than the source's max_allowed_packet. (Bug #25996472)

* The MySQL server, bundled with the MySQL Enterprise Service Manager,
   has been upgraded to MySQL 5.6.36.

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

* The bundled JRE was updated to 1.8.0_131 for both the Agent and
   Service Manager.

* An agent installer is now available for FreeBSD 11.

Bugs Fixed

* A Null Pointer Exception was logged if the Average Statement
   Execution Time advisor was enabled but all its notice thresholds
   were disabled. (Bug #25872561)

* The documentation erroneously stated that SSL certificates which
   existed in the previous installation must be manually imported after
   an upgrade.

   The upgrade creates a backup of any existing SSL certificates and
   imports them into the upgraded version as part of the upgrade
   process. (Bug #25833748)

* MySQL Enterprise Service Manager stopped responding if a custom
   graph was imported, and the graph's definition included a hyphen (-)
   in the name.

   If a service restart was attempted, an Unexpected token error was
   logged and Tomcat would not start. (Bug #25761280)

* Network speeds were incorrectly reported on the Network Interfaces
   table of the MySQL Instances dashboard. (Bug #25636784)

* OS X 10.12 Sierra was not recognised and was listed as Unknown.
   (Bug #25511036)

* It was not possible to export graphs to PNG in Internet Explorer 11.
   (Bug #24831338)

* It MySQL Enterprise Monitor Agent encountered an error, it failed to
   restart due to a permissions issue. The mysql-monitor-agent.pid ran
   as root and could not be stopped by the agentrestart.sh which runs
   under the same user as MySQL Enterprise Monitor Agent.

   As of this release, the mysql-monitor-agent.pid is created with the
   permissions 644 (-rw-r--r--). (Bug #24667408)

* On Windows platforms, it was not possible to install to a path which
   contained spaces on any drive other than the C:\ drive.

   For example, trying to install to
   D:\Program Files\MySQL\Enterprise\Monitor failed,
   while
   C:\Program Files\MySQL\Enterprise\Monitor succeeded.
   (Bug #24482872)

* The MySQL Enterprise Monitor Agent was not properly displayed as
   running and monitoring an instance. This occurred if it was stopped
   and it's monitored instance removed from the MySQL Instances
   dashboard, and then the MySQL Enterprise Monitor Agent was
   restarted.

* Empty groups were not displayed on the Advisors page.

* If an instance was renamed on the MySQL Instances dashboard, the
   instance name was not updated immediately elsewhere in the user
   interface.

* Under certain circumstances, if a overrides were defined on MySQL
   instances in an advisor, both the parent and child schedules were
   evaluated for the overridden instance, instead of child schedule
   only. As a result, duplicate collections were performed and
   incorrect events displayed.

* The upgrade process prompted you to reimport SSL certificates from
   the backup of the previous version. This is not necessary unless you
   are using LDAP and had imported your own SSL certificates into the
   keystore of the JRE bundled with MySQL Enterprise Monitor.

   The prompt has been updated.

* Under certain circumstances, a monitored MySQL instance could be
   reported as having two, different server_uuid values. This could
   happen if the monitored instance was part of a replication topology,
   or installed in a docker container, and used Host Plus Data
   Directory from the MySQL Instance Identity Source menu.
Thread
MySQL Enterprise Monitor 3.2.8 has been releasedandy bang13 Jun