Bug #70693 agent looking in the wrong place for the master details

• Submitted: 23 Oct 2013 6:18
• Modified: 7 Feb 2014 13:26
• Reporter: Simon Mudd (OCA)
• Status: Closed
• Category: MySQL Enterprise Monitor: Agent
• Severity: S3 (Non-critical)
• Version: 3.0.2.2900
• OS: Any
• CPU Architecture: Any

[23 Oct 2013 6:18] Simon Mudd

Description:
I notice in the logs.

2013-10-23 08:04:07,255 ERROR [cme.schedule.Scheduler-4:com.mysql.etools.agent.collection.mysql.MasterInfoDiscoveryStrategy] The master.info file '/path/to/master.info' does not exist
2013-10-23 08:05:07,249 ERROR [cme.schedule.Scheduler-14:com.mysql.etools.agent.collection.mysql.MasterInfoDiscoveryStrategy] The master.info file '/path/to/master.info' does not exist
2013-10-23 08:06:07,249 ERROR [cme.schedule.Scheduler-4:com.mysql.etools.agent.collection.mysql.MasterInfoDiscoveryStrategy] The master.info file '/path/to/master.info' does not exist
2013-10-23 08:07:07,250 ERROR [cme.schedule.Scheduler-3:com.mysql.etools.agent.collection.mysql.MasterInfoDiscoveryStrategy] The master.info file '/path/to/master.info' does not exist
2013-10-23 08:08:07,249 ERROR [cme.schedule.Scheduler-13:com.mysql.etools.agent.collection.mysql.MasterInfoDiscoveryStrategy] The master.info file '/path/to/master.info' does not exist
2013-10-23 08:09:07,249 ERROR [cme.schedule.Scheduler-2:com.mysql.etools.agent.collection.mysql.MasterInfoDiscoveryStrategy] The master.info file '/path/to/master.info' does not exist
2013-10-23 08:10:07,249 ERROR [cme.schedule.Scheduler-9:com.mysql.etools.agent.collection.mysql.MasterInfoDiscoveryStrategy] The master.info file '/path/to/master.info' does not exist
2013-10-23 08:11:07,249 ERROR [cme.schedule.Scheduler-16:com.mysql.etools.agent.collection.mysql.MasterInfoDiscoveryStrategy] The master.info file '/path/to/master.info' does not exist

The server being monitored runs 5.6 so does not use this file:

root@my56server [(none)]> show global variables like '%repository%';
+---------------------------+-------+
| Variable_name             | Value |
+---------------------------+-------+
| master_info_repository    | TABLE |
| relay_log_info_repository | TABLE |
+---------------------------+-------+
2 rows in set (0.00 sec)

root@my56server [(none)]> select @@version;
+------------+
| @@version  |
+------------+
| 5.6.14-log |
+------------+
1 row in set (0.00 sec)

How to repeat:
look in log file.

Suggested fix:
Please make the agent 5.6 aware, and if the configuration is using the TABLEs rather than the FILES, then look in the right place.

[7 Feb 2014 13:26] Mark Leith

Fixed 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)