Bug #71118 MEM agent: do not report a missing master.info file if using TABLE replication

• Submitted: 9 Dec 2013 10:51
• Modified: 7 Feb 2014 11:02
• Reporter: Simon Mudd (OCA)
• Status: Closed
• Category: MySQL Enterprise Monitor: Agent
• Severity: S3 (Non-critical)
• Version: 3.0.4
• OS: Any
• CPU Architecture: Any

[9 Dec 2013 10:51] Simon Mudd

Description:
The agent reports this:

2013-12-09 11:47:05,700 ERROR com.mysql.etools.agent.collection.mysql.MasterInfoDiscoveryStrategy: The master.info file '/path/to/mysql/datadir/master.info' does not exist

This makes no sense given my configuration:

I have a slave configured this way:

+------------+
| @@version  |
+------------+
| 5.6.14-log |
+------------+

root@myslave [(none)]> show global variables like '%repository';
+---------------------------+-------+
| Variable_name             | Value |
+---------------------------+-------+
| master_info_repository    | TABLE |
| relay_log_info_repository | TABLE |
+---------------------------+-------+

How to repeat:
See above.

Suggested fix:
Do not report an error when the expected file is not expected to be there.

[7 Feb 2014 11:02] Mark Leith

This was resolved in 3.0.5:

"MySQL Enterprise Service Manager now also (first) checks the MySQL server 5.6+ master-info-repository variable to obtain the master's information. If set to table, then master information is read from the mysql.slave_master_info table. (Bug #17829049)"

http://dev.mysql.com/doc/mysql-monitor/3.0/en/mem-news-3-0-5.html