Bug #41874 [mysqld] and [merlind] information are now in two seperate files

• Submitted: 5 Jan 2009 15:58
• Modified: 9 Jan 2009 16:23
• Reporter: Roger David Nay
• Status: Closed
• Category: MySQL Enterprise Monitor: Documentation
• Severity: S3 (Non-critical)
• Version: 2.0+
• OS: Any
• Assigned to: MC Brown
• CPU Architecture: Any

[5 Jan 2009 15:58] Roger David Nay

Description:
Sections

2.6.5 Troubleshooting the Agent
2.6.4 Monitoring Outside the Firewall with an SSH Tunnel

Both contain references to 
...with the values shown in the [mysqld] section of the mysql-monitor-agent.ini

...check the hostname specified in the [merlind] portion of the mysql-monitor-agent.ini file.

This information has been split up into two seperate files.

The placement of this [mysqld] information is no longer in the mysql-monitor-agent.ini file. The information for connecting to the MySQL database can be found in the /instances/mysql/agent-instance.ini file.

The [merlind] section configuration for connecting to the MySQL Monitor server is still contained in the mysql-monitor-agent.ini although there is not section for [merlind]. The [merlind] line has been removed and replaced with [mysql-proxy].

How to repeat:
View the installed 2.0 files.

Sections 2.6.1 and 2.6.2 of the 2.0 talk about the above files and give examples, so you can see there is a mismatch.

Suggested fix:
Update the documentation with the corrected information.

[9 Jan 2009 16:23] MC Brown

Thanks for a detailed report. The documentation has been updated accordingly.