This appendix lists the changes to the MySQL Enterprise Monitor, beginning with the most recent release. Each release section covers added or changed functionality, bug fixes, and known issues, if applicable. All bug fixes are referenced by bug number and include a link to the bug database. Bugs are listed in order of resolution. To find a bug quickly, search by bug number.
This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 1.3.3.
Functionality added or changed:
Important Change:
The server-name configuration parameter is
deprecated. For compatibility, during an upgrade, the
information will be migrated to a displayname
configuration parameter within the individual instance
configuration files. This configuration parameter is provided
only for compatibility, as display name information is now
stored within the main repository. Support for
displayname is also deprecated and will be
removed in a future release.
Important Note: The rules 「32-Bit Binary Running on 64-Bit AMD Or Intel System」 and 「Key Buffer Size Greater Than 4 GB」 occasionally do not evaluate correctly due to timing issues. This causes them to be displayed with the Severity level of 「Unknown」. This is a known issue and will be resolved in future versions of MySQL Enterprise Monitor.
Important Note: When you start the Merlin 2.0 agent from the command line on Windows, you get the following error dialog:
"mysql-proxy.exe - Entry Point Not Found" "The procedure entry point libiconv_set_relocation_prefix could not be located in the dynamic link library iconv.dll"
If you click the agent works fine after that.
This only occurs when starting the agent from the command line,
and only when there is another version of one of the DLLs that
the agent uses somewhere on the current path. This error can be
avoided by opening a command prompt, typing SET
PATH= to clear the path, and then starting the agent.
Important Note: If you are monitoring one instance of MySQL server (mysqld) and then upgrade that MySQL server, the correct version of the MySQL server is not displayed in the Dashboard. This is a known issue that will be fixed in future versions of MySQL Enterprise Monitor.
The following has been added to the Tomcat
config.properties properties file:
# max connections in the pool for the repository
default.maxActive=70
The dashboard could be used to change the agent password to one
containing the @ character, or other special
characters, which subsequently caused errors. To fix this
problem, special characters in passwords are now prevented by
the dashboard. The list of disallowed special characters can be
found at the following location:
http://en.wikipedia.org/wiki/Percent-encoding#Types_of_URI_characters
(Bug#37172)
The Query Analysis page was missing the Refresh dropdown control that the Monitor, Events, and Graphs pages had at the top. (Bug#36831)
The User Interface only returned error strings, without any associated error codes. This meant that if the error string was in a language that the user did not understand, it would be very difficult to determine which error actually occurred.
The User Interface now supports error codes, as well as error strings. This change allows easier testing of multiple locales. (Bug#32131)
The wording was changed on the fading popup subscription alert. The text 「account」 was changed to 「subscription」. (Bug#31492)
The alert thresholds for the Query Cache Advisor were changed:
| Information | Warning | Critical | |
|---|---|---|---|
| From | 95 | 85 | 75 |
| To | 60 | 50 | 40 |
The agent log file name has changed from
mysql-service-agent.log to
mysql-monitor-agent.log. The old log file
will be retained during a upgrade install.
Bugs fixed:
Starting a new agent against an instance that contained many databases broke up the initial discovery packet, causing collections such as CPU usage and their graphs to fail. See also Bug#33150 and Bug#41314. (Bug#41933)
When altering an existing rule you had to add an empty string,
"", to any threshold level that was empty.
Otherwise, the rule failed to run and the resulting exceptions
caused the Events page to be unusable due
to duplicate key exceptions.
(Bug#41310)
After installing the 2.0.0.7119 Dashboard the following error was generated in the logs:
com.opensymphony.xwork2.util.OgnlValueStack Warning Dec 5, 2008 10:41:26 AM Caught an Ognl exception while getting property titleAddition
The dc_ng_long_now table became very large
partly due to an unused column begin_time.
(Bug#41093)
Although there was a unique constraint on the user name, it was
not enforced during first-time setup. This resulted in a stack
trace being produced, rather than a more user-friendly error
message, if the same name was used for the
admin and agent accounts.
(Bug#40870)
MySQL Enterprise Monitor server had stopped sending up/down SNMP traps. (Bug#40861)
The Query Analyzer's Explain Query tab did
not have pop up text or a link to the documentation regarding
SELECT queries.
(Bug#40841)
When you tried to import a Trial-level advisor JAR using a Trial user account, one of the following error messages was generated:
U0009 The uploaded Advisor jar was invalid
U0161 Please import a Platinum level Advisor .jar to use with this Platinum level product key
Meta Info on the Dashboard did not display information for the
meta data os_description.
(Bug#40830)
Attempting to create an alias of statements such as
COMMIT, ROLLBACK,
BEGIN, resulted in the error:
Can't find template commitTnx.st; group hierarchy is [HTMLFormatting] org.antlr.stringtemplate.StringTemplateGroup.lookupTemplate(StringTemplateGroup.java:507)
Trying to upgrade from 2.0.0.7088 to 2.0.0.7092 failed as there
was a missing file. When the update program
mysqlmonitor-2.0.0.7092-solaris-intel-update-installer.bin
was run, the file
/tmp/com/mysql/merlin/server/version.props
could not be found.
(Bug#40692)
On OS X with Java 1.5, Tomcat crashed on launch with the error:
Invalid memory access of location 00000007 eip=013df179
When the agent was installed using the command line installer
and --enableproxy 0 was specified, the
installer should have removed quan.lua from
the agent-item-files option in the INI file.
(Bug#40551)
The Agent could not connect to a database with the
hostname set to localhost.
Doing so resulted in the error:
(critical) the MySQL server could not be reached at socket '(null)', we will check in 10 seconds
The update installer for the 2.0 Monitor did not have an
Is SSL support required? checkbox.
Therefore, the appropriate SSL connector definition was
commented out in the conf/server.xml file.
(Bug#40414)
The Service Manager installer did not uninstall or wipe out the previous installation if you answered 「Yes」 to the question:
「The directory you selected already contains a MySQL installation. If you continue installation all data will be lost. Do you wish to continue?」 (Bug#40410)
If you unchecked the Enable Proxy checkbox on the Query Analysis Configuration screen, the agent's INI file still contained proxy configuration data and was not commented out. (Bug#40272)
As different queries were sent through the agent it used increasing amounts of memory. (Bug#40260)
The Service Manager installer set the Java Virtual Machine
option HeapDumpPath to
<install_root>\temp on Windows and
/tmp on other platforms. For consistency
the HeapDumpPath directory should have been
set to <install_root>\tmp on Windows.
(Bug#40215)
When using the command line agent setup program, a socket file was not accepted for the monitored instance. (Bug#40085)
The language option when installing the MySQL Enterprise Monitor in Japanese
using the command-line instllaer has been changed from
jp to ja.
(Bug#40082)
When monitoring MySQL 5.1.24 and above, the user used by the
agent to connect to the MySQL server for monitoring must have
the PROCESS privilege.
(Bug#40050)
The check box option string 「Is SSL support required?」, on the Tomcat Server Option dialog of the Monitor installation, was not correctly translated into Japanese. (Bug#39814)
The base application directory for the MySQL Enterprise Dashboard has been
updated from http://localhost:18080/merlin to
http://localhost:18080/.
(Bug#39403)
If the Service Manager or the MySQL Server running the Repository crashed, they did not restart automatically. (Bug#39377)
If the agent crashed, there was no watchdog, angel or keep-alive mechanism to restart the agent and keep it running. (Bug#39374)
If the MySQL client libraries were located in a nonstandard location, the agent 2.0.0.7042 installer failed with a 「library not found」 error. (Bug#39317)
For the rule 「Server-Enforced Data Integrity Checking Not
Strict」, the Recommended Action did not display
correctly. It displayed as SET
sql_mode=modes, rather than SET
[GLOBAL|SESSION] sql_mode=modes.
(Bug#39261)
A query that was issued through the proxy, and that had an
auto-explain performed on that query, did not give the correct
response to a subsequent query of SELECT
FOUND_ROWS().
(Bug#39223)
It was not possible to establish a connection with the Dashboard using the SSL protocol (https://). (Bug#39198)
When a 1.3 MySQL Enterprise Monitor installation with many rules scheduled was upgraded to 2.0, the upgraded installation was then found to have only the heat chart rules scheduled. (Bug#39043)
The agent installer did not allow a second agent to be installed on Windows. (Bug#38976)
The Dashboard incorrectly diplayed that insufficient licenses were available, even though sufficient licenses had been purchased. (Bug#38514)
After running the MySQL Service Agent uninstall program, the
file /etc/init.d/mysql-service-agent
remained present on the server.
(Bug#38490)
The notice fader continued to display English text after you changed the locale to Japanese. (Bug#38460)
The Subscription Expired pop-up window referred to the 「Global Preferences」 page, instead of the 「Global Settings」 page. (Bug#38358)
An inappropriate time zone was used to parse user-entered date and time strings. (Bug#38323)
A sigar network stats error was generated on the Solaris platform:
# /opt/mysql/enterprise/agent/bin/mysql-service-agent --version MySQL Service Agent - 1.2.0.7879, (glib lib=2.8.5, headers=2.8.5) SunOS mysqlprd01 5.10 Generic_127127-11 sun4v sparc SUNW,T5240 2008-07-21 10:07:24: (critical) sigar_net_interface_config_primary_get() failed: 6 2008-07-21 10:08:00: (critical) sigar_net_interface_config_primary_get() failed: 6 # /opt/mysql/enterprise/agent/bin/sigar-test-all >/tmp/test.txt sigar_net_interface_stat_get(e1000g0:2) failed#
After deleting a server from the Settings, Manage Servers tab, at the very bottom of the page the Monitoring x instances on x host values did not reflect the deletion. (Bug#38225)
The MySQL Enterprise Monitor alert 「INFO Alert - Users Can View All Databases On MySQL Server (v 1.5 *)」 from the Security advisor was incorrect. This is because the default server behavior allows users to see databases for which they have privileges, not 「all databases on server」 as suggested by the alert. (Bug#38052)
The 「Maximum Connection Limit Nearing Or Reached」 advisor did not generate a new Critical Alert event when there was an open info success event. (Bug#37816)
The Linux IA64 installer appeared to crash. The installer appeared to crash on RH4_IA64 if called with option "--version":
------------------------------------------------------------------------------- <INSTALLER> --version mysqlmonitorage(30704): unaligned access to 0x6000000000a8413c, ip=0x2000000003ddd5f0 mysqlmonitorage(30704): unaligned access to 0x6000000000a84144, ip=0x2000000003ddd5f1 mysqlmonitorage(30704): unaligned access to 0x6000000000a8414c, ip=0x2000000003ddd600 mysqlmonitorage(30704): unaligned access to 0x6000000000a84154, ip=0x2000000003ddd601 MySQL Enterprise Monitor Agent 0.7.0.1737 --- Built on 2008-06-25 19:31:53 -------------------------------------------------------------------------------
However, this warning is harmless and will not impact the operation of the agent. (Bug#37496)
If the log-level option in the agent configuration file was set
to an unknown level by mistake, the init.d
script appeared to enter an infinite loop.
(Bug#37108)
Malformatted server meta information appeared on the Dashboard; RAM and Disk Space appeared under the CPU category. (Bug#36740)
A 「rename」 link incorrectly appeared next to the Upgrade category on the Manage Rules page. (Bug#36584)
In the case where exceptions were passed through to the User Interface, the substituted arguments in the message contained developer-only information. (Bug#36580)
Agent Version, Last MySQL Contact, OS Info, CPU Info, and IP Addresses were all blank on the dashboard when the agent for the selected server was not functioning. (Bug#36301)
mysql-monitor-agent became confused by the
.DS_Store files that are created on Mac OS
X.
(Bug#36216)
The rule 「Key Buffer Size Greater Than 4 GB」 incorrectly triggered the following alert:
CRITICAL Alert - Key Buffer Size Greater Than 4 GB
However, on non-Windows systems, a key buffer size greater than 4 GB is supported. (Bug#36143)
Since the repository database for MySQL Enterprise Monitor uses InnoDB there was no way to reduce the size of the data files after an old log/event data purge operation. Further, the purge data operation executed once per day, and had no option to trigger the purge operation manually. (Bug#35971)
On the Graphs page, if all graphs were expanded, then the Time Display interval updated, the page was refreshed with the button displayed, even though all the graphs were already expanded. (Bug#35917, Bug#35133)
The Meta Info area of the Monitor page incorrectly reported the operating system version number for the MySQL version. (Bug#35836)
The rule 「XA Distributed Transaction Support Enabled For InnoDB」 incorrectly sent a warning when the binary log was on. (Bug#35786)
On the Monitor page, the time displayed for Last MySQL
Contact lagged behind that for Last Agent
Contact by a large amount.
(Bug#35774)
MySQL Enterprise Monitor did not update replication settings correctly. After a slave became the master, the Adviser still referred to it as a slave. (Bug#35771)
The Adviser email suggested using the
--log-queries-not-using-indexes option.
However, this option is not available in MySQL Server versions
prior to 4.1.
(Bug#35770)
Thumbnail graphs did not update properly after a time zone change. (Bug#35756)
If a system had a global wait_timeout lower
than the general activity of the agent, the agent was
disconnected. The monitored server then logged an error and
incremented Aborted_clients.
(Bug#35648)
Alerts fired after a blackout period based on data collections that happened during the blackout. (Bug#35617)
The translation of the button on the Rule Definition window was incorrect. (Bug#35495)
An uninstallation message asked about removing Apache files, even though Apache is no longer used. (Bug#35154)
After updating from a previous version to the latest 1.3 version, the Query Cache Has Sub-Optimal Hit Rate was still displayed in English after setting the locale to Japanese. Note, the rule was translated correctly if the full installer was used. (Bug#35134)
The MySQL Enterprise Monitor uninstall dialog box had missing text when using the Japanese locale. (Bug#34982)
Running the installer with the --help option
caused an incorrect message to be displayed.
(Bug#34200)
When using the unattended unInstall script
on Linux together with the option --env
deleteUserData=yes the correct warning text was
displayed. However, this text should not be displayed in
unattended mode. Further, the option --env
deleteUserData=yes was not displayed by the
--help output.
(Bug#34071)
Platinum Unlimited customers sometimes received a warning stating incorrectly that their subscription supported zero hosts. (Bug#34010)
Clicking on the resolution notes link for a closed event on the events tab showed incorrect behavior. The popup initially showed the resolution notes, but when the resolution tab was clicked the notes disappeared and were replaced by an edit box. (Bug#33935)
The status on the product information page was not translated when the user locale was set to Japanese. (Bug#32785)
When the locale was set to Japanese, the date picker still had English month titles. (Bug#32741)
Flashing display of a pop-up used while saving outgoing email settings was caused by problematic initial placement calculations. (Bug#32579)
AIX 5.2 Agent did not work on AIX 5.3. (Bug#32414)
When the First Time Setup program was run it did not prompt the user to allow importing an Advisor bundle. (Bug#32199)
Agent on MacOSX did not read IP addresses for network interfaces correctly, so the monitor displayed empty host IP addresses. (Bug#32188)
HTML code in queries was not escaped when reporting replication errors, causing the code to be rendered into the page. (Bug#32186)
The First Run pop-up defaulted to English rather than to the locale set in the browser. (Bug#32129)
The error dialog box flashed in the upper left corner before being positioned in the center of the screen. This error dialog box now opens in the center of the screen. (Bug#32068)
The Events list did not take into account Daylight Time and Standard Time when listing events that happened during 1:00am-1:59am. An event that occurred at 1:10am Standard Time was listed before an event that occurred 50 minutes before it at 1:20am Daylight Time. (Bug#32016)
The pop-up for editing log levels failed to load due to bad instantiation data. (Bug#32013)
During the repeated hour of Daylight Savings Time (when 2am turns back into 1am), the graphs were not drawing data. Instead, there was a straight line from the point at 1:00 to the second 1:00, which is what happens if there is no data. The repository did, however, have data for this hour. (Bug#31997)
Only US English was supported for a locale setting. Other
English variants are now available for the
locale setting on the General
Settings or the User Preferences
pages.
(Bug#31801)
If the user locale was changed the graph cache would continue to display the graph in the last locale until it timed out. (Bug#31680)
No init script was installed for the MySQL Network Monitoring Service Manager, and so it did not restart automatically on reboot. (Bug#31676)
The graph's displayed time was not the local time of the Dashboard corresponding to the requested time on the monitored server. (Bug#31656)
Saving a rule with a name that already existed resulted in a stack trace in the window, instead of a more user-friendly error message. (Bug#30925)
The network.mysql.com error messages were
remapped thereby causing confusion. For example, the following
error message:
E9000: MySQL Enterprise Customer Center is having difficulties fetching your contract information. Please contact enterprise-feedback@mysql.com for assistance.
Was remapped to:
Unable to connect to verify credentials (Bug#30873)
A newly added server showed as 「down」 in the user interface, and could potentially have sent a false alarm notification. (Bug#30735)
The information on the , page did not accurately reflect how many rules and graphs were actually in the database and available to the user. (Bug#29623)
The agent did not process SIGHUP.
(Bug#29380)
Monitor did not have a facility to stop or downgrade an agent collection frequency. (Bug#28589)
After an agent installation was updated from 1.0.1.4391 to
1.1.0.4899, the version in the menu was incorrectly displayed as 1.0.1.4391,
even though the update was successful and the file version of
agent.exe was correctly displayed as
1.1.0.4899.
(Bug#27447)
When viewing the Results of an Event in the Events tab of the Dashboard, the Notifications section did not reflect the Notifications settings at the time the Event was triggered, but rather the Notifications settings at the time the Event Results were viewed. (Bug#26349)
When the Monitor Agent was remotely monitoring a MySQL server it incorrectly reported that it could collect operating system information. (Bug#22497)
The Account Without Password advisor did not report all users who were without a password, it only reported one. (Bug#15165)