The Monitor Agent did not log connections to, and disconnects from, the monitored database.

This meant it was not possible to check if the Agent was connected to the database by simply looking at the log file. (Bug#42403)

The Monitor Agent failed to create the mysql.inventory table. The logs displayed the following error message:

(critical) (share/mysql-proxy/quan.lua:711) [proxy] please add SELECT permissions for
this user on mysql.inventory to enable the QUAN feature, got Table 'mysql.inventory'
doesn't exist

This happened even though the Monitor Agent used the root account. (Bug#42389)

After installing Monitor Agent 2.0.4.7138 and then starting it with --version, the incorrect version was displayed. Although 2.0.4.7138 was installed, the Monitor Agent displayed the version number as 2.0.2.7138. (Bug#42263)

An invalid path was shown in the error message if the upgrade installer failed to find the previous install location.

The error message is shown below, note that the error message displays a different path to that provided by the user:

Please specify the directory that contains the previous installation of the MySQL
Enterprise Monitor Agent

Installation directory [/home/mysql/mysql/enterprise/agent]: /var/lib/mysql/agent

Warning: The directory /home/mysql/mysql/enterprise/agent does not contain a a
previous installation. Please select the right installation directory.
Press [Enter] to continue :
----------------------------------------------------------------------------
Please specify the directory that contains the previous installation of the MySQL
Enterprise Monitor Agent

(Bug#42200)

The agent password error in the Service Manager did not log the originating host, making it impossible to determine the agent that failed to log in:

ErrorJan 5, 2009 4:56:08 PM<?xml version='1.0'?><exceptions><error><![CDATA[E1702:
IncorrectPasswordException: [agent]]]></error></exceptions>

(Bug#42139)

The Service Manager's JDBC connections did not have sql_mode set to include NO_ENGINE_SUBSTITUTION. This resulted in the failure of Data Definition Language (DDL) if the Service Manager was inadvertently pointed to an incorrect mysqld instance. (Bug#42137)

A number of Advisor rules had advice text that had not been translated into Japanese. The Advisors that contained untranslated rules included Performance, Schema and Security. (Bug#42067)

Monitor Agent configuration files had global read privileges on the filesystem. (Bug#41794)

When the log files rotated to the maximum allowed by the log4j configuration, the metadata contained in the FileAppender became out of synchronization due to a logic bug. This caused an assertion error on any subsequent request for the logs tab or data. (Bug#41593)

SNMP trap messages were sending 127.0.0.1 as the IP address, and there was no feature to allow the user to configure the IP address contained in the SNMP message, which would have been useful for troubleshooting. (Bug#41361)

On all available test systems, including SUSE Linux Enterprise Server (SLES) 9 and 10 x86-32, x86-64, IA64, and Ubuntu 6.10 x86-64, the agent memory grew incrementally within ~3 hours to ~25M.

The agents then switched to the 'red' condition on the dashboard and no more data was reported. The agent processes were still alive.

This was also present in MySQL Enterprise Monitor version 2.0.0.7111 on Suse 7.3, with the glibc2.2 x86 agent.

There was no load on the monitored servers, and the problem also occurred when the “self-quan” was not configured. (Bug#41244)

Although the Monitor tab loaded initially, after a 64-bit MySQL server running a 32-bit MySQL Monitor Agent was clicked, a Null Pointer Exception was generated. (Bug#41164)

The Monitor Agent startup configuration did not seem to work and did not generate a log file. (Bug#40583)

An error generated by a rule failed to clear.

When a rule was created with the os:disk:fs_used data item, if the instance was not a valid mount point then the Monitor Agent reported the error:

2008-08-11 17:57:00: (critical) disk-get failed for all: 2

Note the above instance was for “all”, and similar results occurred for instance “disk”.

The issue was that upon editing the rule, or even deleting the rule, the agent still showed the above error type. Restarting the agent and the monitoring service failed to remove the error. (Bug#38709)

If the “On Save send test trap” checkbox was checked when the Save button was clicked and the locale was set to Japanese, an error occurred. The orange error banner was displayed at the top of the page with the error message in Japanese. (Bug#32069)