Bug #56330 Monitor error messages without an error code
Submitted: 27 Aug 2010 17:53 Modified: 9 Nov 2015 15:24
Reporter: Marcos Palacios Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Enterprise Monitor: Web Severity:S3 (Non-critical)
Version:2.2.2.1730 OS:Any
Assigned to: Josh Sled CPU Architecture:Any

[27 Aug 2010 17:53] Marcos Palacios
Description:
There are three rules that get error messages like these below when scheduling them. Two problems with the error messages:
* they refer to the rule as "monitor", 
* they don't have an error code (like "U0146").
An example error message with an error code is given at the bottom.

* The server "marcos-palacioss-macbook-pro.local:33306" does not support item(s) "mysql.variables.innodb_file_format_check" required by monitor "InnoDB File Format Check Disabled Or Incorrect".

* The server "marcos-palacioss-macbook-pro.local:33306" does not support item(s) "mysql.variables.innodb_strict_mode" required by monitor "InnoDB Strict Mode Is Off".

* The server "marcos-palacioss-macbook-pro.local:33306" does not support item(s) "mysql.variables.innodb_file_format" required by monitor "InnoDB Not Using Newest File Format".

Example:
* U0146 Unable to schedule rule "Binary Logging Is Limited" due to "mysql.MasterStatus.Binlog_Ignore_DB" data not being collected from server "marcos-palacioss-macbook-pro.local:33306". It may be an unsupported collection for that server.

How to repeat:
- install monitor and agent
- attempt to schedule these rules:
  InnoDB File Format Check Disabled Or Incorrect
  InnoDB Strict Mode Is Off
  InnoDB Not Using Newest File Format

Suggested fix:
- add error code
[20 Oct 2010 22:35] Enterprise Tools JIRA Robot
Marcos Palacios writes: 
In Japanese, these are the messages without error code (tested with build 2.3.0.2036):
* ???"dhcp-adc-twvpn-2-vpnpool- 10-154-54-101.vpn.oracle.com:13306" ? ???"InnoDB ???????????????????????"????????"mysql.variables.innodb_file_format" ????????????
* ???"marcos-palacioss- macbook-pro.local:3306" ? ???"InnoDB ???????????????????????"????????"mysql.variables.ignore_builtin_innodb" ????????????
* ???"dhcp- adc-twvpn-2-vpnpool-10-154-54-101.vpn.oracle.com:13306" ? ???"InnoDB Strict Mode ? OFF??"????????"mysql.variables.innodb_strict_mode" ????????????
* ???"dhcp-adc-twvpn-2- vpnpool-10-154-54-101.vpn.oracle.com:13306" ? ???"InnoDB ????????????????????????"????????"mysql.variables.innodb_file_format_check" ????????????
* ???"marcos-palacioss-macbook-pro.local:3306" ? ???"InnoDB INFORMATION_SCHEMA Plugins ????????"????????"mysql.variables.ignore_builtin_innodb" ????????????
* ???"marcos-palacioss-macbook-pro.local:3306" ? ???"InnoDB Strict Mode ? OFF??"????????"mysql.variables.ignore_builtin_innodb" ????????????
* ???"marcos-palacioss-macbook-pro.local:3306" ? ???"InnoDB ????????????????????????"????????"mysql.variables.innodb_file_format_check" ????????????
* ???"marcos-palacioss-macbook-pro.local:3306" ? ???"InnoDB ??????????????"????????"mysql.variables.ignore_builtin_innodb" ????????????
[9 Nov 2015 15:24] Mark Leith
Not an issue in 3.x.