Skip navigation links
MySQL Enterprise Monitor 2.0 :: D MySQL Enterprise Monitor Change History :: D.5 Changes in MySQL Enterprise Monitor 2.0.3 (23rd January 2009)
D.6 Changes in MySQL Enterprise Monitor 2.0.2 (14th January 2009) »
Section Navigation      [Toggle]

D.5. Changes in MySQL Enterprise Monitor 2.0.3 (23rd January 2009)

This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.2.

Bugs fixed:

  • The Monitor Agent failed to connect to the server, and no error message was displayed in the log file.

    However, when the log verbosity level was set to message, the following message was recorded: 

    2009-01-12 13:34:43: (warning) agent_mysqld.c:600: agent connecting to mysql-server
failed: mysql_real_connect(host = '127.0.0.1', port = 3306, socket = ''): Lost connection
to MySQL server at 'reading initial communication packet', system error: 0 (mysql-errno =
2013)

    (Bug#42044)

  • There was a mismatch between the contents of an SNMP Trap from MySQL Enterprise Monitor and the definition given in the file MONITOR.MIB. (Bug#41912)

  • If a copy was made of a standard rule, the resulting Wiki markup was incorrect, resulting in the display of user-interface text containing HTML markup. (Bug#41375)

  • Allowing the heat chart rules to be set to unscheduled caused the user interface to appear broken. (Bug#41312)

  • When a custom rule requiring disk information was created, for example: 

    [Expression]
%disk_reads%> THRESHOLD

[Thresholds]
Critical Alert: 9000
Warning Alert: 3000
Info Alert: 1000

[Variable Assignment]
variables: %disk_reads%
Data Item: os:disk:disk_reads
Instance: /

    The following error was written to the file mysql-service-agent.log: 

    2007-09-05 17:11:00: (critical) disk-get failed for c0d0p1: 2

    It therefore appeared that the Monitor Agent was not able to obtain the required information. (Bug#30820)